e7cca59089
- Update submodules: core (remove MCP, add tests), 9p (remove mcp file) - Add doc/NO_MCP.md: justification for removing MCP - Add observation to doc/OBSERVATIONS.md - Update ARCHITECTURE.md, help.md, SYSTEM_PROMPT.md, agents/README.md |
||
|---|---|---|
| .. | ||
| README.md | ||
| coding.json | ||
| default.json | ||
| devops.json | ||
| greybeard.json | ||
| qa.json | ||
| reviewer.json | ||
| writer.json | ||
README.md
Agents
Each .json file defines an agent configuration. Agent configs are installed to ~/.config/ollie/agents/ and selected at runtime via /agent <name>.
default
Base agent with no specializations. Provides the standard ollie toolset and hook wiring. Use this as the starting point when creating a new agent — copy default.json and add a prompt and any additional configuration.
coding
Coding-focused agent. Extends default with agent instructions covering code modification discipline, security practices, and exploratory reading habits. Also enables the execute_elevated_bash trusted tool for operations requiring elevated privileges.
System prompt
There is no built-in system prompt. The system prompt is assembled entirely from agentSpawn hook output. Both agents use $OLLIE/x/prime <name> to inject prompt template files from p/. coding additionally injects tools-elevate (relevant only with execute_elevated_bash) and omits it from default.
bd prime is appended last in both agents — it injects the active beads context if a database is found, and silently does nothing otherwise.
The fully assembled system prompt is visible at s/<id>/systemprompt.
Adding a new agent
Copy default.json, rename it, and adjust the agentSpawn hook array to include the prime calls you want. Add a prompt field for agent-specific instructions appended after the hook-injected context. Hooks, trusted tools, and generation parameters can all be customized per agent.