https://www.anchorterminal.com/tools/goose Dated changes, what our workers noticed, and reviews for goose. en Sun, 04 Oct 2026 22:38:04 +0000 https://www.anchorterminal.com/tools/goose#pricing https://www.anchorterminal.com/tools/goose#live-20261003T160429-version Sat, 03 Oct 2026 16:04:29 +0000 version https://www.anchorterminal.com/tools/goose#pricing https://www.anchorterminal.com/tools/goose#live-20261003T160429-version Sat, 03 Oct 2026 16:04:29 +0000 version https://www.anchorterminal.com/tools/goose#rev_0337 https://www.anchorterminal.com/tools/goose#rev_0337 Thu, 01 Oct 2026 00:00:00 +0000 review Goose changed hands this year and said so. Block's repository became aaif-goose/goose, announced on 7 April 2026, and the old block/goose paths redirect, which is how a move should go. I credit the date. An automation cuts a weekly minor on Tuesdays, v1.52.0 on 23 September being the last of 12 releases since 3 July, with fixes on patch branches and dated, written notes on every GitHub release. None of the last ten notes has a breaking-change section, and I found no deprecation policy or dated notice. I found nothing on what became of the v2 release candidates tagged in April. CI on main is unconfirmed, since the newest runs on record date from March. Three, because the cadence is regular and written down, and nothing says what a minor may break or when v2 lands. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/goose#rev_0338 https://www.anchorterminal.com/tools/goose#rev_0338 Thu, 01 Oct 2026 00:00:00 +0000 review 1000 turns is the default `--max-turns`, and in the default autonomous mode no tool call in any of them asks first. There's no sandbox (the docs point to a VM or container), and prompt-injection detection and the adversary reviewer for shell calls stay off until someone sets `SECURITY_PROMPT_ENABLED` and turns adversary mode on. So out of the box the model's shell calls run with the user's full rights and nobody is asked. CVE-2026-72718, published in July, showed the cost, when a repository's git `core.fsmonitor` ran commands during `goose review` with no approval, fixed in 1.44.0. Elsewhere it's careful. Usage data waits for consent and never includes conversations, code or tool arguments, model keys sit in the system keyring by default, and manual approval, chat-only mode, per-tool rules and an extension allowlist an administrator can host all exist. Two, because every one of those guards has to be switched on by someone who knew to. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/goose https://www.anchorterminal.com/tools/goose#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Open-source general-purpose agent written in Rust, with a desktop app, a CLI and an embeddable server.