Expand description
Layered configuration.
Later layers win, field by field:
- built-in defaults
~/.mecha/config.toml./mecha.tomlin the working directory (project-local)- environment variables
- CLI flags (applied by the caller, not here)
Structs§
- Agent
Config - Capability
Override - Capabilities to force on a server’s tools. Absent flags leave the server’s own declaration alone; there is deliberately no way to switch one off.
- Config
- Hook
Config - One hook: a command run at a lifecycle point, with the event payload as JSON on stdin.
- McpServer
Config - Messages
Config - Messaging between this machine’s own mecha sessions.
- Outbox
Config - Which tools are outbox-routed, and where staged items live.
- Provider
Config - Search
Backend Config - Security
Config - Defenses against the lethal trifecta: private data, untrusted content, and a way to send data out. An agent holding all three can be turned into an exfiltration tool by instructions hidden in the content it reads — a calendar invite title, an email footer, a web page.
- Skills
Config - Which skills a run carries.
- Slack
Config [slack]— tunables for the Slack remote control. Nothing here grants anything. Who may drive the agent lives in~/.mecha/slack/binding.json, a store rather than config, for the reason[messages]is global-only and then some: a project file arrives with a cloned repository, and a repo that could name a Slack owner would have been handed the remote control.- Tools
Config - WebConfig
- Tunables for
mecha serve— the tailnet web surface. - Work
Config - How much of a producer’s generated output survives a
mecha work clean.