# goose vs Traycer (slim)

> goose scores 71.3 (BB) to Traycer's 57 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/goose-vs-traycer.md (~5,700 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/goose-vs-traycer.json · canonical https://www.anchorterminal.com/compare/goose-vs-traycer
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

goose scores 71.3 (BB) on agent readiness against Traycer's 57 (C), and leads in every scored category. Both do agent harnesses.

- goose: BB 71.3, rank #166 of 1510 · https://www.anchorterminal.com/tools/goose.min.md
- Traycer: C 57, rank #816 of 1510 · https://www.anchorterminal.com/tools/traycer.min.md
- goose, good for People and pipelines that want one agent across many model providers or local models, with recipes for repeatable jobs and a desktop app for non-engineers. Ahead on Reliability, 77 against 65; Schema & documentation, 81 against 65; Agent ergonomics, 82 against 65; Security & auth, 77 against 42; Payments & pricing, 60 against 30; Maintenance & community, 86 against 75; Transparency & trust, 67 against 60. Also Agent-ready, a grade of BB or better; Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Also No incidents deducted, where goose loses 5 points for them.

| Category | goose | Traycer |
| --- | --- | --- |
| Reliability (16%) | 77 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 65 |
| Agent ergonomics (13%) | 82 | 65 |
| Security & auth (14%) | 77 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 75 |
| Transparency & trust (7%) | 67 | 60 |

| Fact (where they differ) | goose | Traycer |
| --- | --- | --- |
| Vendor | Agentic AI Foundation (originally Block) | Traycer AI |
| Licence | Apache-2.0 | MIT |
| llms.txt | yes | no |
| Last release | 2026-10-27 | 2026-11-06 |
| Popularity | 55k stars | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Security & auth, goose +35: goose 77 (Harness reading of the framework checklist, used for all five harnesses in this batch. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Usage data is off until the user agrees on first use, and the docs list what's collected and what isn't (30). Four modes (autonomous, smart approval, manual approval, chat only), per-tool always, ask or never rules, and an extension allowlist fetched from `GOOSE_ALLOWLIST`, which from 1.57.0 must be HTTPS and blocks installs when the policy can't be read, but autonomous is the default (the first-run prompt for the mode still preselects Auto in 1.57.0) and there's no sandbox, with the docs pointing to a VM or container (11). Pattern and optional ML prompt-injection detection and an adversary reviewer for shell calls, both off until turned on, plus a prompt-injection caution in SECURITY.md (11). Session logs, a diagnostics report and a Langfuse tracing guide (12). SECURITY.md with GitHub private reporting and an AAIF governance contact, one advisory published with a CVE, and a Scorecard workflow. A second CVE, CVE-2026-109561 (low, Manual Approval bypassed by persisted read-only annotations after Smart Approval, fixed in 1.44.0), was published by NVD on 12 October from a third party, with no goose advisory of its own. No bug bounty, and goose-docs.ai/.well-known/security.txt returned 404 on 6 and 17 October and 1 November (13).); Traycer 42 (Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.)
- Payments & pricing, goose +30: goose 60 (No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines. It runs local models, including built-in local inference, with no signup.); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Agent ergonomics, goose +17: goose 82 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The built-in extensions are few, and Code Mode lets the model find MCP tools through code instead of loading every definition (23). `--max-turns` (default 1000), `GOOSE_MAX_TOKENS` and automatic context compaction, though 1000 turns is a high default for an unattended run (16). `goose run --output-format json` or `stream-json` for scripts (15). Recipes can retry with success checks and an `on_failure` command, and sessions resume (17). A Rust core with Python and Java SDK builds, and one command runs a task, but a provider has to be configured first and the default mode approves everything (11).); Traycer 65 (Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).)
- Schema & documentation, goose +16: goose 81 (Recipes have a documented schema with typed parameters and a `response` JSON Schema for structured output, and config and environment variables are documented in tables, but we found no OpenAPI spec for the goose server (18). llms.txt at goose-docs.ai, which now covers goose and the goose Development Kit (10). Permission modes come with a best-for column and the security pages say what each guard catches and misses (15). Recipe parameters take types and requirement levels, and retries take typed success checks (12). Many tutorials, a headless guide that tells scripts to check exit codes, and a known-issues page (13). Dated, written notes on every GitHub release, with no changelog file (13).); Traycer 65 (Harness reading. Mintlify docs, a protocol package and a CLI (65).)
- Reliability, goose +12: goose 77 (Read as a local package, which is how the 1 October dossier read it. Desktop builds and a CLI for macOS, Linux and Windows (a Windows NSIS installer from 1.56.0), Homebrew casks, a download script on GitHub releases, an npm package that installs the binary (@aaif/goose-acp) and a GHCR image, with Rust 1.94.1 as the minimum for source builds (20). A CI workflow runs on every push to main, with cargo-deny, cargo-machete, MCP and tool-call conformance and an OpenSSF Scorecard job beside it. The Actions page loaded on 1 October showed only passing runs from March 2026, and GitHub pages refused our requests on 6 and 17 October and 1 November, so the current state is unconfirmed (18). 266 to 271 open issues on 1 October, many from that week with no reply, including open reports that the default mode approves every tool call (#12567) and that schedules can overwrite each other (#12613), per the 1 October check, not re-read since (15). Weekly minor releases with notes written by a release-notes workflow whose sections are `Features`, `Bug Fixes`, `Improvements` and `Documentation`, with no breaking-change section. 1.55.0 dropped background subagents (`delegate(..., async: true)` and `GOOSE_MAX_BACKGROUND_TASKS`) and 1.57.0 dropped the developer tools that delegated file reads and terminal commands to an ACP editor, each edited out of the code and docs with no earlier notice (9). 1.57, stable (15).); Traycer 65 (Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.)
- Maintenance & community, goose +11: goose 86 (v1.57.0 tagged on 27 October 2026, after v1.56.0 on 22 October (30). 13 releases in the 90 days from 3 August, 1.46.0 (11 August) to 1.57.0, about one a week, plus GDK alpha tags (20). Issues move through a public board with Inbox and Ready columns and some new reports get a label within a day, but many of the week's reports had no reply on 1 October, and pull requests that don't implement a Ready issue are closed, per the 1 October check, not re-read since (15). Desktop, CLI, npm and GHCR builds ship from the same tag, and Python and Java SDK builds run in CI (13). cargo-deny, cargo-machete, Dependabot and Scorecard workflows, every GitHub Action pinned to a commit SHA since 29 September, and jsonwebtoken removed on 26 October to stop ignoring its cargo-deny advisories, with the current CI state unconfirmed (8).); Traycer 75 (Commits on 6 November 2026 and host 1.5.3 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.)