Repository navigation
Closed
Labels
enhancementNew feature or requestNew feature or requestp2Eventually: real, but nothing waits on itEventually: real, but nothing waits on it
Milestone
Description
What
Add a named goose preset to launch() (src-tauri/src/harness.rs) so users can attach Goose without custom argv. Command: goose acp.
Why now
#735 census identified Goose as a high-value zero-npx candidate:
- Binary distribution in ACP registry (no Node/npx required).
- Open-source local agent (Block, strong "local agent" positioning).
- Already works via custom argv; named preset removes friction.
Scope
In
launch()row — Add"goose" => (value, vec!["goose", "acp"])to the match in harness.rs.- Smoke test —
AI_BUDDY_HARNESS=goose scripts/probe-harness.sh(or equivalent). Confirminitializehandshake and tool list. - README Harness Support table — Add Goose row (already noted in launch() comment "Keep the README Harness Support table in step").
- Settings preset — If Settings Harness picker has a dropdown/list, add Goose option (same as claude/codex/hermes/etc.).
- Chat landing button — If connect landing shows per-harness buttons, add Goose (same tier as other named presets).
- Install URL for missing-binary message — When
goosebinary not on PATH, error should say "Install Goose from https://... to use Goose." (Find correct install URL from https://block.xyz/ or Goose docs.)
Out
- Bundling the Goose binary (declare only; user installs via their package manager or from Block).
- Other registry agents (junie, kimi, etc. — separate issues if desired).
Done when
-
launch("goose")returnsLaunch { name: "goose", argv: ["goose", "acp"] }. -
probe-harness.shwithAI_BUDDY_HARNESS=goosecompletes a turn (or documents failure mode if Goose ACP has quirks). - README Harness Support table includes Goose.
- Settings and Chat landing present Goose as a named option (if UI has preset picker).
- Missing-binary error names correct install URL.
Related
- spike(ship): Census of runtime deps beyond the binary — self-contain or present cleanly #735 — runtime deps census (parent spike; this is follow-up for zero-npx named preset)
- Attaching real harnesses: per-harness MCP client config for Claude Code, opencode, Hermes, Pi, and Grok #166 / spike(harness): Integrate and test OpenAI Codex CLI as a Harness (ACP?) #554 — harness attach / Codex (precedent for named preset process)
- ACP Registry: https://cdn.agentclientprotocol.com/registry/v1/latest/registry.json (goose entry, binary distribution)
— Cursor agent, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestp2Eventually: real, but nothing waits on itEventually: real, but nothing waits on it
Projects
- StatusShow more project fieldsDone
Activity
docs(research): Record Oded's locked decisions for runtime deps
docs(research): Record all Oded's locked decisions for runtime deps
refactor: Keep Goose as custom argv only, remove from named presets
omesser commentedon Sep 24, 2026
Shipped on main via #971 (
e35fd823).Acceptance vs main:
launch("goose")→goose acp(unit-tested inharness.rs)AI_BUDDY_HARNESS=goose scripts/probe-harness.sh, goose 1.51.0, exit 0 both)HARNESS_PRESETSincludesgoose) and Chat connect landing button presentOut of this issue (and not claimed by #971): whether ai-buddy’s own MCP tools reach a Goose session under a real attach.
— Cursor agent (Coder), on @omesser's behalf.