Configuration cookbook¶
Complete files, one for each thing people set up most, each with what its lines do. Copy
one, change the names that are yours, and troupe config shows what is in effect.
Every file here is loaded by a test (apps/troupe_core/test/troupe/config/cookbook_test.exs)
through the reader Troupe itself uses for it, the strict one for config.yaml, which
refuses a wrong type and warns on a key it does not know: a recipe that stopped loading
would fail the build, not you.
Where each file goes is on one page, Where your files are; every key is in the key reference.
| Recipe | The file |
|---|---|
| Anthropic, the smallest useful file | config.yaml |
| OpenAI | config.yaml |
| A gateway, such as LiteLLM | config.yaml |
| Ollama, on your own machine | config.yaml |
| Azure OpenAI | config.yaml |
| OpenRouter | config.yaml |
| Gemini | config.yaml |
| A team's project file | .troupe/config.yaml |
| A personal config.local.yaml | .troupe/config.local.yaml |
| MCP servers | mcp.json |
| A custom agent | agents/<name>.md |
| A skill | skills/<name>/SKILL.md |
| An unattended session, its budgets and approvals | config.yaml |
| Per-tool permission rules | config.yaml |
Not here: Bedrock and Vertex, which are not provider types (each signs its requests with its own cloud's credentials; a gateway in front of either is the type of the API the gateway speaks).