Option A: Run the default agent
The fastest way to try docker-agent — no config file needed:Option B: Run a pre-built agent from the catalog
Pull and run a ready-made agent from the agent catalog — no YAML required:Option C: Write your own agent config
Create an agent.yaml
Create a file named This is the minimal structure every agent config requires:
agent.yaml in your working directory:agent.yaml
agents.root— the entry-point agent (the namerootis the default)model— the AI model inprovider/model-nameformatdescription— a short summary of what the agent doesinstruction— the system prompt that shapes the agent’s behavior
Add tools (optional)
Give your agent capabilities by adding toolsets. Here is an agent with filesystem access, shell execution, and step-by-step reasoning:
agent.yaml
Option D: Generate a config interactively
Usedocker agent new to scaffold a config file through prompts:
agent.yaml in the current directory. Run it with:
Non-interactive mode
Use--exec to run an agent without the TUI — useful for scripts and one-shot tasks:
--exec, the agent processes the prompt and exits. Combine with --hide-tool-calls for clean output or --json for machine-readable results.
Add more capabilities
Extend your agent with persistent memory and web search:agent.yaml
The
ref: docker:duckduckgo syntax runs the DuckDuckGo MCP server in a Docker container. This is the recommended way to use MCP tools — secure, isolated, and easy to configure. Requires Docker Desktop.What’s next
Understand agents
Learn how agents work and what you can configure.
Multi-agent systems
Build teams of collaborating agents.
Configuration reference
Full reference for all YAML options.
Troubleshooting
Debug tips and common fixes.