DevAgentRadar → Goose

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: Goose Proposal: Route Goose Desktop through the ACP state-machine loop after v1.51.0 Summary: Goose v1.51.0 routes Desktop to a state-machine loop via ACP prompt meta, connects external ACP sockets to redirect-resolved backend URLs, and shows real backend failures plus failed tool-call output. Adopt that loop, opt in to the turn-complete bell, and stop using removed CLI planning-mode and create-recipe commands. Primary source: https://github.com/aaif-goose/goose/releases/tag/v1.51.0

Why it matters

Goose v1.51.0 routes Desktop to a state-machine loop via ACP prompt meta and connects external backend ACP sockets to the redirect-resolved backend URL. Connection failures now report their real cause, resource links that cannot be inlined are preserved in ACP, failed tool-call output appears in Desktop, and an opt-in terminal bell can fire when a turn finishes or approval is needed. Those changes make the Desktop loop observable instead of a black box.

The release is also breaking for CLI users: planning mode and the create-recipe command were removed, auto-compact 100% is treated as disabled, and goose doctor requires the Developer extension. Recipes should be built from one validated snapshot, validated consistently in the scheduler, with recipe-before-inference ordering guarded on scheduled runs. Gateway pairing adds an operator allowlist and protected pairing codes, plus restricted session storage permissions. Upgrade, switch Desktop onto the ACP loop, and replace the removed CLI and recipe paths before scheduled or headless jobs fail.

Suggested actions

1. Upgrade Goose Desktop and CLI to v1.51.0. Confirm Desktop routes sessions to the state-machine loop via ACP prompt meta, and reconnect any external backend ACP socket to the redirect-resolved backend URL, not the pre-redirect host.
2. On the next external backend connection failure, use the real cause Goose now reports; do not retry against a stale URL. Preserve ACP resource links that cannot be inlined instead of stripping them.
3. In Goose Desktop, opt in to the terminal bell for turn-finished and approval-needed events. When a tool fails, read the tool output now shown in Desktop before issuing the same call again.
4. Remove scripts or aliases that pass CLI planning mode or run the Goose create-recipe command; both were removed in v1.51.0. Build each recipe from one validated snapshot, let the scheduler validate it consistently, and keep recipe-before-inference ordering on scheduled runs.
5. Set Goose auto-compact to a threshold below 100% so compaction still runs (100% is now treated as disabled). Enable the Developer extension before running goose doctor. Add an operator allowlist for gateway pairing and treat pairing codes as secrets.

Config surfaces this release may change

• permission rules — check your repo before applying
• context and compaction settings — check your repo before applying
• MCP servers — check your repo before applying
• background and headless runs — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/goose-v1-51-0-route-goose-desktop-through-the-acp-state-machine-loop-aft and mark Applied, Skipped, or Failed. Proposal id: 8b268105-3343-4a4f-a839-9b965c676b8b

Your job

1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.