Skip to content

feat(harness): Named preset for Goose (zero-npx, open-source local agent) #930

Closed

Description

@cursor

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

  1. launch() row — Add "goose" => (value, vec!["goose", "acp"]) to the match in harness.rs.
  2. Smoke test — AI_BUDDY_HARNESS=goose scripts/probe-harness.sh (or equivalent). Confirm initialize handshake and tool list.
  3. README Harness Support table — Add Goose row (already noted in launch() comment "Keep the README Harness Support table in step").
  4. Settings preset — If Settings Harness picker has a dropdown/list, add Goose option (same as claude/codex/hermes/etc.).
  5. Chat landing button — If connect landing shows per-harness buttons, add Goose (same tier as other named presets).
  6. Install URL for missing-binary message — When goose binary 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") returns Launch { name: "goose", argv: ["goose", "acp"] }.
  • probe-harness.sh with AI_BUDDY_HARNESS=goose completes 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

— Cursor agent, on @omesser's behalf.

Activity

  1. added this to the V1 milestone on Sep 23, 2026
  2. added
    enhancementNew feature or request
    p2Eventually: real, but nothing waits on it
    on Sep 23, 2026
  3. moved this from Todo to In Progress in Fidgeton Sep 23, 2026
  4. moved this from In Progress to Done in Fidgeton Sep 24, 2026
  5. omesser commented on Sep 24, 2026

    @omesser
    Owner

    Shipped on main via #971 (e35fd823).

    Acceptance vs main:

    • launch("goose") → goose acp (unit-tested in harness.rs)
    • Fresh + resumed turn smoked (AI_BUDDY_HARNESS=goose scripts/probe-harness.sh, goose 1.51.0, exit 0 both)
    • README Harness Support session + tools rows filled
    • Settings AI-source picker (HARNESS_PRESETS includes goose) and Chat connect landing button present
    • Missing-binary message points at https://goose-docs.ai/docs/getting-started/installation/

    Out 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestp2Eventually: real, but nothing waits on it

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions