← Lab Experiment
Operator guide
Heart, mind, and senses: code named for the agent inside
Ouroboros uses a body metaphor because naming and structure affect how an agent navigates the code it has to inhabit.
The body metaphor is an attempt to make the runtime easier for the agent to place, traverse, and modify from the inside.
Words used here
- Psyche
- Five Markdown files that define who the agent is, loaded every turn. More →
- Bundle
- One folder holding an agent's identity, memory, and tools, so you can back it up and move it. More →
- Reorientation overhead
- What it costs, usually the human, to get an agent back on track after it loses the thread. More →
Ask your agent
Inspect the current Ouroboros codebase and explain the main body parts to me in plain English. Tell me what each top-level area does and why the naming matters.
Your agent walks the actual source tree — the answer reflects what's there right now.
What to ask next
- Which part of the body owns this behavior right now?
- How do habits and the inner dialog work together?
- How does the MCP server let dev tools talk to the agent?
- If I want to extend this safely, where should the change live?