14 commits

Author	SHA1	Message	Date
mehmet turac	8448b1105c	fix: preserve OpenClaude fallback credentials (#3361)	2026-05-31 03:49:25 +00:00
Denis Redozubov	f4c5d22f22	fix(daemon): confine sandbox project roots and host discovery (#3243) ... * fix(daemon): confine sandbox project and host discovery * fix(daemon): resolve sandbox data dir for toolchain discovery * fix(daemon): resolve sandbox data dir for agent env * fix(daemon): fail fast for sandbox imported folders * test(daemon): assert sandbox imported folder rejection * fix(daemon): keep sandbox import guard at run start * fix(daemon): reject sandbox imported project file roots * fix(daemon): preserve imported project detail roots * test(daemon): expect sandbox profiles to stay scoped * fix(daemon): bypass proxies for agent tool callbacks * test(daemon): isolate media policy route memory extraction * fix(daemon): keep loopback no-proxy scoped to sandbox	2026-05-30 16:57:04 +00:00
Denis Redozubov	9a3424d68c	feat(daemon): add sandbox runtime foundation (#3242) ... * feat(daemon): add sandbox runtime foundation * fix(daemon): preserve sandbox roots after agent env overrides * fix(daemon): keep readiness probes pathless * fix(daemon): harden headless run fallbacks * fix(daemon): bootstrap sandbox runtime discovery * fix(daemon): preserve explicit sandbox agent profile mounts * fix(daemon): keep sandbox profile lookup run scoped * fix(daemon): normalize sandbox data dir input * fix(daemon): pin sandbox env roots to base data dir	2026-05-30 15:06:05 +00:00
lefarcen	98a2c63973	feat(daemon): add Antigravity agent adapter (#3157) ... * feat(daemon): add Antigravity agent adapter Adds Google Antigravity (`agy` CLI) as a coding-agent runtime. Detection picks up `agy` on PATH, the daemon spawns `agy -p "<prompt>"` for a single non-interactive turn, and the assistant text reply streams back on stdout. OAuth is shared with the Antigravity IDE through the system keyring, so users who have signed into the desktop app are authenticated on first run with no extra step. `agy` v1.0.3 has no JSON / stream-json / ACP output mode (upstream issue #119), no `--model` flag (issue #35), and no MCP forwarding hook yet — the adapter ships with `streamFormat: 'plain'` and a single `default` fallback model so the model picker doesn't mislead users into thinking their choice is wired through. We will upgrade buildArgs + add a dedicated event parser when upstream ships structured output. Also gitignores `.antigravitycli/`, the project-local config directory `agy` auto-creates on every run (upstream issue #175). * fix(daemon): Antigravity adapter — stdin prompt, brand icon, form loop, empty-output guard - Switch prompt delivery from argv to stdin (`agy -p -`) to avoid the 30KB maxPromptArgBytes limit that blocked real-world composed prompts - Add official Antigravity brand SVG icon to agent picker - Fix repeated question-form loop for plain agents by injecting an OVERRIDE block when form answers are already present in the transcript - Add empty-output guard for plain agents so expired auth or silent failures surface a user-visible error instead of a blank "Done" turn * feat(daemon): expand Antigravity adapter — model picker, form-loop fix, OAuth launcher, log-file classification PR #3157 follow-up integrating four iterations from end-to-end manual testing on Gemini 3.5 Flash + GPT-OSS 120B Medium through `agy` v1.0.3. Each section is independently verifiable; combined they're what made the first successful artifact generation work end-to-end. ## Model picker via settings.json (agy has no --model flag) agy v1.0.3 ships no `--model` CLI flag (upstream issue #35), but the TUI Switch-Model picker writes the chosen label to `~/.gemini/antigravity-cli/settings.json`'s `"model"` field, and every `-p` invocation re-reads that file on startup — verified by capturing the `--log-file` line `Propagating selected model override to backend: label="<model>"`. Antigravity's `fallbackModels` now lists the 8 labels its TUI exposes (Gemini 3.1 Pro / 3.5 Flash variants, Claude Sonnet/Opus 4.6 Thinking, GPT-OSS 120B Medium) and `buildArgs` persists the user's choice to settings.json right before spawn. The synthetic `default` id is preserved — picking it leaves settings.json untouched so a user who switches models from agy's own TUI keeps their choice. Introduces `RuntimeAgentDef.supportsCustomModel?: boolean`. AMR's hardcoded blocklist in `SettingsDialog.tsx` migrates to the declarative flag (it rejects free-form ids at the ACP layer), and antigravity opts out because its label set is a server-side enum that silently fails on unrecognised strings. ## Form-loop fix (transcript sanitizer + stronger OVERRIDE) The discovery form loop on weak/medium plain-stream models (GPT-OSS 120B Medium, Gemini 3.5 Flash) had two reinforcing causes: 1. `buildDaemonTranscript` packed the prior assistant turn's literal `<question-form>` markup into the user request on the next turn, giving the model a template to echo. New `sanitizePriorAssistantTurnForTranscript` strips `<question-form>...</question-form>` blocks and ```json fences that match form-schema shape, replacing them with a brief placeholder. User content is preserved verbatim (a user who legitimately mentions `<question-form>` in chat keeps their message intact). 2. The OVERRIDE block on form-answered turns was 4 lines and only banned the bare `<question-form>` tag — models still emitted the fenced JSON, form-asking prose ("Got it — tell me the following"), and fake system events ("subagents stopped"). The new `FORM_ANSWERED_SYSTEM_OVERRIDE` enumerates each anti-pattern and pins them via tests, so silently weakening any line reintroduces the regression. Also adds RuntimeAgentDef.resumesSessionViaCli + RuntimeContext. hasPriorAssistantTurn as forward-looking abstractions (skipTranscript option on composeChatUserRequestForAgent). Antigravity does NOT opt in — agy's `-c` resume activates an internal agentic loop with tool retries and fallback-to-cached-response on tool errors that the OD system prompt cannot steer; reverted after seeing byte-identical form re-emissions caused by agy's own retry logic, not OD's transcript. ## One-click OAuth via system terminal agy print mode can't complete Google Sign-In on its own (the OAuth callback page asks the user to paste an auth code back into agy, but `-p` has no input field). Before this commit the auth banner only told the user to "open a terminal yourself." Adds `POST /api/agents/antigravity/oauth-launch` and a cross-platform launcher in `runtimes/terminal-launch.ts`: - macOS: osascript → Terminal.app `do script "agy"` + activate - Linux: tries x-terminal-emulator, gnome-terminal, konsole, xfce4-terminal, xterm in order - Windows: `cmd /c start "Open Design" cmd /k agy` The endpoint hardcodes the `agy` command (no user input → no shell injection surface) and is loopback-gated like the other daemon endpoints. The chat's `AGENT_AUTH_REQUIRED` banner now renders a "Sign in via terminal" button next to Retry; clicking it spawns the terminal so the user can finish OAuth in one click. ## Silent-failure classification (auth vs quota via --log-file) agy print mode is silent on stdout/stderr for both missing-OAuth AND quota-exhausted failures — the upstream `RESOURCE_EXHAUSTED (code 429): Individual quota reached` and the `not logged into Antigravity` line only surface in agy's `--log-file`. Without log inspection the daemon misread quota as "auth required" and showed the wrong banner. `RuntimeContext.agentLogFilePath` carries a daemon-owned per-run temp path that antigravity's buildArgs translates to `--log-file <path>`. The empty-output guard now reads that log on a `code === 0 && !childStdoutSeen` exit, feeds the tail to `classifyAgentServiceFailure`, and routes: - "not logged into Antigravity" → AGENT_AUTH_REQUIRED with antigravityAuthGuidance - "RESOURCE_EXHAUSTED" / "quota" / → RATE_LIMITED with "Individual quota reached" antigravityQuotaGuidance - none of the above (rare) → fall back to auth guidance as the most likely cause Both surface a terminal launcher in the auth banner: auth gets "Sign in via terminal", quota gets "Switch model in terminal" — same endpoint, contextual label. The handler is identical (open agy in a terminal); the user either signs in or uses agy's Switch Model picker to pick a model with available quota. ## Validation - `pnpm guard` pass - `pnpm --filter @open-design/daemon` runtime + telemetry suites: 192 passed, 1 skipped (the 1 pre-existing `task-type` failure on origin/main is unrelated to this change) - `pnpm --filter @open-design/web` typecheck pass; sse / amr-guidance / AgentIcon suites pass (51 web tests) - Manual end-to-end on darwin + Gemini 3.5 Flash and GPT-OSS 120B Medium: turn-1 question-form rendered correctly, turn-2 produced `<artifact>` with full HTML (3.3KB Modern Minimal design) instead of re-emitting the form. agy `--log-file` content correctly classified as RATE_LIMITED when Gemini Pro quota was exhausted, and as AGENT_AUTH_REQUIRED when keychain was cleared. * fix(web/test): align amrAgent fixture with supportsCustomModel contract The AMR agent definition in the daemon ships `supportsCustomModel: false` so the Settings model picker hides the free-text "Custom…" option. The PR changed `allowCustomModel` from `selected.id !== 'amr'` (hardcoded) to `selected.supportsCustomModel !== false` (declarative), but the test fixture was not updated to carry the same field — causing the `__custom__` sentinel to appear in the picker under test. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): align formAnswerTransition wording with main + scope build directive to discovery CI surfaced two failures on the merge with main: - chat-route.test marks submitted discovery form answers ... expected the main-version wording 'Do not emit another <formId> form.' - telemetry-message-finalization keeps non-discovery form answers active ... expected task-type to fall through the else branch ('Treat these form answers as the active user turn'), not the discovery RULE 2/RULE 3 build branch. The colleague's earlier fba1e40b form-loop fix tightened both pieces (stronger wording + grouped discovery|task-type into the build branch) but didn't update the tests that pin the contract. Revert the transition wording to main and re-scope the build directive to 'discovery' only. The aggressive form-loop suppression we added in this PR now lives in the system-prompt FORM_ANSWERED_SYSTEM_OVERRIDE block, which is far stronger than the user-request transition text this commit reverts. * fix(daemon): scope formOverride by form id, detach Linux terminal, move agy log cleanup to finally - FORM_ANSWERED_GENERIC_OVERRIDE: new exported constant for non-discovery/ non-task-type form ids; contains only the "do not re-ask" suppression without the RULE 2 / RULE 3 / artifact directive. - formAnswerTransitionForCurrentPrompt: extend build-transition branch to include task-type alongside discovery, keeping user-turn and system override consistent. - Prompt assembly (server.ts ~10848): derive formOverride from the parsed form id — FORM_ANSWERED_SYSTEM_OVERRIDE for discovery/task-type, FORM_ANSWERED_GENERIC_OVERRIDE for all other form ids, empty otherwise. - launchOnLinux: replace execFileAsync (waited for terminal exit, 3 s cap) with spawn({ detached: true, stdio: 'ignore' }) + unref(); resolve on the 'spawn' event so long-lived interactive terminals (xterm, konsole) are not killed mid-OAuth-flow. - Antigravity log cleanup: move fs.promises.unlink(agentLogFilePath) into a try/finally wrapper around the close handler so every exit path (success, failure, cancel, non-zero exit) cleans up the per-run temp file, preventing unbounded /tmp accumulation. - Tests: rename task-type case to assert build-transition behaviour; add generic-form-id case (preferences) pinning the non-build path; add FORM_ANSWERED_GENERIC_OVERRIDE content assertions. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): switch Antigravity buildArgs to chat subcommand invocation Replace top-level `-p -` with `agy chat [--log-file …] -` so the adapter uses the documented chat subcommand and stdin sentinel instead of the unrecognised global -p flag. Update the agent-args test description and all four deepEqual assertions to assert the ['chat', '-'] shape. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * test(daemon): drop real-platform default-launch assertion from terminal-launch suite The removed test called launchAgentInSystemTerminal('agy') with no platform override, which invokes the real system terminal on every developer machine running the daemon test suite (Terminal.app on macOS, cmd.exe on Windows, xterm/gnome-terminal on Linux). That is an unacceptable OS side effect for a unit test. The behaviour being asserted — that omitting platform selects process.platform — is a TypeScript default-parameter guarantee, not a runtime invariant that needs an integration test. The remaining 'aix' case continues to pin the unsupported-platform failure shape. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): buffer Antigravity stdout to suppress auth URL before close-time classifier The plain-stream close handler at code===0 can detect an agy OAuth prompt in agentStdoutTail and emit AGENT_AUTH_REQUIRED, but by the time close fires the stdout chunk has already been forwarded to the client via the plain-stream `send('stdout', { chunk })` path. This leaves both the raw OAuth URL and the terminal-launch guidance visible in chat. Buffer all stdout chunks for the `antigravity` agent instead of forwarding them immediately. The existing close-time auth-prompt guard (code===0, !trackingSubstantiveOutput, childStdoutSeen) returns early when it detects the auth pattern, leaving the buffer unflushed and the OAuth URL out of the SSE stream. For legitimate assistant output the buffer is flushed in order just before design.runs.finish so the chunks still arrive before the run's finished event. Adds a chat-route integration test using a fake `agy` that exits 0 after printing the canonical auth prompt; asserts that the run emits AGENT_AUTH_REQUIRED with no event: stdout delta containing the URL. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * test(daemon): isolate antigravity buildArgs argv test from real settings file Pass a temp antigravitySettingsPath in the RuntimeContext for the withModel argv assertion so unit tests do not touch ~/.gemini/antigravity-cli/settings.json. Adds the optional antigravitySettingsPath field to RuntimeContext and threads it through buildArgs to writeAntigravityModelSelection; production callers leave it undefined, preserving the existing default path. Generated-By: looper 0.9.2 (runner=fixer, agent=claude-code) * fix(daemon): revert Antigravity buildArgs to `-p -` (the only working agy v1.0.3 invocation) The looper-reviewer-bot reported `chat` as agy's headless subcommand based on its environment's agy build, and looper-fixer applied that shape. The installed CLI (`agy --version` reports `1.0.3`) does NOT expose a `chat` subcommand — `agy --help`'s `Available subcommands` section lists only `changelog / help / install / plugin / update`, and `agy chat - < prompt` exits 0 with empty stdout (the daemon then forwards it as a 'successful' empty reply, exactly the failure mode the auth/quota guard at server.ts ~12090 is meant to catch — for the wrong reason). `-p` is the documented print-mode flag (`Short alias for --print`) and `agy -p -` reads the prompt from stdin and prints the model reply, which the entire end-to-end test sequence in this PR has verified against (form-loop fix, settings.json model routing, log-file classification all confirmed working on Gemini 3.5 Flash + GPT-OSS 120B Medium with this invocation). Updates the agent-args test to pin `['-p', '-']` instead of `['chat', '-']` and adds an inline comment in antigravity.ts noting that `chat` may exist in a future agy build but is not the contract on the installed CLI today. * fix(daemon): serialize Antigravity concrete-model spawns to dodge settings.json race Reviewer (looper) flagged a concurrency race in the model-routing path: ~/.gemini/antigravity-cli/settings.json is process-global, so two OD runs starting close together with different concrete models can race the file — run A writes model A, run B writes model B, then A's agy finally reads settings.json and executes on model B. The Settings model picker becomes nondeterministic under parallel conversations. Adds a per-process promise chain in antigravity.ts: - acquireAntigravityModelLock(): chain-await + return release fn - waitForAgyToReadModel(logPath, expected): polls agy's --log-file for the upstream signal 'Propagating selected model override to backend: label="<X>"' which model_config_manager.go emits once agy has finished reading settings.json. Returns true on observed match, false on timeout. Regex-escapes the expected label so '(' / ')' in 'GPT-OSS 120B (Medium)' match literally, not as a capture group. server.ts spawn pipeline now acquires the lock BEFORE buildArgs (which performs the settings.json write) and schedules a release-once handler that fires when EITHER (a) the log-file confirms agy read the model or (b) the child exits — the exit fallback prevents a stuck/crashed agy from starving the queue for every subsequent antigravity spawn. Default-model spawns bypass the lock entirely: their buildArgs doesn't touch settings.json, so there's nothing to serialize. Tests pin: - FIFO ordering across 2 / 3 concurrent acquirers - Wait helper's regex correctly matches parenthesized labels - Wait helper does NOT match a different model with shared prefix - Wait helper swallows missing-log-file errors and returns false on timeout (no spawn-pipeline crash if the log never appears) 194 → 198 passing runtime tests, 0 regressions. * fix(daemon): close Antigravity lock release race on slow agy startup (looper #263fd2fe7) Reviewer flagged that the previous serialization scheduled `releaseOnce` in `.finally()` on waitForAgyToReadModel — meaning the helper's `false` timeout return ALSO released the lock. If agy took longer than the 15s polling window to read settings.json (cold start, swap-thrash, slow network handshake to the upstream backend), run A's lock dropped at 15s, run B rewrote settings.json with model B, and run A's still-starting agy then read the wrong model. Same race the original mutex was meant to close. Fix the release semantics to be release-on-confirmation-only: - waitForAgyToReadModel: `false` now strictly means 'I gave up polling,' not 'agy definitely did not read this.' Document the contract so a future caller can't conflate the two. Add an optional AbortSignal so server.ts can stop polling when the child exits — without it, the leftover watcher could outlive the run and accidentally match a later concurrent run's log content, releasing the wrong lock. - server.ts: schedule `releaseOnce` only when waitForAgyToReadModel returns true. The exit handler (which fires for crashes, fast exits, normal completion) is now the canonical fallback that releases the lock no matter what — the queue can't starve permanently because agy always exits eventually. The exit handler also fires the AbortController so the watcher cleans up. New tests pin: - timeout returns false WITHOUT any release-implying side effect - already-aborted signal short-circuits (no readFile calls) - abort mid-poll wakes the helper from its setTimeout (no multi-hundred-ms hang waiting out a poll interval that no longer matters) 198 → 201 passing runtime tests, 0 regressions. --------- Co-authored-by: qiongyu1999 <2694684348@qq.com>	2026-05-29 05:43:37 +00:00
Marc Chan	338cb4d423	fix(platform): support live system proxy changes (#3093) ... * fix(platform): support live system proxy changes * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Honor lowercase proxy env vars within a single source before merging proxy-aware envs.\n\nGenerated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Refresh provider request proxy env on each dispatcher creation and cover it with a focused regression test. Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): enable node env proxy for user proxy vars * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode) * fix(platform): support live system proxy changes Generated-By: looper 0.9.1 (runner=fixer, agent=opencode)	2026-05-28 06:11:47 +00:00
lefarcen	df8a0faff6	feat(runtimes): register AMR (vela) as an ACP stdio agent (#2355) ... * feat(runtimes): register AMR (vela) as an ACP stdio agent AMR is the vela CLI's ACP runtime mode. `vela agent run --runtime opencode` speaks ACP JSON-RPC over stdio (see vela's `specs/current/runtime/manual-agent-run-openrouter.md`); per `docs/new-agent-runtime-acp.md` we expose it through the same `streamFormat: 'acp-json-rpc'` transport that already powers Hermes, Devin, Kimi, etc. The new `defs/amr.ts` is the entire wiring — `buildArgs` returns `['agent', 'run', '--runtime', 'opencode']`, `fetchModels` reuses `detectAcpModels`, and the fallback list seeds the OpenRouter ids vela's e2e baseline uses. `executables.ts`/`app-config.ts`/`metadata.ts` get the matching `VELA_BIN`/`VELA_LINK_URL`/`VELA_RUNTIME_KEY`/`VELA_OPENCODE_BIN` allowlist + install/docs URLs, so users can configure the per-agent env in Settings without leaking into other adapters. Coverage: `tests/fixtures/fake-vela.mjs` is a minimal ACP stub that returns the documented `initialize` / `session/new` / `session/set_model` / `session/prompt` shapes; `tests/amr-acp-integration.test.ts` spawns it via `child_process.spawn` and drives a full turn through `attachAcpSession` and `detectAcpModels`, so the ACP transport contract for AMR is end-to-end verified locally even before a real `vela` binary is installed. Validated: - pnpm guard - pnpm typecheck (all workspace projects) - pnpm --filter @open-design/daemon test (2881/2881) Deferred: real OpenRouter-backed turn through a built `vela` binary — the runtime def needs no changes for that path, only `VELA_RUNTIME_KEY` and `VELA_LINK_URL` in env (or Settings). * fix(runtimes/amr): pin a concrete default model and bare openai ids End-to-end validation against a freshly-built `vela` (nexu-io/vela@main) + OpenRouter surfaced two contract details the first AMR runtime def got wrong: 1. vela rejects `session/prompt` with `session/set_model must be called before session/prompt`. attachAcpSession in apps/daemon/src/acp.ts skips set_model whenever the picked model is the synthetic 'default' id, so AMR's fallback list must NOT include DEFAULT_MODEL_OPTION. The def now ships a concrete `gpt-5.4-mini` as both `fetchModels`' default option and `fallbackModels[0]`, which makes attachAcpSession always send a real `session/set_model` for AMR turns. 2. `vela --runtime opencode` auto-prepends `openai/` to whatever modelId it forwards to opencode's openai provider. With OpenRouter-style ids like `openai/gpt-5.4-mini`, opencode receives the double-prefixed `openai/openai/gpt-5.4-mini` and replies `ProviderModelNotFoundError`. The new fallback list ships the bare ids opencode's openai registry actually knows about (gpt-5.4, gpt-5.4-mini, gpt-5.4-fast, etc.). Stub + tests: - tests/fixtures/fake-vela.mjs now enforces the set_model gate the same way real vela does, so a regression that silently goes back to model: 'default' would surface as a fatal error in tests instead of a hidden production failure. - tests/amr-acp-integration.test.ts pins both contracts: no 'default' / no 'openai/' prefix in fallbackModels, and a negative case that asserts session/prompt fails when no model is set. Adds `apps/daemon/scripts/verify-amr-real-vela.mjs` — a small dev-time runner that drives `attachAcpSession` against a real `vela` binary and prints the daemon's chat events, so future protocol drift can be checked against an actual OpenRouter call. Verified locally: `vela agent run --runtime opencode` + OpenRouter returns the prompted string ("AMR-E2E-PASS") through the full daemon pipeline; daemon test suite stays 2883/2883. * fix(runtimes/amr): substitute concrete model when chat run sends 'default' A plugin-driven AMR run from the UI surfaced a real-world hole in the prior commit: json-rpc id 3: session/set_model must be called before session/prompt The Default-design-router plugin (and any caller that doesn't pin a real model) sends `model: 'default'` straight through, which the AMR runtime def cannot accept — vela rejects `session/prompt` without `session/set_model` and attachAcpSession skips set_model whenever model === 'default'. Just leaving DEFAULT_MODEL_OPTION out of the adapter's `fallbackModels` is not enough: the chat-run handler in server.ts still forwarded 'default' verbatim. This adds `resolveModelForAgent(def, resolved, env?)` as the single source of truth for the substitution: 1. If the caller picked a real id, pass it through. 2. Else, if `def.defaultModelEnvVar` is set and the daemon process env has a non-empty value for it, return that (operator escape hatch — see below). 3. Else, if the def's `fallbackModels` does NOT contain a 'default' id, return `fallbackModels[0].id`. 4. Else, return the original value (the historic shape — defs that list 'default' themselves are untouched). AMR sets `defaultModelEnvVar: 'VELA_DEFAULT_MODEL'`, so when opencode's openai-provider registry deprecates `gpt-5.4-mini` upstream, an operator can swap the fallback id without a code change by exporting `VELA_DEFAULT_MODEL=gpt-5.5` before launching tools-dev / od. Worth noting the env var must live in the daemon's `process.env` (Settings-UI per-agent env values only reach the spawned child, not the daemon's resolver) — the new field's docblock spells this out. Coverage: - `tests/runtimes/resolve-model.test.ts` — 8 unit tests covering all four resolver branches plus the env-override happy path / fallback / ignore-when-user-picked-a-real-id case. - `pnpm --filter @open-design/daemon typecheck` clean. * chore(runtimes/amr): move AMR to the top of the base agent list So `AMR (vela)` shows up first in the agent picker / status views, ahead of claude / codex. Pure ordering change; no behavior delta. * feat(amr): Sign-in / Sign-out button on the AMR Settings card The first half of the AMR work assumed the operator would set VELA_RUNTIME_KEY / VELA_LINK_URL on the daemon process and never surfaced login state to users. This adds the missing UX so a fresh install can drive the full path from Settings: - GET /api/integrations/vela/status reads ~/.vela/config.json for the active profile and returns { loggedIn, profile, user } (without leaking the runtime/control keys themselves). - POST /api/integrations/vela/login spawns `vela login` once (409 if one is already in flight). The vela CLI opens the user's browser to the device-authorization page itself — Open Design only needs to kick the subprocess off. - POST /api/integrations/vela/logout removes ~/.vela/config.json so the next status read returns logged-out. `AmrAgentCard` is a dedicated agent-card component for AMR because the existing `<button>` row can't host an interactive sub-control (nested interactive elements). It polls /status after a login click until the daemon reports loggedIn=true (or 5 minutes elapse), and exposes a Sign-out action on hover. Other adapters (claude, codex, hermes, …) keep their existing `<button>` card. i18n: 8 new keys (settings.amrLogin / Logout / LoggingIn / etc.) added to en + zh-CN. Other locales spread `en` and inherit the English copy until translations land. Coverage: - `tests/integrations/vela.test.ts` pins the config.json reader against a tmp HOME — including the negative case where a profile has user info but no runtimeKey (still logged-out), and the secret-leak guard ("rt-secret-*" must not appear in the projection payload). - `tests/components/AmrAgentCard.test.tsx` covers all four UI states (logged-out, logging-in, logged-in, logging-out) plus the click-propagation invariant the divergent card was built to keep. `pnpm --filter @open-design/daemon test` 2901 / 2901 passing. `pnpm --filter @open-design/web test` 1719 / 1719 passing. `pnpm typecheck` + `pnpm guard` clean. Dev script side-effects: `apps/daemon/scripts/verify-amr-real-vela.mjs` no longer requires both VELA_RUNTIME_KEY and VELA_LINK_URL — if VELA_PROFILE is set, the vela CLI is allowed to resolve credentials from `~/.vela/config.json`. Added the two AMR `.mjs` fixtures to `scripts/guard.ts` allowlist with the executable-fixture / dev-runner rationale. * fix(connection-test): substitute model for AMR before attachAcpSession The chat-run path in server.ts already routes the requested model through `resolveModelForAgent` so AMR / vela (whose CLI demands an explicit `session/set_model` before `session/prompt`) gets the def's first concrete fallback id when the chat run ships `model: 'default'`. `connectionTest.ts` was wiring `attachAcpSession({ ..., model: model ?? null })` directly, which made the Test Connection button on the AMR Settings card deadlock with the same `session/set_model must be called before session/prompt` error the chat-run path already handles — surfaced as a permanent "Testing connection…" spinner in the UI. Reuse the same helper here so Test Connection mirrors chat-run behavior. * test(amr): three-layer end-to-end coverage for the AMR login + turn flow The PR up to this point shipped runtime + UI code with unit-level Vitest coverage. This commit adds the cross-layer regression net the live demo relied on: 1. apps/daemon/tests/integrations/vela.routes.test.ts (HTTP, Vitest) Spins up the real daemon Express app via `startServer({port:0,...})`, persists `agentCliEnv.amr.VELA_BIN = <fake>` into app-config.json, and exercises every /api/integrations/vela/* endpoint against the extended fake-vela stub: - status reads ~/.vela/config.json under various states - login spawns the fake, waits for config.json to appear, returns pid + startedAt + profile - 409 already-running guard with the stub's delay knob - logout removes the file (idempotent) - secrets (runtimeKey / controlKey) never leak in the projection - login → status round-trip flips loggedIn=false → true 2. e2e/tests/amr/turn.test.ts (tools-dev orchestrated, Vitest) Boots a namespaced daemon + web pair through `createSmokeSuite`, inlines a self-contained fake `vela` binary that handles BOTH `vela login` (writes ~/.vela/config.json) and `vela agent run --runtime opencode` (ACP stdio with the `session/set_model must precede session/prompt` gate the real binary enforces), then drives a complete /api/runs lifecycle for `agentId: 'amr', model: 'default'` and asserts the assistant message captures the fake's streamed text. This is the test that would have surfaced today's plugin-default-model regression (the `set_model before prompt` error) at PR time instead of demo time. 3. e2e/ui/amr-login-pill.test.ts (Playwright) Mocks /api/agents + /api/integrations/vela/{status,login,logout} to drive the Settings AMR card through the full Sign in → Signed in → Sign out cycle. Pins the AmrLoginPill polling contract and the aria-label semantics (the pill's accessible name is "Sign out" once logged in, regardless of which label the hover-state text shows). fake-vela.mjs extensions: - Handles `vela login` argv by writing ~/.vela/config.json for the active VELA_PROFILE and exiting 0 — mirrors real vela's on-disk side-effect without the device-auth loop. - FAKE_VELA_LOGIN_DELAY_MS knob so route tests can observe the in-flight state of the spawn lifecycle. - FAKE_VELA_LOGIN_USER_EMAIL / _USER_PLAN to assert the surfaced user fields end-to-end. Validated: - `pnpm guard` + `pnpm typecheck` (all workspace projects) - `pnpm --filter @open-design/daemon test`: 2998 / 2998 passing, including the new 8-test integration suite. - `cd e2e && pnpm test tests/amr`: 1 / 1 passing. - `cd e2e && pnpm exec playwright test ui/amr-login-pill.test.ts`: 1 / 1 passing (6.7s). * feat(amr): package native cli and refine login ui * feat(amr): wire vela cli beta packaging * docs(amr): document vela ci packaging review * docs(amr): refine vela ci integration review * fix(ci): refresh nix pnpm dependency hashes * fix(pack): clean up Vela CLI packaging * fix(pack): bundle Vela CLI support files * fix(amr): recover login attempts from stale auth state * test: expand AMR and automations coverage * fix(amr): address review follow-ups * test(web): align tasks fixtures with contracts * fix(daemon): type wildcard route params * fix(ci): refresh PR merge validation * fix(amr): clear env credentials on logout * feat(settings): inline local CLI model configuration * fix(amr): recognize daemon env credentials * [codex] Fix Vela companion packaging (#2979) * Fix Vela companion packaging * Update Nix pnpm dependency hashes * [codex] Surface AMR account failures (#2980) * fix: surface AMR account failures * fix: cover AMR recovery error guidance * chore: bump beta base version to 0.8.1 (#2990) * Fix AMR profile and packaged runtime review issues * Detect packaged AMR OpenCode companion tree * feat(web): polish AMR frontend flows * Polish AMR onboarding card * fix: read AMR login state from dot-amr config (#3048) * test: tighten AMR credential and packaging coverage * test: restore AMR executable test env helper * [codex] Fix packaged mac Dock identity and AMR label (#3076) * Fix packaged mac sidecar Dock identity * Rename AMR assistant label * Fix AMR live models and dot-amr login state (#3073) * fix: read AMR login state from dot-amr config * fix: load live AMR models before runs * fix: point AMR onboarding link to production wallet * fix: address AMR model review feedback * fix: persist live AMR model fallback * [codex] Fix AMR link catalog model ids (#3088) * Fix packaged mac sidecar Dock identity * Rename AMR assistant label * Fix AMR link catalog model ids * Fix AMR model normalization typecheck * Use live AMR model for default runs * fix: polish AMR runtime settings UI * Accelerate AMR startup defaults (#3092) * Surface AMR insufficient balance wallet URL (#3099) * fix(web): polish onboarding controls (#3112) * fix(web): show CLI scan loading state * Avoid duplicate AMR wallet recharge links (#3117) * Avoid duplicate AMR wallet recharge links * Use Vela CLI 0.0.3 test package * chore(nix): refresh pnpm deps hash * Fix AMR wallet guidance display --------- Co-authored-by: open-design-bot[bot] <282769551+open-design-bot[bot]@users.noreply.github.com> * chore(pack): pin Vela CLI 0.0.3-test.1 (#3127) * chore(nix): refresh pnpm deps hash * chore(pack): pin Vela CLI 0.0.3 * chore(nix): refresh pnpm deps hash * fix(web): suppress AMR exit 130 fallback (#3136) * feat(web): nudge users to hosted AMR on model/auth/quota failures (#3083) * feat(web): nudge users to hosted AMR on model/auth/quota failures When a non-AMR agent run fails with an auth / quota / upstream model error, surface an inline nudge under the error pill linking to Open Design's hosted AMR gateway (https://open-design.ai/amr). The nudge fires `surface_view` (element=run_failed_toast) on impression and `ui_click` (element=go_amr) on the link. Also teach the daemon to classify CLI-agent auth/quota/upstream failures (Claude Code, codex, ...) into specific API error codes (AGENT_AUTH_REQUIRED / RATE_LIMITED / UPSTREAM_UNAVAILABLE) instead of the generic AGENT_EXECUTION_FAILED, so both the error message and the nudge key off accurate codes. AMR's own runs are excluded from the nudge — they keep the dedicated sign-in / recharge affordances. * feat(web): rework failed-run AMR guidance into per-case error UI Replace the single inline nudge with a per-case failed-run experience driven by the run's error code + agent: - The error card is now neutral gray (was red) and always carries a retry button; it is driven by the persisted per-message error event so it survives a reload. - Non-AMR agent hitting a model/auth/quota wall: a theme-color promotion card under the error card offers "switch to AMR & retry" — switches the run to AMR, opens Settings on the AMR card, and auto-retries once the account signs in (ProjectView polls vela login status, independent of the Settings pill lifecycle, with success / 5-min-timeout / unmount exits). - AMR agent unauthorized: clearer copy + an "authorize & retry" button. - AMR agent out of balance: clearer copy + a "top up" button to the AMR wallet, with manual retry. - Settings AMR card: when opened from the nudge, it scrolls into view and pulses, and an authorize-button coachmark (a fake hand cursor that rises in and dismisses on hover) points at the sign-in control when not yet authorized. analytics: surface_view (run_failed_toast) on the promotion card and ui_click (go_amr) on its action are retained. i18n adds chat.amrCard.* and chat.amrError.* (en / zh-CN / zh-TW translated; other locales fall back to en) and drops the old chat.amrErrorGuidance keys. * fix(daemon): require status context for numeric service-failure codes Per review on #3083: the model-service classifier matched bare HTTP status numbers (`500`, `502`, `429`, `401`), so ordinary CLI output like `line 500`, `read 502 bytes`, or `exit code 401` could be misclassified as a provider outage / auth wall and wrongly surface the AMR nudge. Now a status number only counts when it carries explicit context (`HTTP 500`, `status 503`, `code: 401`, `502 Bad Gateway`); textual provider phrases (overloaded, bad gateway, service unavailable, rate limit, …) are unchanged. Adds fixtures proving unrelated numeric output stays null. * fix(web): keep error pill for failed runs ChatPane's card doesn't cover Per review on #3083: the per-message gray error pill was suppressed for every persisted error status event, but ChatPane only renders the replacement top-level error card for `retryableAssistantMessage` (the last failed assistant). So a failed turn that is no longer last (after a follow-up) or an older failed run in history showed neither the pill nor the card — its error detail vanished, undercutting reload/history survival. ChatPane now passes `errorCardOwnerId` (the assistant id whose error the card represents); AssistantMessage suppresses only that one pill and keeps rendering StatusPill for all other error events. * fix(daemon): don't treat a process exit code as an HTTP status Follow-up to review on #3083: the status-context helper accepted a bare `code` prefix, so `exit code 401` / `process exited with code 429` still matched and got classified as AGENT_AUTH_REQUIRED / RATE_LIMITED (the very `exit code 401` case the comment calls out as noise). `code` now only counts when qualified (`status code` / `error code` / `response code`) or punctuation-bound (`code: 401`); bare `exit code N` no longer matches. Adds fixtures for exit-code lines returning null. * chore(web): translate AMR card / error keys for 16 remaining locales PR #3083 added 10 new `chat.amrCard.*` / `chat.amrError.*` keys but only provided en/zh-CN/zh-TW translations; the other 16 locales fell back to English. Translate the card title/body, three chips, primary CTA, and the AMR self-error (auth / balance) messages and buttons for ar, de, es-ES, fa, fr, hu, id, it, ja, ko, pl, pt-BR, ru, th, tr, uk. * fix(amr): address review feedback on #2355 Targeted fixes for the unresolved review threads on #2355. Each fix includes / updates a focused test. - runtimes/executables.ts: `packagedVelaOpenCodeCompanionTree` now verifies the inner `opencode` executable exists + is runnable, not just the directory. This closes the false-positive availability path that let `detectAgents()` surface AMR as available even when the packaged companion was empty / partially copied (mrcfps, 4 threads). - runtimes/executables.ts: `resolveAmrOpenCodeExecutable` now prefers the bundled `<OD_RESOURCE_ROOT>/bin/libexec/opencode/opencode` over a stale `opencode` on the user's PATH, so packaged AMR builds can't be hijacked by a global installation. - web/EntryShell.tsx: when the Local CLI scan returns an available agent and the previously-selected agent is AMR, switch the selection to the first available local agent so the runtime and persisted agent agree before Continue. - server.ts (model-probe branch): for AMR, check `readVelaLoginStatus` BEFORE rejecting on an empty live-model catalog — a signed-out user was getting `AMR_MODEL_UNAVAILABLE` ("choose a model") instead of the correct `AMR_AUTH_REQUIRED` (sign-in affordance). - server.ts (default model fallback): if the user asked for the AMR agent default and the cached id is no longer in the FRESH catalog, fall back to `liveModels[0]` from the probe instead of rejecting the run as `AMR_MODEL_UNAVAILABLE`. - integrations/vela.ts: route `vela login` through `createCommandInvocation` so an npm/Node-style `vela.cmd` / `.bat` shim on Windows gets the correct `cmd.exe /d /s /c …` wrapping with verbatim args (matches `execAgentFile` / chat-run spawning). - tools/pack/src/linux.ts: in containerized Linux builds, bind-mount the host directory of `OPEN_DESIGN_VELA_CLI_BIN` and rewrite the env to the container-side path. The host path was being passed in as-is even though the default container only mounts /project, /tools-pack and cache/home — `copyOptionalVelaCliBinary` saw a missing path. Deferred (out of scope for this PR): - `od amr status/login/logout/cancel` CLI subcommands (AGENTS.md UI/CLI dual-track rule, server.ts:5763) — sizable surface; tracked for a separate focused PR. - Strict `--require-vela-cli` for Windows + mac-x64 beta builds: prematurely blocked — `@powerformer/vela-cli` only publishes the `darwin-arm64` platform binary today; adding the flag elsewhere would fail the builds. Revisit once win/x64/linux binaries ship. * fix(amr): hoist sendAmrAccountFailure above the AMR catalog preflight (TDZ) The new signed-out AMR branch in the catalog preflight at server.ts:10875 calls `sendAmrAccountFailure(...)` to emit AMR_AUTH_REQUIRED, but the const declaration sat ~100 lines below at the outer function scope. Because `const` is TDZ-aware, that branch would have thrown `ReferenceError: Cannot access 'sendAmrAccountFailure' before initialization` for the exact users it tries to help — defeating the original intent. Hoist the helper to just above the AMR preflight block so it's available to every AMR code path in this function. Behavior elsewhere is unchanged. Also rerun the daemon test suite: `launch.test.ts > resolveAgentLaunch uses packaged built-in Vela for AMR` was creating the `<resourceRoot>/bin/libexec/opencode/` companion *directory* only, but this PR's earlier tightening of `packagedVelaOpenCodeCompanionTree` also requires the inner `opencode` executable. Add it to that fixture to match the new contract; the test was a sibling of the executables / env-and-detection fixtures already updated in 13fc4f4. Addresses #2355 review (mrcfps, 2026-05-28). * feat(web): add hover cancel for AMR login (#3158) * feat(web): add hover cancel for AMR login * fix(web): don't bounce AmrLoginPill back to 'Signing in…' after local cancel Both codex-connector (P2) and looper (CHANGES_REQUESTED) on this PR flagged the same race in the new local-cancel path: `handleCancelLogin` dispatches `notifyAmrLoginStatusChanged('login-canceled')` immediately after `/login/cancel` returns, but the `AMR_LOGIN_STATUS_EVENT` listener unconditionally re-enters `refresh()` and then restarts polling whenever `/api/integrations/vela/status` still reports `loginInFlight: true`. That is a real race because the daemon's `cancelVelaLogin()` only sends SIGTERM (escalating to SIGKILL after `LOGIN_CANCEL_KILL_GRACE_MS` = 2000 ms) and keeps the child in `activeLoginProcs` until it actually exits — so the first `/status` read after a successful cancel can legally still come back as in-flight. Under that window the pill flips back to 'Signing in…' and can later surface the timeout/error path even though the user already canceled, defeating the behavior promised in the PR description. Fix the listener instead of every dispatch site: in the `login-canceled` branch, after the local reset (stopPolling + setPending(null) + clear refs), optimistically mark every subscribed pill instance as not-in-flight (`setStatus((c) => c ? { ...c, loginInFlight: false } : c)`) and `return` — skip the refresh-and-reconcile branch below entirely. The next explicit refresh (component mount, user interaction, or a `status-changed` event) will pick up the daemon's confirmed state once the child has actually exited. Add a focused regression test that holds `/api/integrations/vela/status` at `loginInFlight: true` even after a successful `/login/cancel`, asserting that the pill stays at the Canceled → Authorize sequence and never bounces back to 'Signing in…'. This test fails on the pre-fix listener and passes on the new behavior; existing 'cancels an in-flight AMR sign-in…' and 'reconciles late AMR browser completion to Signed in after local cancel' tests continue to pass. Addresses review feedback on #3158 (chatgpt-codex-connector, nettee). --------- Co-authored-by: lefarcen <935902669@qq.com> --------- Co-authored-by: a1chzt <chizblank@gmail.com> Co-authored-by: Amy <1184569493@qq.com> Co-authored-by: Mason <jinmeihong0201@gmail.com> Co-authored-by: Caprika <56862773+alchemistklk@users.noreply.github.com> Co-authored-by: open-design-bot[bot] <282769551+open-design-bot[bot]@users.noreply.github.com>	2026-05-28 05:09:55 +00:00
吴杨帆	8268253f61	fix(daemon): detect CodeWhale as DeepSeek TUI fallback binary (#3025) ... * fix(daemon): detect CodeWhale as DeepSeek TUI fallback binary The renamed CodeWhale CLI installs the `codewhale` dispatcher instead of `deepseek`. Probe it via fallbackBins so agent detection works without requiring DEEPSEEK_BIN overrides. Fixes #2983 * test(daemon): align deepseek docsUrl expectation with CodeWhale metadata Update env-and-detection coverage to match the runtime metadata URL changed for issue #2983.	2026-05-27 03:04:40 +00:00
MrBeanDev	07fad5d56a	feat(daemon): add Aider agent adapter (#1970) ... Wire Aider (https://aider.chat) into the daemon agent registry alongside the existing 16 CLIs. Aider is one of the most-used open-source coding CLIs and routes through LiteLLM, so users can drive any provider they already have a key for (OpenAI, Anthropic, DeepSeek, Gemini, OpenRouter, local Ollama, etc.) without an extra adapter per provider. Implementation follows the DeepSeek TUI pattern: prompt-via-argv with a 30 KB byte budget guard, plain stdout streaming, and the suppression flags needed to keep aider runnable without a TTY (--yes-always, --no-pretty, --no-git, --no-auto-commits, --no-suggest-shell-commands, --no-show-model-warnings). `--message-file -` is not used because aider treats `-` as a literal filename rather than a stdin sentinel. Touchpoints mirror the other one-shot adapters: - runtimes/defs/aider.ts new RuntimeAgentDef - runtimes/registry.ts register in AGENT_DEFS - runtimes/executables.ts AIDER_BIN override - app-config.ts AIDER_BIN in agent env set - web/utils/agentLabels.ts 'Aider' display label + aliases - tests/runtimes/agent-args.test.ts buildArgs shape coverage - tests/runtimes/env-and-detection bin override coverage - tests/runtimes/helpers shared `aider` test helper Validated with `pnpm guard`, `pnpm typecheck`, and `pnpm --filter @open-design/daemon test tests/runtimes` (123 passing). End-to-end probe against the live aider binary against DeepSeek via the exact argv the adapter produces returned the expected output.	2026-05-26 03:45:47 +00:00
jasonyang365	840019c8e2	Add Trae CLI as an ACP coding-agent adapter (#2729) ... * Add Trae CLI ACP adapter * Add Trae CLI binary override support * Update mature ACP MCP discovery test * Stabilize Orbit summary tracking test --------- Co-authored-by: AI Bot <bot@example.com>	2026-05-23 15:17:42 +00:00
YOMXXX	f08f7e390b	fix(daemon): strip stale BYOK OPENAI_API_KEY for codex spawn (#2441) ... Mirror the issue #398 fix the claude adapter already has: when spawning Codex CLI without a custom OPENAI_BASE_URL, strip both OPENAI_API_KEY and CODEX_API_KEY from the child env so Codex CLI's own `~/.codex/auth.json` (codex login) wins. Without this guard, a stale BYOK key left behind in `agentCliEnv.codex.OPENAI_API_KEY` (e.g. after the user clears the BYOK dialog and switches execution mode back to Local CLI) silently flows through `spawnEnvForAgent` and trips 401 invalid_api_key. The stripping is gated on OPENAI_BASE_URL so users who intentionally route Codex CLI through a third-party OpenAI-compatible gateway keep the credential that authenticates against it. Comparison is case-insensitive to close the Windows mixed-case env name hole that issue #398 already documents for ANTHROPIC_API_KEY. Fixes #2420	2026-05-22 19:47:29 +08:00
初晨	22b5cbdb25	Fix Cursor Agent model id parsing (#2228)	2026-05-19 18:11:09 +08:00
shangxinyu1	2976c76fc3	test: expand Memory and Routines coverage (#1521) ... * test: expand settings and packaged coverage * test: extend memory settings coverage * test: cover routine settings failure states * test: cover routine operation failures * test: fix daemon test typing on CI * test: decouple packaged smoke from orbit bug * test: avoid live memory LLM calls in route tests * test: fix daemon fetch typing in CI * fix: restore preview comment and inspect toggles * test: align manual edit flow with current inspector UX * test: align comment attachment flow with current preview comments UI * fix: probe resolved Codex launch path during detection * fix: remove duplicate board activation helper after rebase * test: update ghost cli detection mock * test: align FileViewer toolbar expectation * ci: move full app tests to extended lane * ci: run app tests by changed scope * ci: cover shared app inputs in test scopes * ci: avoid setup-node cache in windows packaged smoke * test: align extended settings and manual edit flows	2026-05-14 14:48:40 +08:00
Caprika	06dbde51f9	[codex] Add Cursor Agent auth diagnostics (#1538) ... * Add Cursor Agent auth diagnostics * Handle Cursor not logged in auth status * Address Cursor auth review feedback * Classify Cursor stdout auth failures	2026-05-13 20:25:34 +08:00
nettee	ab922327f4	refactor(daemon): split agent runtime definitions (#1063)	2026-05-11 15:01:55 +08:00