Many hosted and local providers can sit behind the same local agent surfaces.
Agent Atlas / Coding agents
aaif-goose/goose
A local, general-purpose agent with desktop, CLI, and API surfaces, broad provider support, and an extension model built around MCP.
Coding agent
Full dossier
Project documented
Reviewed July 21, 2026
Intended operator
People using a local agent for coding, research, automation, and other tool-using work.
Primary surfaces
desktop app / CLI / embeddable API
Tracked repository
Teaching mechanism
MCP extensions separate the local agent from its external capabilities
The project documents a local Rust agent that connects provider choices and external capabilities through standard extension contracts instead of baking every integration into one model path.
Evidence limitREADME-level extension counts do not prove consistent credential scope, approval behavior, or reliability across extensions.
Inspect the source
System Map
Eight inspection boundariesLocal sessions and extension-provided context shape the run; retention details require deeper inspection.
MCP extensions supply tools for coding and broader workflows to a Rust runtime.
Local execution makes host authority and each extension's credentials central inspection questions.
Desktop, CLI, and API continuity require a shared session contract that remains to be traced.
The current profile does not claim a worker hierarchy without deeper source inspection.
Desktop and CLI surfaces give the operator different ways to inspect and steer local work.
The public Rust source, self-test configuration, diagnostics, releases, and docs provide the starting receipts.
Learn Through This Project
9 lessons
Chapter 1
Before the First Model Request
Chapter 2
The Invisible Prompt
Chapter 3
Tool Calls: Contract, Authorization, Execution
Chapter 4
Loops, Workflows, and Recovery
Chapter 6
Memory Is a Typed Storage Contract
Chapter 7
The Approval Trap
Chapter 8
The Human Control Loop
Chapter 9
Trust Must Make Its Case
Chapter 10
The Future Has Three Branches
Latest Reporting
0 articlesNo Daily Edition reporting is attached yet.
Open Questions
- Can every extension make its credentials, approval requirements, and side effects legible across desktop, CLI, and API use?
Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.