You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(chat): Codex landing connect shows no error, chat header stuck on "codex - not running" #726
On a Windows machine with Codex installed, with no Harness configured, Chat showed the big shiny connect landing. Pressing Codex:
Produced no error / no failure toast.
Dismissed the landing and bounced into the normal chat surface.
The chat header showed codex - not running.
Chat did not work (Harness never came up).
So the landing button looks successful while the session is dead.
Steps to reproduce
Machine has Codex installed (PATH / install present).
ai-buddy with no Harness configured (fresh / unset).
Open Chat → see connect landing (“Connect a Harness to get started”).
Press Codex.
Expected
Either:
Codex starts and the header shows it running, or
Connect fails loudly (error / stay on landing / actionable message) and does not pretend the session is connected.
Actual
Silent “success” path into chat with header codex - not running; no usable Harness session.
Environment
OS: Windows (DESKTOP-UQIE144)
Reporter: Oded, live repro 2026-09-15
Notes / likely area
Landing connect buttons in src/chat.html (data-harness="codex"). Failure from spawn / ACP handshake / PATH resolution is probably being swallowed before the UI can show it.
Related context (not dupes): #554 (Codex spike), #166 (harness attach).
Done when
Failed Codex connect from the landing surfaces a clear error (or stays on landing) instead of a dead chat.
Header does not claim a Harness that is not running without an explanation.
Repro above either connects for real or fails visibly.
Reporter notes: looks like missing npx is not handled nicely in the UI. Log from the same session as the silent Codex landing connect:
character: Buddy Bot from \\?\C:\tmp\ai-buddy\target\debug\characters\buddy-bot
overlay: overlay-0 covers 3440x1440 at (0,0)
overlay: overlay-1 covers 1200x1920 at (-1200,-209)
overlay: 2 display(s); sprite 90x90; Buddy Bot as Buddy Bot
harness: codex via `npx -y @agentclientprotocol/codex-acp@latest`
harness: MCP server http://127.0.0.1:58931/mcp, or `C:\tmp\ai-buddy\target\debug\ai-buddy.exe --mcp-stdio` (relays here) for a Harness that advertises no mcpCapabilities.http
harness: attaching now; the next `harness:` line on this stream is how it went
director: model, ambient first 120s
overlay: double-click interval 480ms
harness: `npx` is not installed; ai-buddy does not bundle a Harness; StaticDirector is in force until it answers
So the shell does know why attach failed (npx missing → StaticDirector), but Chat still dismissed the landing and showed codex - not running with no error. Done when should include: surface “npx is not installed” (or equivalent) in Chat when landing-connect fails for that reason.
Same failure mode: shell already prints `npx` is not installed; … StaticDirector is in force while Chat can dismiss the landing / show *- not running with no actionable copy.
First-party ACP presets (cursor-agent, hermes, opencode, grok) and custom native ACP (e.g. copilot --acp --stdio) do not need this path — they fail on a missing CLI binary instead.
Related: #735 (census), Architect comment on that issue.
Claiming this. Chat connect landing currently treats a Harness pick as ready as soon as Settings saves the name, while spawn_preflight still runs on another thread. Missing npx is logged and stored on HarnessInspect.missing, and Settings already names it. Chat's opening payload and landing do not.
Fixing the shared Chat/Harness error path for every npx-adapter preset (claude, codex, pi). Linux CI plus automated tests. No Windows desktop gate and no windows label on the PR.
Fix is in #831. Chat now stays on the landing when a pick cannot answer, and the header names a missing launcher (npx for the claude/codex/pi adapters).
#831 merged. Chat connect landing now stays up when an npx-adapter pick (claude / codex / pi) cannot answer, and the header names the missing launcher (e.g. `npx` is not installed) instead of a silent dead chat.
Acceptance on #726 is met. Issue closed via the PR.
Project card: gh token lacks read:project / project scopes here, so Status → Done needs a manual nudge if the card is still In Progress.
Activity
omesser commentedon Sep 15, 2026
Console log (Windows repro)
Reporter notes: looks like missing
npxis not handled nicely in the UI. Log from the same session as the silent Codex landing connect:So the shell does know why attach failed (
npxmissing → StaticDirector), but Chat still dismissed the landing and showedcodex - not runningwith no error. Done when should include: surface “npxis not installed” (or equivalent) in Chat when landing-connect fails for that reason.— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Sep 17, 2026
Scope note from the #735
npx/acpxspike (Architect)This bug is the “declare loudly” follow-up for missing Node/
npx(spike option 2). No separate issue opened.Please treat Done when as covering every npx-adapter preset, not only Codex:
claude→npx -y @agentclientprotocol/claude-agent-acp@latestcodex→npx -y @agentclientprotocol/codex-acp@latestpi→npx -y pi-acp@latestSame failure mode: shell already prints
`npx` is not installed; … StaticDirector is in forcewhile Chat can dismiss the landing / show*- not runningwith no actionable copy.First-party ACP presets (
cursor-agent,hermes,opencode,grok) and custom native ACP (e.g.copilot --acp --stdio) do not need this path — they fail on a missing CLI binary instead.Related: #735 (census), Architect comment on that issue.
— Cursor agent (Architect), on @omesser's behalf.
omesser commentedon Sep 17, 2026
Claiming this. Chat connect landing currently treats a Harness pick as ready as soon as Settings saves the name, while
spawn_preflightstill runs on another thread. Missingnpxis logged and stored onHarnessInspect.missing, and Settings already names it. Chat's opening payload and landing do not.Fixing the shared Chat/Harness error path for every npx-adapter preset (
claude,codex,pi). Linux CI plus automated tests. No Windows desktop gate and nowindowslabel on the PR.— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Sep 17, 2026
Fix is in #831. Chat now stays on the landing when a pick cannot answer, and the header names a missing launcher (
npxfor the claude/codex/pi adapters).— Cursor agent (Coder), on @omesser's behalf.
fix(chat): Surface a missing Harness launcher on the landing
omesser commentedon Sep 17, 2026
Landed
#831 merged. Chat connect landing now stays up when an npx-adapter pick (
claude/codex/pi) cannot answer, and the header names the missing launcher (e.g.`npx` is not installed) instead of a silent dead chat.Acceptance on #726 is met. Issue closed via the PR.
Project card:
ghtoken lacksread:project/projectscopes here, so Status → Done needs a manual nudge if the card is still In Progress.— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Sep 17, 2026
Shipped on main via #831 (merged 2026-09-17).
What landed:
`npx` is not installedfor the claude/codex/pi adapters), same reason Settings already used.ChatOpeningcarriesmissing;canAnswerrequires a live child with no missing launcher.Done-when from this issue is met. Auto-closed by the merge.
— Cursor agent (Coder), on @omesser's behalf.
fix(docs): Update runtime deps census to reflect #831 shipped
Fix: Chat shows unhealthy harness state and message
Fix: Chat shows unhealthy harness state and message