Busabase x Knowledge Base for Zoo CodeKnowledge Base for Zoo Code
Zoo Code uses specialized modes to change how an agent plans, edits, debugs, or answers. Every change lands as a diff for review, while MCP adds external capability. A mode can constrain behavior, but a diff still needs a human decision.
MAP
Modes shape the work; diffs make the work reviewable; approval makes it durable.
Zoo Code uses specialized modes to change how an agent plans, edits, debugs, or answers. Every change lands as a diff for review, while MCP adds external capability. A mode can constrain behavior, but a diff still needs a human decision.
Code, Architect, Ask, Debug, or custom rules
Strategy, file map, and intended changes
Exact file changes before they land
External database, API, or resource
BOUNDARY
Zoo Code distinguishes planning from editing through modes
Modes shape the work; diffs make the work reviewable; approval makes it durable.
| Mode | Code, Architect, Ask, Debug, or custom rules | A task-specific behavior contract |
|---|---|---|
| Plan output | Strategy, file map, and intended changes | A reviewable proposal before edits |
| Diff | Exact file changes before they land | Evidence of what the agent actually did |
| MCP tool | External database, API, or resource | Capability with its own trust boundary |
SCOPE
Changes are presented as diffs before touching the codebase
Zoo Code uses specialized modes to change how an agent plans, edits, debugs, or answers. Every change lands as a diff for review, while MCP adds external capability. A mode can constrain behavior, but a diff still needs a human decision.
A task-specific behavior contract
A reviewable proposal before edits
Evidence of what the agent actually did
Capability with its own trust boundary
EVIDENCE
MCP extends tools but does not replace repository review
Zoo Code distinguishes planning from editing through modes Changes are presented as diffs before touching the codebase MCP extends tools but does not replace repository review
| Mode | Code, Architect, Ask, Debug, or custom rules | A task-specific behavior contract |
|---|---|---|
| Plan output | Strategy, file map, and intended changes | A reviewable proposal before edits |
| Diff | Exact file changes before they land | Evidence of what the agent actually did |
| MCP tool | External database, API, or resource | Capability with its own trust boundary |
ACCEPTANCE
Modes shape the work; diffs make the work reviewable; approval makes it durable.
Zoo Code distinguishes planning from editing through modes Changes are presented as diffs before touching the codebase MCP extends tools but does not replace repository review
Verify Code, Architect, Ask, Debug, or custom rules before accepting A task-specific behavior contract.
Verify Strategy, file map, and intended changes before accepting A reviewable proposal before edits.
Verify Exact file changes before they land before accepting Evidence of what the agent actually did.
Verify External database, API, or resource before accepting Capability with its own trust boundary.
FAQ
Knowledge Base for Zoo Code: practical questions
Modes shape the work; diffs make the work reviewable; approval makes it durable.
Does Architect mode change the repository?
Its purpose is to plan and produce a strategy or file map before code changes. Verify the handoff before implementation.
Is seeing a diff enough to approve it?
No. A diff shows the proposed mutation; tests, ownership, and product context still matter.
Are custom modes shared policies?
They are configuration. Treat a custom mode as policy only after reviewing its prompt, permissions, and scope.
Does MCP make external data authoritative?
No. It makes a resource available. Provenance and validation remain separate.
NEXT
Modes shape the work; diffs make the work reviewable; approval makes it durable.
Zoo Code uses specialized modes to change how an agent plans, edits, debugs, or answers. Every change lands as a diff for review, while MCP adds external capability. A mode can constrain behavior, but a diff still needs a human decision.