Repository navigation
Closed
Milestone
Description
What
Settings/landing copy should clarify which Harness presets need Node (Claude/Codex/Pi via npx adapters) vs which are standalone CLIs (hermes/opencode/grok/cursor-agent, zero external deps beyond the binary itself).
Why now
#735 census showed users face a choice: three presets need Node+npx (external dep), four need only a PATH binary (which they may already have installed). Presenting this distinction helps users choose the zero-dep option when available.
Scope
In
- Settings Harness picker — Group or annotate presets. Examples:
- "Standalone: hermes, opencode, grok, cursor-agent (no Node required)"
- "Requires Node: Claude, Codex, Pi (install from nodejs.org)"
- Or inline badges/notes per preset row.
- Chat connect landing — When presenting Harness buttons, clarify which need external deps. Same grouping or annotation as Settings.
- First failure messaging — fix(chat): Surface a missing Harness launcher on the landing #831 already shows ```npx` is not installed`` for Claude/Codex/Pi. Ensure first-party ACP missing-binary messages name the CLI to install (e.g. "Install Hermes from https://...").
- Consistent naming — "First-party ACP" vs "registry adapter" vs "npx adapter" — pick one term for the distinction and use it consistently.
Out
- Changing which presets exist (separate issues: spike(ship): Bundle Node runtime + pinned ACP adapters for self-contained Claude/Codex/Pi #928 Node bundling decision, goose/antigravity named presets).
- BYO harness UI (already separate; user supplies full argv).
Done when
- Settings Harness picker groups or annotates zero-Node presets (hermes/opencode/grok/cursor-agent) vs npx presets (Claude/Codex/Pi).
- Chat landing buttons or copy clarify the same distinction.
- Missing-binary messages for first-party ACP name the correct CLI + install URL (hermes → hermes-agent.nousresearch.com, etc.).
- Terminology consistent across Settings/landing/errors.
Related
- spike(ship): Census of runtime deps beyond the binary — self-contain or present cleanly #735 — runtime deps census (parent spike; this is UX follow-up)
- fix(chat): Surface a missing Harness launcher on the landing #831 — loud failure when missing launcher (shipped; this refines the messaging)
- spike(ship): Bundle Node runtime + pinned ACP adapters for self-contained Claude/Codex/Pi #928 — Node bundling spike (decision input; if Node is bundled, this distinction goes away for Claude/Codex/Pi)
— Cursor agent, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
No labels
Projects
- StatusShow more project fieldsDone
Activity
omesser commentedon Sep 23, 2026
Clarification (Oded)
Sticky inline missing-dep text (selectable / copy-paste into search or another AI), not a toast. Presentation owned by #950; install URLs + first-party vs npx grouping stay here.
Also related: #949 (Apply/Connect initializing), #948 (ADR).
— Cursor agent (Architect), on @omesser's behalf.
docs(research): Record Oded's locked decisions for runtime deps
docs(research): Record all Oded's locked decisions for runtime deps
omesser commentedon Sep 23, 2026
Shipped on main via #961
Merge commit
639a1486.Done when — checked against main
settings/form.rs.installUrlFor()(npx→ nodejs.org; hermes / cursor-agent / grok / opencode → their sites).not_installed()carries the same URLs.Chat landing does not add a separate proactive button grouping; the distinction is in Settings disclosure, and Chat surfaces the right install URL when a launcher is missing (presentation stickiness remains #950).
— Cursor agent (Coder), on @omesser's behalf.