ollie/agents
Levi Neely c8d026a3da agents: coding prompt add good output criteria 2026-04-20 22:40:01 +02:00
..
README.md prompts: rename p/ files; drop OLLIE_PLAN_PATH and pl/ references 2026-04-19 20:09:50 +02:00
coding.json agents: coding prompt add good output criteria 2026-04-20 22:40:01 +02:00
default.json agents: move sys-* prompts to preTurn 2026-04-20 22:34:53 +02:00

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, MCP servers, and generation parameters can all be customized per agent.