StackMap
Subscribe

goose vs tau

General-purpose local AI agent in Rust — native desktop app, full CLI and embeddable API — over 15+ providers and 70+ MCP extensions. Block's goose, now an Agentic AI Foundation project. — versus — Hugging Face's Python port of Pi's minimalist coding agent: a real terminal agent with TUI, sessions and skills — built to be READ, with a clean brain/environment/frontend separation.

The curated verdict

Opposite ends of the same axis. Tau is a minimalist Python agent built to be read, with a clean brain/environment/frontend split; goose is a batteries-included Rust product you install and use. Read tau to learn, run goose to work.

goosetau
Stars54k2.5k
Forks6.1k304
LanguageRustPython
LicenseApache-2.0MIT
Last activitytodayyesterday
Topicsagents, codingcoding, agents
Curated connections53

goose — the curator's take

The default answer when someone wants a real agent on their own machine and does not want to assemble one. Rust, three surfaces (desktop app, CLI, API), 15+ providers including Ollama and your existing Claude/ChatGPT/Gemini subscriptions over ACP, 70+ MCP extensions, and custom distributions if you want to ship your own branded build. Now governed under the Linux Foundation's AAIF rather than one vendor, which matters if you are betting a product on it. It is deliberately general — code, research, writing, data — so it has no opinion about your SDLC: no verification gates, no worktree isolation, no PR pipeline. If you want an agent that must prove its work, or a spec-to-PR factory, layer that on or pick a purpose-built harness. Note the repo moved from block/goose; old links and forks still point at the old org.

tau — the curator's take

The teaching codebase for how coding agents are shaped: tau_ai (provider-neutral streaming) → tau_agent (the portable brain: loop, tools, events, sessions) → tau_coding (the actual app). That boundary discipline — the core knows nothing about rendering or config paths — is the lesson most production harnesses can't teach because they've already violated it. And unlike a toy, it's a usable daily agent with durable sessions. NOT the benchmark baseline (that's mini-swe-agent's 100 lines) and not the feature-race winner — no MCP sprawl by design. Read tau to understand the architecture; read mini to understand the loop; use whatever you like after.