From 58df09f05fb15e5e5f6313487594955d9d298555 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Wed, 4 Mar 2026 12:07:49 +0100 Subject: [PATCH 1/4] Update docs to rename cagent => docker agent Signed-off-by: Guillaume Tardif --- content/get-started/workshop/10_what_next.md | 4 +- content/guides/agentic-ai.md | 2 +- .../{lab-cagent.md => lab-docker-agent.md} | 25 +++-- content/manuals/_index.md | 4 +- .../ai/{cagent => docker-agent}/_index.md | 31 +++--- .../best-practices.md | 6 +- .../ai/{cagent => docker-agent}/evals.md | 18 +-- .../images/cagent-acp-zed.avif | Bin .../integrations/_index.md | 10 +- .../integrations/a2a.md | 18 +-- .../integrations/acp.md | 20 ++-- .../integrations/mcp.md | 24 ++-- .../{cagent => docker-agent}/local-models.md | 12 +- .../model-providers.md | 4 +- .../ai/{cagent => docker-agent}/rag.md | 12 +- .../reference/_index.md | 0 .../{cagent => docker-agent}/reference/cli.md | 104 +++++++++--------- .../reference/config.md | 4 +- .../reference/examples.md | 0 .../reference/toolsets.md | 4 +- .../sharing-agents.md | 12 +- .../ai/{cagent => docker-agent}/tutorial.md | 16 +-- content/manuals/ai/sandboxes/_index.md | 2 +- content/manuals/ai/sandboxes/agents/_index.md | 2 +- content/manuals/ai/sandboxes/agents/cagent.md | 24 ++-- content/manuals/ai/sandboxes/architecture.md | 2 +- content/manuals/ai/sandboxes/workflows.md | 2 +- content/manuals/desktop/release-notes.md | 2 +- data/summary.yaml | 2 +- 29 files changed, 185 insertions(+), 181 deletions(-) rename content/guides/{lab-cagent.md => lab-docker-agent.md} (67%) rename content/manuals/ai/{cagent => docker-agent}/_index.md (84%) rename content/manuals/ai/{cagent => docker-agent}/best-practices.md (96%) rename content/manuals/ai/{cagent => docker-agent}/evals.md (93%) rename content/manuals/ai/{cagent => docker-agent}/images/cagent-acp-zed.avif (100%) rename content/manuals/ai/{cagent => docker-agent}/integrations/_index.md (82%) rename content/manuals/ai/{cagent => docker-agent}/integrations/a2a.md (88%) rename content/manuals/ai/{cagent => docker-agent}/integrations/acp.md (88%) rename content/manuals/ai/{cagent => docker-agent}/integrations/mcp.md (92%) rename content/manuals/ai/{cagent => docker-agent}/local-models.md (92%) rename content/manuals/ai/{cagent => docker-agent}/model-providers.md (97%) rename content/manuals/ai/{cagent => docker-agent}/rag.md (97%) rename content/manuals/ai/{cagent => docker-agent}/reference/_index.md (100%) rename content/manuals/ai/{cagent => docker-agent}/reference/cli.md (79%) rename content/manuals/ai/{cagent => docker-agent}/reference/config.md (99%) rename content/manuals/ai/{cagent => docker-agent}/reference/examples.md (100%) rename content/manuals/ai/{cagent => docker-agent}/reference/toolsets.md (99%) rename content/manuals/ai/{cagent => docker-agent}/sharing-agents.md (84%) rename content/manuals/ai/{cagent => docker-agent}/tutorial.md (94%) diff --git a/content/get-started/workshop/10_what_next.md b/content/get-started/workshop/10_what_next.md index 3b7bdfb8ffb2..4d146111f974 100644 --- a/content/get-started/workshop/10_what_next.md +++ b/content/get-started/workshop/10_what_next.md @@ -35,9 +35,9 @@ ai-development: - title: MCP Toolkit description: Set up, manage, and run containerized MCP servers to power your AI agents. link: /ai/mcp-catalog-and-toolkit/toolkit/ -- title: Build AI agents with cagent +- title: Build AI agents with Docker Agent description: Create teams of specialized AI agents that collaborate to solve complex problems. - link: /ai/cagent/ + link: /ai/docker-agent/ - title: Use AI models in Compose description: Define AI model dependencies in your Docker Compose applications. link: /compose/how-tos/model-runner/ diff --git a/content/guides/agentic-ai.md b/content/guides/agentic-ai.md index d61a82023195..0ad9b8839007 100644 --- a/content/guides/agentic-ai.md +++ b/content/guides/agentic-ai.md @@ -13,7 +13,7 @@ params: > > This guide uses the familiar Docker Compose workflow to orchestrate agentic AI > applications. For a smoother development experience, check out [Docker -> cagent](../manuals/ai/cagent/_index.md), a purpose-built agent runtime that +> Docker Agent](../manuals/ai/docker-agent/_index.md), a purpose-built agent runtime that > simplifies running and managing AI agents. ## Introduction diff --git a/content/guides/lab-cagent.md b/content/guides/lab-docker-agent.md similarity index 67% rename from content/guides/lab-cagent.md rename to content/guides/lab-docker-agent.md index 2b6a7348c637..54a6202117b7 100644 --- a/content/guides/lab-cagent.md +++ b/content/guides/lab-docker-agent.md @@ -1,20 +1,21 @@ --- -title: "Lab: Getting Started with cagent" -linkTitle: "Lab: Getting Started with cagent" +title: "Lab: Getting Started with Docker Agent" +linkTitle: "Lab: Getting Started with Docker Agent" description: | - Build intelligent multi-agent teams with cagent and Docker in this hands-on + Build intelligent multi-agent teams with Docker Agent and Docker in this hands-on interactive lab. summary: | Hands-on lab: Create, share, and orchestrate intelligent AI agents using - cagent, MCP Toolkit, and Docker. -keywords: AI, Docker, cagent, agents, multi-agent, MCP Toolkit, lab, labspace + Docker Agent, MCP Toolkit, and Docker. +keywords: AI, Docker, docker agent, agents, multi-agent, MCP Toolkit, lab, labspace aliases: - /labs/docker-for-ai/cagent/ + - /guides/lab-cagent/ params: tags: [ai, labs] time: 20 minutes resource_links: - - title: cagent documentation + - title: Docker Agent documentation url: https://github.com/docker/cagent - title: Docker MCP Toolkit url: https://docs.docker.com/ai/mcp-catalog-and-toolkit/toolkit/ @@ -22,27 +23,27 @@ params: url: https://github.com/ajeetraina/labspace-cagent --- -This lab walks you through building intelligent agents with cagent. You'll learn beginner +This lab walks you through building intelligent agents with Docker Agent. You'll learn beginner agent concepts, then build sophisticated multi-agent teams that handle complex real-world tasks. Learn how to create, share, and orchestrate AI agents with Docker. ## What you'll learn -- Create simple agents with cagent +- Create simple agents with Docker Agent - Use built-in generic agentic tools for common tasks - Integrate MCP servers from the MCP Toolkit - Share agents using the Docker Registry - Build multi-agent systems for complex workflows -- Use Docker Model Runner with cagent (preview) +- Use Docker Model Runner with Docker Agent (preview) ## Modules | # | Module | Description | |---|--------|-------------| -| 1 | Introduction | Overview of cagent and intelligent agent concepts | -| 2 | Getting Started | Create your first agent with cagent | -| 3 | Using Built-in Tools | Leverage the generic agentic tools in cagent | +| 1 | Introduction | Overview of Docker Agent and intelligent agent concepts | +| 2 | Getting Started | Create your first agent with Docker Agent | +| 3 | Using Built-in Tools | Leverage the generic agentic tools in Docker Agent | | 4 | Using MCP | Integrate MCP servers from the MCP Toolkit | | 5 | Sharing Agents | Package and share agents via Docker Registry | | 6 | Introduction to Sub-agents | Build multi-agent systems with sub-agent orchestration | diff --git a/content/manuals/_index.md b/content/manuals/_index.md index ac5659e6e665..cf54d6eae1a8 100644 --- a/content/manuals/_index.md +++ b/content/manuals/_index.md @@ -32,10 +32,10 @@ params: description: Run containers programmatically in your preferred programming language. icon: /icons/Testcontainers.svg link: /testcontainers/ - - title: Cagent + - title: Docker Agent description: The open-source multi-agent solution to assist you in your tasks. icon: /icons/cagent.svg - link: /ai/cagent + link: /ai/docker-agent ai: - title: Ask Gordon description: Streamline your workflow and get the most out of the Docker ecosystem with your personal AI assistant. diff --git a/content/manuals/ai/cagent/_index.md b/content/manuals/ai/docker-agent/_index.md similarity index 84% rename from content/manuals/ai/cagent/_index.md rename to content/manuals/ai/docker-agent/_index.md index 17ec7493f12f..35c1f4759d74 100644 --- a/content/manuals/ai/cagent/_index.md +++ b/content/manuals/ai/docker-agent/_index.md @@ -1,19 +1,22 @@ --- -title: cagent -description: cagent lets you build, orchestrate, and share AI agents that work together as a team. +title: Docker Agent +description: Docker Agent lets you build, orchestrate, and share AI agents that work together as a team. weight: 60 +aliases: + - /ai/cagent/ + - /manuals/ai/cagent/ params: sidebar: group: Open source badge: color: violet text: Experimental -keywords: [ai, agent, cagent] +keywords: [ai, agent, docker agent, cagent] --- -{{< summary-bar feature_name="cagent" >}} +{{< summary-bar feature_name="Docker Agent" >}} -[cagent](https://github.com/docker/cagent) is an open source tool for building +[Docker Agent](https://github.com/docker/cagent) is an open source tool for building teams of specialized AI agents. Instead of prompting one generalist model, you define agents with specific roles and instructions that collaborate to solve problems. Run these agent teams from your terminal using any LLM provider. @@ -21,7 +24,7 @@ problems. Run these agent teams from your terminal using any LLM provider. ## Why agent teams One agent handling complex work means constant context-switching. Split the work -across focused agents instead - each handles what it's best at. cagent manages +across focused agents instead - each handles what it's best at. Docker Agent manages the coordination. Here's a two-agent team that debugs problems: @@ -58,7 +61,7 @@ its specialty. ## Installation -cagent is included in Docker Desktop 4.49 and later. +Docker Agent is included in Docker Desktop 4.49 and later. For Docker Engine users or custom installations: @@ -66,7 +69,7 @@ For Docker Engine users or custom installations: - **Winget**: `winget install Docker.Cagent` - **Pre-built binaries**: [GitHub releases](https://github.com/docker/cagent/releases) -- **From source**: See the [cagent +- **From source**: See the [Docker Agent repository](https://github.com/docker/cagent?tab=readme-ov-file#build-from-source) ## Get started @@ -86,7 +89,7 @@ Try the bug analyzer team: 3. Run your agent team: ```console - $ cagent run debugger.yaml + $ docker agent run debugger.yaml ``` You'll see a prompt where you can describe bugs or paste error messages. The @@ -138,8 +141,8 @@ Agent configurations are packaged as OCI artifacts. Push and pull them like container images: ```console -$ cagent push ./debugger.yaml myusername/debugger -$ cagent pull myusername/debugger +$ docker agent push ./debugger.yaml myusername/debugger +$ docker agent pull myusername/debugger ``` Use Docker Hub or any OCI-compatible registry. Pushing creates the repository if @@ -149,11 +152,11 @@ it doesn't exist yet. - Follow the [tutorial](./tutorial.md) to build your first coding agent - Learn [best practices](./best-practices.md) for building effective agents -- Integrate cagent with your [editor](./integrations/acp.md) or use agents as +- Integrate Docker Agent with your [editor](./integrations/acp.md) or use agents as [tools in MCP clients](./integrations/mcp.md) -- Browse example agent configurations in the [cagent +- Browse example agent configurations in the [Docker Agent repository](https://github.com/docker/cagent/tree/main/examples) -- Use `cagent new` to generate agent teams with AI - Connect agents to external tools via the [Docker MCP Gateway](/manuals/ai/mcp-catalog-and-toolkit/mcp-gateway.md) diff --git a/content/manuals/ai/cagent/best-practices.md b/content/manuals/ai/docker-agent/best-practices.md similarity index 96% rename from content/manuals/ai/cagent/best-practices.md rename to content/manuals/ai/docker-agent/best-practices.md index 0b06ab29162f..550247864c74 100644 --- a/content/manuals/ai/cagent/best-practices.md +++ b/content/manuals/ai/docker-agent/best-practices.md @@ -1,11 +1,11 @@ --- title: Best practices -description: Patterns and techniques for building effective cagent agents -keywords: [cagent, best practices, patterns, agent design, optimization] +description: Patterns and techniques for building effective Docker Agent agents +keywords: [docker agent, best practices, patterns, agent design, optimization] weight: 40 --- -Patterns you learn from building and running cagent agents. These aren't +Patterns you learn from building and running Docker Agent agents. These aren't features or configuration options - they're approaches that work well in practice. diff --git a/content/manuals/ai/cagent/evals.md b/content/manuals/ai/docker-agent/evals.md similarity index 93% rename from content/manuals/ai/cagent/evals.md rename to content/manuals/ai/docker-agent/evals.md index dabc28cbae6d..6824a9ca4963 100644 --- a/content/manuals/ai/cagent/evals.md +++ b/content/manuals/ai/docker-agent/evals.md @@ -1,7 +1,7 @@ --- title: Evals description: Test your agents with saved conversations -keywords: [cagent, evaluations, testing, evals] +keywords: [docker agent, evaluations, testing, evals] weight: 80 --- @@ -12,7 +12,7 @@ tell you if behavior changed, not whether it's right or wrong. ## What are evals -An eval is a saved conversation you can replay. When you run evals, cagent +An eval is a saved conversation you can replay. When you run evals, Docker Agent replays the user messages and compares the new responses against the original saved conversation. High scores mean the agent behaved similarly; low scores mean behavior changed. @@ -48,7 +48,7 @@ bad. Save a conversation from an interactive session: ```console -$ cagent run ./agent.yaml +$ docker agent run ./agent.yaml ``` Have a conversation with your agent, then save it as an eval: @@ -66,25 +66,25 @@ directory. You can organize eval files in subdirectories if needed. Run all evals in the default directory: ```console -$ cagent eval ./agent.yaml +$ docker agent eval ./agent.yaml ``` Use a custom eval directory: ```console -$ cagent eval ./agent.yaml ./my-evals +$ docker agent eval ./agent.yaml ./my-evals ``` Run evals against an agent from a registry: ```console -$ cagent eval agentcatalog/myagent +$ docker agent eval agentcatalog/myagent ``` Example output: ```console -$ cagent eval ./agent.yaml +$ docker agent eval ./agent.yaml --- 0 First message: tell me something interesting about kil Eval file: c7e556c5-dae5-4898-a38c-73cc8e0e6abe @@ -96,7 +96,7 @@ Output tokens: 177 ## Understanding results -For each eval, cagent shows: +For each eval, Docker Agent shows: - **First message** - The initial user message from the saved conversation - **Eval file** - The UUID of the eval file being run @@ -156,7 +156,7 @@ see what shifted. ## What's next -- Check the [CLI reference](reference/cli.md#eval) for all `cagent eval` +- Check the [CLI reference](reference/cli.md#eval) for all `docker agent eval` options - Learn [best practices](best-practices.md) for building effective agents - Review [example configurations](https://github.com/docker/cagent/tree/main/examples) diff --git a/content/manuals/ai/cagent/images/cagent-acp-zed.avif b/content/manuals/ai/docker-agent/images/cagent-acp-zed.avif similarity index 100% rename from content/manuals/ai/cagent/images/cagent-acp-zed.avif rename to content/manuals/ai/docker-agent/images/cagent-acp-zed.avif diff --git a/content/manuals/ai/cagent/integrations/_index.md b/content/manuals/ai/docker-agent/integrations/_index.md similarity index 82% rename from content/manuals/ai/cagent/integrations/_index.md rename to content/manuals/ai/docker-agent/integrations/_index.md index d6a23870b668..a31c04ffd265 100644 --- a/content/manuals/ai/cagent/integrations/_index.md +++ b/content/manuals/ai/docker-agent/integrations/_index.md @@ -1,7 +1,7 @@ --- title: Integrations -description: Connect cagent agents to editors, MCP clients, and other agents -keywords: [cagent, integration, acp, mcp, a2a, editor, protocol] +description: Connect Docker Agent agents to editors, MCP clients, and other agents +keywords: [docker agent, integration, acp, mcp, a2a, editor, protocol] weight: 60 --- @@ -12,7 +12,7 @@ want to use them. Each integration type serves a specific purpose. ### ACP - Editor integration -Run cagent agents directly in your editor (Neovim, Zed). The agent sees your +Run Docker Agent agents directly in your editor (Neovim, Zed). The agent sees your editor's file context and can read and modify files through the editor's interface. Use ACP when you want an AI coding assistant embedded in your editor. @@ -21,7 +21,7 @@ See [ACP integration](./acp.md) for setup instructions. ### MCP - Tool integration -Expose cagent agents as tools in MCP clients like Claude Desktop or Claude +Expose Docker Agent agents as tools in MCP clients like Claude Desktop or Claude Code. Your agents appear in the client's tool list, and the client can call them when needed. Use MCP when you want Claude Desktop (or another MCP client) to have access to your specialized agents. @@ -30,7 +30,7 @@ See [MCP integration](./mcp.md) for setup instructions. ### A2A - Agent-to-agent communication -Run cagent agents as HTTP servers that other agents or systems can call using +Run Docker Agent agents as HTTP servers that other agents or systems can call using the Agent-to-Agent protocol. Your agent becomes a service that other systems can discover and invoke over the network. Use A2A when you want to build multi-agent systems or expose your agent as an HTTP service. diff --git a/content/manuals/ai/cagent/integrations/a2a.md b/content/manuals/ai/docker-agent/integrations/a2a.md similarity index 88% rename from content/manuals/ai/cagent/integrations/a2a.md rename to content/manuals/ai/docker-agent/integrations/a2a.md index 1e51b9e80519..7bb58002169d 100644 --- a/content/manuals/ai/cagent/integrations/a2a.md +++ b/content/manuals/ai/docker-agent/integrations/a2a.md @@ -1,12 +1,12 @@ --- title: A2A mode linkTitle: A2A -description: Expose cagent agents via the Agent-to-Agent protocol -keywords: [cagent, a2a, agent-to-agent, multi-agent, protocol] +description: Expose Docker Agent agents via the Agent-to-Agent protocol +keywords: [docker agent, a2a, agent-to-agent, multi-agent, protocol] weight: 40 --- -A2A mode runs your cagent agent as an HTTP server that other systems can call +A2A mode runs your Docker Agent agent as an HTTP server that other systems can call using the Agent-to-Agent protocol. This lets you expose your agent as a service that other agents or applications can discover and invoke over the network. @@ -29,7 +29,7 @@ Before starting an A2A server, you need: Basic usage: ```console -$ cagent a2a ./agent.yaml +$ docker agent a2a ./agent.yaml ``` Your agent is now accessible via HTTP. Other A2A systems can discover your @@ -38,19 +38,19 @@ agent's capabilities and call it. Custom port: ```console -$ cagent a2a ./agent.yaml --port 8080 +$ docker agent a2a ./agent.yaml --port 8080 ``` Specific agent in a team: ```console -$ cagent a2a ./agent.yaml --agent engineer +$ docker agent a2a ./agent.yaml --agent engineer ``` From OCI registry: ```console -$ cagent a2a agentcatalog/pirate --port 9000 +$ docker agent a2a agentcatalog/pirate --port 9000 ``` ## HTTP endpoints @@ -142,7 +142,7 @@ Here's a concrete scenario where A2A is useful. You have two agents: Run the specialist as an A2A server: ```console -$ cagent a2a ./code-reviewer.yaml --port 8080 +$ docker agent a2a ./code-reviewer.yaml --port 8080 Listening on 127.0.0.1:8080 ``` @@ -198,7 +198,7 @@ agents: ## What's next -- Review the [CLI reference](../reference/cli.md#a2a) for all `cagent a2a` +- Review the [CLI reference](../reference/cli.md#a2a) for all `docker agent a2a` options - Learn about [MCP mode](./mcp.md) to expose agents as tools in MCP clients - Learn about [ACP mode](./acp.md) for editor integration diff --git a/content/manuals/ai/cagent/integrations/acp.md b/content/manuals/ai/docker-agent/integrations/acp.md similarity index 88% rename from content/manuals/ai/cagent/integrations/acp.md rename to content/manuals/ai/docker-agent/integrations/acp.md index f6e11bf7af22..d8e7c210a751 100644 --- a/content/manuals/ai/cagent/integrations/acp.md +++ b/content/manuals/ai/docker-agent/integrations/acp.md @@ -1,12 +1,12 @@ --- linkTitle: ACP title: ACP integration -description: Configure your editor or IDE to use cagent agents as coding assistants -keywords: [cagent, acp, editor, ide, neovim, zed, integration] +description: Configure your editor or IDE to use Docker Agent agents as coding assistants +keywords: [docker agent, acp, editor, ide, neovim, zed, integration] weight: 40 --- -Run cagent agents directly in your editor using the Agent Client Protocol (ACP). +Run Docker Agent agents directly in your editor using the Agent Client Protocol (ACP). Your agent gets access to your editor's filesystem context and can read and modify files as you work. The editor handles file operations while cagent provides the AI capabilities. @@ -26,7 +26,7 @@ to "add error handling" and it edits the code right in your editor. The agent works with your editor's view of the project, not some external file system it has to navigate. -The difference from running cagent in a terminal: file operations go through +The difference from running Docker Agent in a terminal: file operations go through your editor instead of the agent directly accessing your filesystem. When the agent needs to read or write a file, it requests it from your editor. This keeps the agent's view of your code synchronized with yours - same working directory, @@ -74,12 +74,12 @@ Zed has built-in ACP support. 2. Start a new external agent thread. Select your agent in the drop-down list. - ![New external thread with cagent in Zed](../images/cagent-acp-zed.avif) + ![New external thread with Docker Agent in Zed](../images/cagent-acp-zed.avif) ### Neovim Use the [CodeCompanion](https://github.com/olimorris/codecompanion.nvim) plugin, -which has native support for cagent through a built-in adapter: +which has native support for Docker Agent through a built-in adapter: 1. [Install CodeCompanion](https://codecompanion.olimorris.dev/installation) through your plugin manager. @@ -131,11 +131,11 @@ reference: ```console # Local file path -$ cagent acp ./agent.yml +$ docker agent acp ./agent.yml # OCI registry reference -$ cagent acp agentcatalog/pirate -$ cagent acp dockereng/myagent:v1.0.0 +$ docker agent acp agentcatalog/pirate +$ docker agent acp dockereng/myagent:v1.0.0 ``` Use the same syntax in your editor configuration: @@ -177,7 +177,7 @@ If the agent starts but can't access files or perform other actions, check: - Explore the [toolsets reference](../reference/toolsets.md) to learn what tools are available - Add [RAG for codebase search](../rag.md) to your agent -- Check the [CLI reference](../reference/cli.md) for all `cagent acp` options +- Check the [CLI reference](../reference/cli.md) for all `docker agent acp` options - Browse [example configurations](https://github.com/docker/cagent/tree/main/examples) for inspiration diff --git a/content/manuals/ai/cagent/integrations/mcp.md b/content/manuals/ai/docker-agent/integrations/mcp.md similarity index 92% rename from content/manuals/ai/cagent/integrations/mcp.md rename to content/manuals/ai/docker-agent/integrations/mcp.md index 1b51bb09349e..e32073a2701b 100644 --- a/content/manuals/ai/cagent/integrations/mcp.md +++ b/content/manuals/ai/docker-agent/integrations/mcp.md @@ -1,7 +1,7 @@ --- title: MCP mode linkTitle: MCP -description: Expose cagent agents as tools to MCP clients like Claude Desktop and Claude Code +description: Expose Docker Agent agents as tools to MCP clients like Claude Desktop and Claude Code keywords: [ cagent, @@ -76,7 +76,7 @@ Before configuring MCP integration, you need: ## MCP client configuration -Your MCP client needs to know how to start cagent and communicate with it. This +Your MCP client needs to know how to start Docker Agent and communicate with it. This typically involves adding cagent as an MCP server in your client's configuration. @@ -142,7 +142,7 @@ Command breakdown: - `myagent`: Name for this MCP server in Claude Code - `--env`: Pass environment variables (repeat for each variable) - `--`: Separates Claude Code options from the MCP server command -- `cagent mcp /path/to/agent.yml`: The cagent MCP command with the path to your +- `docker agent mcp /path/to/agent.yml`: The cagent MCP command with the path to your agent configuration - `--working-dir $(pwd)`: Set the working directory for agent execution @@ -153,8 +153,8 @@ sessions. For other MCP-compatible clients, you need to: -1. Start cagent with `cagent mcp /path/to/agent.yml --working-dir /project/path` -2. Configure the client to communicate with cagent over stdio +1. Start cagent with `docker agent mcp /path/to/agent.yml --working-dir /project/path` +2. Configure the client to communicate with Docker Agent over stdio 3. Pass required environment variables (API keys, etc.) Consult your MCP client's documentation for specific configuration steps. @@ -166,11 +166,11 @@ reference: ```console # Local file path -$ cagent mcp ./agent.yml +$ docker agent mcp ./agent.yml # OCI registry reference -$ cagent mcp agentcatalog/pirate -$ cagent mcp dockereng/myagent:v1.0.0 +$ docker agent mcp agentcatalog/pirate +$ docker agent mcp dockereng/myagent:v1.0.0 ``` Use the same syntax in MCP client configurations: @@ -193,7 +193,7 @@ managing local files. See [Sharing agents](../sharing-agents.md) for details. MCP clients see each of your agents as a separate tool and can call any of them directly. This changes how you should think about agent design compared to -running agents with `cagent run`. +running agents with `docker agent run`. ### Write good descriptions @@ -235,7 +235,7 @@ If an agent needs others to work properly, say so in the description: MCP clients call agents individually, so test them that way: ```console -$ cagent run agent.yml --agent engineer +$ docker agent run agent.yml --agent engineer ``` Make sure the agent works without going through root first. Check that it has @@ -272,7 +272,7 @@ it finds. You stay in Claude's interface the whole time. Your configuration has a coordinator that delegates to designer and engineer agents. Ask Claude Code "Use the coordinator to implement a login form" and the coordinator hands off UI work to the designer and code to the engineer. You get -a complete implementation without running `cagent run` yourself. +a complete implementation without running `docker agent run` yourself. ### Run domain-specific tools @@ -299,7 +299,7 @@ around. - Explore the [toolsets reference](../reference/toolsets.md) to learn what tools agents can use - Add [RAG for codebase search](../rag.md) to your agent -- Check the [CLI reference](../reference/cli.md) for all `cagent mcp` options +- Check the [CLI reference](../reference/cli.md) for all `docker agent mcp` options - Browse [example configurations](https://github.com/docker/cagent/tree/main/examples) for different agent types diff --git a/content/manuals/ai/cagent/local-models.md b/content/manuals/ai/docker-agent/local-models.md similarity index 92% rename from content/manuals/ai/cagent/local-models.md rename to content/manuals/ai/docker-agent/local-models.md index 33fa46ec102c..7ddc81f3740a 100644 --- a/content/manuals/ai/cagent/local-models.md +++ b/content/manuals/ai/docker-agent/local-models.md @@ -2,7 +2,7 @@ title: Local models with Docker Model Runner linkTitle: Local models description: Run AI models locally using Docker Model Runner - no API keys required -keywords: [cagent, docker model runner, dmr, local models, embeddings, offline] +keywords: [docker agent, docker model runner, dmr, local models, embeddings, offline] weight: 20 --- @@ -67,19 +67,19 @@ agents: - type: filesystem ``` -When you first run your agent, cagent prompts you to pull the model if it's +When you first run your agent, Docker Agent prompts you to pull the model if it's not already available locally: ```console -$ cagent run agent.yaml +$ docker agent run agent.yaml Model not found locally. Do you want to pull it now? ([y]es/[n]o) ``` ## How it works -When you configure an agent to use DMR, cagent automatically connects to your +When you configure an agent to use DMR, Docker Agent automatically connects to your local Docker Model Runner and routes inference requests to it. If a model isn't -available locally, cagent prompts you to pull it on first use. No API keys or +available locally, Docker Agent prompts you to pull it on first use. No API keys or authentication are required. ## Advanced configuration @@ -183,7 +183,7 @@ Native DMR reranking is the fastest option for reranking RAG results. ## Troubleshooting -If cagent can't find Docker Model Runner: +If Docker Agent can't find Docker Model Runner: 1. Verify Docker Model Runner status: diff --git a/content/manuals/ai/cagent/model-providers.md b/content/manuals/ai/docker-agent/model-providers.md similarity index 97% rename from content/manuals/ai/cagent/model-providers.md rename to content/manuals/ai/docker-agent/model-providers.md index de0a82893837..671a736dcab6 100644 --- a/content/manuals/ai/cagent/model-providers.md +++ b/content/manuals/ai/docker-agent/model-providers.md @@ -1,7 +1,7 @@ --- title: Model providers -description: Get API keys and configure cloud model providers for cagent -keywords: [cagent, model providers, api keys, anthropic, openai, google, gemini] +description: Get API keys and configure cloud model providers for Docker Agent +keywords: [docker agent, model providers, api keys, anthropic, openai, google, gemini] weight: 10 --- diff --git a/content/manuals/ai/cagent/rag.md b/content/manuals/ai/docker-agent/rag.md similarity index 97% rename from content/manuals/ai/cagent/rag.md rename to content/manuals/ai/docker-agent/rag.md index a9088bb69ba6..3fbd7ec6f041 100644 --- a/content/manuals/ai/cagent/rag.md +++ b/content/manuals/ai/docker-agent/rag.md @@ -1,16 +1,16 @@ --- title: RAG -description: How RAG gives your cagent agents access to codebases and documentation -keywords: [cagent, rag, retrieval, embeddings, semantic search] +description: How RAG gives your Docker Agent agents access to codebases and documentation +keywords: [docker agent, rag, retrieval, embeddings, semantic search] weight: 70 --- -When you configure a RAG source in cagent, your agent automatically gains a +When you configure a RAG source in Docker Agent, your agent automatically gains a search tool for that knowledge base. The agent decides when to search, retrieves only relevant information, and uses it to answer questions or complete tasks - all without you manually managing what goes in the prompt. -This guide explains how cagent's RAG system works, when to use it, and how to +This guide explains how Docker Agent's RAG system works, when to use it, and how to configure it effectively for your content. > [!NOTE] @@ -37,9 +37,9 @@ RAG indexes your content ahead of time and enables semantic search. The agent searches pre-indexed content by meaning, not exact words. It retrieves only relevant chunks that respect code structure. No wasted context on exploration. -## How RAG works in cagent +## How RAG works in Docker Agent -Configure a RAG source in your cagent config: +Configure a RAG source in your Docker Agent config: ```yaml rag: diff --git a/content/manuals/ai/cagent/reference/_index.md b/content/manuals/ai/docker-agent/reference/_index.md similarity index 100% rename from content/manuals/ai/cagent/reference/_index.md rename to content/manuals/ai/docker-agent/reference/_index.md diff --git a/content/manuals/ai/cagent/reference/cli.md b/content/manuals/ai/docker-agent/reference/cli.md similarity index 79% rename from content/manuals/ai/cagent/reference/cli.md rename to content/manuals/ai/docker-agent/reference/cli.md index b20e8846fcb3..f9e3e89b913a 100644 --- a/content/manuals/ai/cagent/reference/cli.md +++ b/content/manuals/ai/docker-agent/reference/cli.md @@ -1,8 +1,8 @@ --- title: CLI reference linkTitle: CLI -description: Complete reference for cagent command-line interface -keywords: [ai, agent, cagent, cli, command line] +description: Complete reference for Docker Agent command-line interface +keywords: [ai, agent, docker agent, cli, command line] weight: 30 --- @@ -15,7 +15,7 @@ reference](./toolsets.md). ## Synopsis ```console -$ cagent [command] [flags] +$ docker agent [command] [flags] ``` ## Global flags @@ -53,7 +53,7 @@ systems to discover and interact with your agent. Auto-selects an available port if not specified. ```console -$ cagent a2a agent-file|registry-ref +$ docker agent a2a agent-file|registry-ref ``` > [!NOTE] @@ -77,8 +77,8 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ cagent a2a ./agent.yaml --port 8080 -$ cagent a2a agentcatalog/pirate --port 9000 +$ docker agent a2a ./agent.yaml --port 8080 +$ docker agent a2a agentcatalog/pirate --port 9000 ``` ### acp @@ -87,7 +87,7 @@ Start agent as ACP (Agent Client Protocol) server on stdio for editor integratio See [ACP integration](../integrations/acp.md) for setup guides. ```console -$ cagent acp agent-file|registry-ref +$ docker agent acp agent-file|registry-ref ``` Arguments: @@ -101,7 +101,7 @@ Supports [runtime flags](#runtime-flags). Create alias for agent. ```console -$ cagent alias add name target +$ docker agent alias add name target ``` Arguments: @@ -112,20 +112,20 @@ Arguments: Examples: ```console -$ cagent alias add dev ./dev-agent.yaml -$ cagent alias add prod docker.io/user/prod-agent:latest -$ cagent alias add default ./agent.yaml +$ docker agent alias add dev ./dev-agent.yaml +$ docker agent alias add prod docker.io/user/prod-agent:latest +$ docker agent alias add default ./agent.yaml ``` -Setting alias name to "default" lets you run `cagent run` without arguments. +Setting alias name to "default" lets you run `docker agent run` without arguments. ### alias list List all aliases. ```console -$ cagent alias list -$ cagent alias ls +$ docker agent alias list +$ docker agent alias ls ``` ### alias remove @@ -133,8 +133,8 @@ $ cagent alias ls Remove alias. ```console -$ cagent alias remove name -$ cagent alias rm name +$ docker agent alias remove name +$ docker agent alias rm name ``` Arguments: @@ -146,7 +146,7 @@ Arguments: HTTP API server. ```console -$ cagent api agent-file|agents-dir +$ docker agent api agent-file|agents-dir ``` Arguments: @@ -166,9 +166,9 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ cagent api ./agent.yaml -$ cagent api ./agents/ --listen :9000 -$ cagent api docker.io/user/agent --pull-interval 10 +$ docker agent api ./agent.yaml +$ docker agent api ./agents/ --listen :9000 +$ docker agent api docker.io/user/agent --pull-interval 10 ``` The `--pull-interval` flag works only with OCI references. Automatically pulls and reloads at the specified interval. @@ -178,7 +178,7 @@ The `--pull-interval` flag works only with OCI references. Automatically pulls a Build Docker image for agent. ```console -$ cagent build agent-file|registry-ref [image-name] +$ docker agent build agent-file|registry-ref [image-name] ``` Arguments: @@ -198,8 +198,8 @@ Flags: Example: ```console -$ cagent build ./agent.yaml myagent:latest -$ cagent build ./agent.yaml --dry-run +$ docker agent build ./agent.yaml myagent:latest +$ docker agent build ./agent.yaml --dry-run ``` ### catalog list @@ -207,7 +207,7 @@ $ cagent build ./agent.yaml --dry-run List catalog agents. ```console -$ cagent catalog list [org] +$ docker agent catalog list [org] ``` Arguments: @@ -221,7 +221,7 @@ Queries Docker Hub for agent repositories. Show resolved agent configuration. ```console -$ cagent debug config agent-file|registry-ref +$ docker agent debug config agent-file|registry-ref ``` Arguments: @@ -237,7 +237,7 @@ Shows canonical configuration in YAML after all processing and defaults. List agent tools. ```console -$ cagent debug toolsets agent-file|registry-ref +$ docker agent debug toolsets agent-file|registry-ref ``` Arguments: @@ -253,7 +253,7 @@ Lists all tools for each agent in the configuration. Run evaluation tests. ```console -$ cagent eval agent-file|registry-ref [eval-dir] +$ docker agent eval agent-file|registry-ref [eval-dir] ``` Arguments: @@ -268,7 +268,7 @@ Supports [runtime flags](#runtime-flags). Single message execution without TUI. ```console -$ cagent exec agent-file|registry-ref [message|-] +$ docker agent exec agent-file|registry-ref [message|-] ``` Arguments: @@ -283,9 +283,9 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ cagent exec ./agent.yaml -$ cagent exec ./agent.yaml "Check for security issues" -$ echo "Instructions" | cagent exec ./agent.yaml - +$ docker agent exec ./agent.yaml +$ docker agent exec ./agent.yaml "Check for security issues" +$ echo "Instructions" | docker agent exec ./agent.yaml - ``` ### feedback @@ -293,7 +293,7 @@ $ echo "Instructions" | cagent exec ./agent.yaml - Submit feedback. ```console -$ cagent feedback +$ docker agent feedback ``` Shows link to submit feedback. @@ -304,7 +304,7 @@ MCP (Model Context Protocol) server on stdio. Exposes agents as tools to MCP clients. See [MCP integration](../integrations/mcp.md) for setup guides. ```console -$ cagent mcp agent-file|registry-ref +$ docker agent mcp agent-file|registry-ref ``` Arguments: @@ -316,8 +316,8 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ cagent mcp ./agent.yaml -$ cagent mcp docker.io/user/agent:latest +$ docker agent mcp ./agent.yaml +$ docker agent mcp docker.io/user/agent:latest ``` ### new @@ -325,7 +325,7 @@ $ cagent mcp docker.io/user/agent:latest Create agent configuration interactively. ```console -$ cagent new [message...] +$ docker agent new [message...] ``` Flags: @@ -344,7 +344,7 @@ Opens interactive TUI to configure and generate agent YAML. Pull agent from OCI registry. ```console -$ cagent pull registry-ref +$ docker agent pull registry-ref ``` Arguments: @@ -360,7 +360,7 @@ Flags: Example: ```console -$ cagent pull docker.io/user/agent:latest +$ docker agent pull docker.io/user/agent:latest ``` Saves to local YAML file. @@ -370,7 +370,7 @@ Saves to local YAML file. Push agent to OCI registry. ```console -$ cagent push agent-file registry-ref +$ docker agent push agent-file registry-ref ``` Arguments: @@ -381,7 +381,7 @@ Arguments: Example: ```console -$ cagent push ./agent.yaml docker.io/myuser/myagent:latest +$ docker agent push ./agent.yaml docker.io/myuser/myagent:latest ``` ### run @@ -389,7 +389,7 @@ $ cagent push ./agent.yaml docker.io/myuser/myagent:latest Interactive terminal UI for agent sessions. ```console -$ cagent run [agent-file|registry-ref] [message|-] +$ docker agent run [agent-file|registry-ref] [message|-] ``` Arguments: @@ -413,11 +413,11 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ cagent run ./agent.yaml -$ cagent run ./agent.yaml "Analyze this codebase" -$ cagent run ./agent.yaml --agent researcher -$ echo "Instructions" | cagent run ./agent.yaml - -$ cagent run +$ docker agent run ./agent.yaml +$ docker agent run ./agent.yaml "Analyze this codebase" +$ docker agent run ./agent.yaml --agent researcher +$ echo "Instructions" | docker agent run ./agent.yaml - +$ docker agent run ``` Running without arguments uses the default agent or a "default" alias if configured. @@ -441,10 +441,10 @@ TUI slash commands: Print version information. ```console -$ cagent version +$ docker agent version ``` -Shows cagent version and commit hash. +Shows Docker Agent version and commit hash. ## Environment variables @@ -466,15 +466,15 @@ Without an agent name, the model applies to all agents. With an agent name, it a Apply to all agents: ```console -$ cagent run ./agent.yaml --model gpt-5 -$ cagent run ./agent.yaml --model anthropic/claude-sonnet-4-5 +$ docker agent run ./agent.yaml --model gpt-5 +$ docker agent run ./agent.yaml --model anthropic/claude-sonnet-4-5 ``` Apply to specific agents only: ```console -$ cagent run ./agent.yaml --model researcher=gpt-5 -$ cagent run ./agent.yaml --model "agent1=gpt-5,agent2=claude-sonnet-4-5" +$ docker agent run ./agent.yaml --model researcher=gpt-5 +$ docker agent run ./agent.yaml --model "agent1=gpt-5,agent2=claude-sonnet-4-5" ``` Providers: `openai`, `anthropic`, `google`, `dmr` diff --git a/content/manuals/ai/cagent/reference/config.md b/content/manuals/ai/docker-agent/reference/config.md similarity index 99% rename from content/manuals/ai/cagent/reference/config.md rename to content/manuals/ai/docker-agent/reference/config.md index 941757cca311..2b49bb5e832b 100644 --- a/content/manuals/ai/cagent/reference/config.md +++ b/content/manuals/ai/docker-agent/reference/config.md @@ -6,7 +6,7 @@ keywords: [ai, agent, cagent, configuration, yaml] weight: 10 --- -This reference documents the YAML configuration file format for cagent agents. +This reference documents the YAML configuration file format for Docker Agent agents. It covers file structure, agent parameters, model configuration, toolset setup, and RAG sources. @@ -137,7 +137,7 @@ commands: analyze: "Analyze ${env.PROJECT_NAME || 'demo'}" ``` -Run with: `cagent run config.yaml /greet` +Run with: `docker agent run config.yaml /greet` ### Structured output diff --git a/content/manuals/ai/cagent/reference/examples.md b/content/manuals/ai/docker-agent/reference/examples.md similarity index 100% rename from content/manuals/ai/cagent/reference/examples.md rename to content/manuals/ai/docker-agent/reference/examples.md diff --git a/content/manuals/ai/cagent/reference/toolsets.md b/content/manuals/ai/docker-agent/reference/toolsets.md similarity index 99% rename from content/manuals/ai/cagent/reference/toolsets.md rename to content/manuals/ai/docker-agent/reference/toolsets.md index 618c4943a32c..cb4bd5dc2d91 100644 --- a/content/manuals/ai/cagent/reference/toolsets.md +++ b/content/manuals/ai/docker-agent/reference/toolsets.md @@ -1,12 +1,12 @@ --- title: Toolsets reference linkTitle: Toolsets -description: Complete reference for cagent toolsets and their capabilities +description: Complete reference for Docker Agent toolsets and their capabilities keywords: [ai, agent, cagent, tools, toolsets] weight: 20 --- -This reference documents the toolsets available in cagent and what each one +This reference documents the toolsets available in Docker Agent and what each one does. Tools give agents the ability to take action—interacting with files, executing commands, accessing external resources, and managing state. diff --git a/content/manuals/ai/cagent/sharing-agents.md b/content/manuals/ai/docker-agent/sharing-agents.md similarity index 84% rename from content/manuals/ai/cagent/sharing-agents.md rename to content/manuals/ai/docker-agent/sharing-agents.md index 5072229f873a..d3c201af739c 100644 --- a/content/manuals/ai/cagent/sharing-agents.md +++ b/content/manuals/ai/docker-agent/sharing-agents.md @@ -1,7 +1,7 @@ --- title: Sharing agents description: Distribute agent configurations through OCI registries -keywords: [cagent, oci, registry, docker hub, sharing, distribution] +keywords: [docker agent, oci, registry, docker hub, sharing, distribution] weight: 50 --- @@ -27,7 +27,7 @@ For other registries, use their authentication method. Push your agent configuration to a registry: ```console -$ cagent push ./agent.yml myusername/agent-name +$ docker agent push ./agent.yml myusername/agent-name ``` Push creates the repository if it doesn't exist yet. Use Docker Hub or @@ -36,8 +36,8 @@ any OCI-compatible registry. Tag specific versions: ```console -$ cagent push ./agent.yml myusername/agent-name:v1.0.0 -$ cagent push ./agent.yml myusername/agent-name:latest +$ docker agent push ./agent.yml myusername/agent-name:v1.0.0 +$ docker agent push ./agent.yml myusername/agent-name:latest ``` ## Using published agents @@ -45,7 +45,7 @@ $ cagent push ./agent.yml myusername/agent-name:latest Pull an agent to inspect it locally: ```console -$ cagent pull agentcatalog/pirate +$ docker agent pull agentcatalog/pirate ``` This saves the configuration as a local YAML file. @@ -53,7 +53,7 @@ This saves the configuration as a local YAML file. Run agents directly from the registry: ```console -$ cagent run agentcatalog/pirate +$ docker agent run agentcatalog/pirate ``` Or reference it directly in integrations: diff --git a/content/manuals/ai/cagent/tutorial.md b/content/manuals/ai/docker-agent/tutorial.md similarity index 94% rename from content/manuals/ai/cagent/tutorial.md rename to content/manuals/ai/docker-agent/tutorial.md index e2a88e184c8c..360f1560c777 100644 --- a/content/manuals/ai/cagent/tutorial.md +++ b/content/manuals/ai/docker-agent/tutorial.md @@ -1,7 +1,7 @@ --- title: Building a coding agent description: Create a coding agent that can read, write, and validate code changes in your projects -keywords: [cagent, tutorial, coding agent, ai assistant] +keywords: [docker agent, tutorial, coding agent, ai assistant] weight: 30 --- @@ -25,7 +25,7 @@ A coding agent that can: ## What you'll learn -- How to configure cagent agents in YAML +- How to configure Docker Agent agents in YAML - How to give agents access to tools (filesystem, shell, etc.) - How to write effective agent instructions - How to compose multiple agents for specialized tasks @@ -35,7 +35,7 @@ A coding agent that can: Before starting, you need: -- **cagent installed** - See the [installation guide](_index.md#installation) +- **Docker Agent installed** - See the [installation guide](_index.md#installation) - **API key configured** - Set `ANTHROPIC_API_KEY` or `OPENAI_API_KEY` in your environment. Get keys from [Anthropic](https://console.anthropic.com/) or [OpenAI](https://platform.openai.com/api-keys) @@ -43,7 +43,7 @@ Before starting, you need: ## Creating your first agent -A cagent agent is defined in a YAML configuration file. The minimal agent needs +A Docker Agent agent is defined in a YAML configuration file. The minimal agent needs just a model and instructions that define its purpose. Create a file named `agents.yml`: @@ -61,7 +61,7 @@ agents: Run your agent: ```console -$ cagent run agents.yml +$ docker agent run agents.yml ``` Try asking it: "How do I read a file in Python?" @@ -267,7 +267,7 @@ The best way to improve your agent is to use it. When you notice issues: You now know how to: -- Create a basic cagent configuration +- Create a basic Docker Agent configuration - Add tools to enable agent capabilities - Write structured instructions for consistent behavior - Compose multiple agents for specialized tasks @@ -277,7 +277,7 @@ You now know how to: - Learn [best practices](best-practices.md) for handling large outputs, structuring agent teams, and optimizing performance -- Integrate cagent with your [editor](integrations/acp.md) or use agents as +- Integrate Docker Agent with your [editor](integrations/acp.md) or use agents as [tools in MCP clients](integrations/mcp.md) - Review the [Configuration reference](reference/config.md) for all available options @@ -288,4 +288,4 @@ You now know how to: different use cases - See the full [golang_developer.yaml](https://github.com/docker/cagent/blob/main/golang_developer.yaml) - that the Docker team uses to develop cagent + that the Docker team uses to develop Docker Agent diff --git a/content/manuals/ai/sandboxes/_index.md b/content/manuals/ai/sandboxes/_index.md index 464ed43619b9..3678b5fa6145 100644 --- a/content/manuals/ai/sandboxes/_index.md +++ b/content/manuals/ai/sandboxes/_index.md @@ -91,7 +91,7 @@ Docker Sandboxes works with multiple AI coding agents: - **Copilot** - GitHub Copilot agent (in development) - **Gemini** - Google's Gemini agent (in development) - **OpenCode** - Multi-provider agent with TUI interface (in development) -- **cagent** - Docker's multi-provider coding agent (in development) +- **Docker Agent** - Docker's multi-provider coding agent (in development) - **Kiro** - Interactive agent with device flow auth (in development) - **Shell** - Minimal sandbox for manual agent installation diff --git a/content/manuals/ai/sandboxes/agents/_index.md b/content/manuals/ai/sandboxes/agents/_index.md index 7ebeba1064ac..53f57d6b9d44 100644 --- a/content/manuals/ai/sandboxes/agents/_index.md +++ b/content/manuals/ai/sandboxes/agents/_index.md @@ -18,7 +18,7 @@ inside microVMs with private Docker daemons. | Codex | `codex` | Experimental | In development | | Copilot | `copilot` | Experimental | In development | | Gemini | `gemini` | Experimental | In development | -| cagent | `cagent` | Experimental | In development | +| Docker Agent | `cagent` | Experimental | In development | | Kiro | `kiro` | Experimental | In development | | OpenCode | `opencode` | Experimental | In development | | Custom shell | `shell` | Experimental | Minimal environment for manual setup | diff --git a/content/manuals/ai/sandboxes/agents/cagent.md b/content/manuals/ai/sandboxes/agents/cagent.md index b6be40586111..0f248718db86 100644 --- a/content/manuals/ai/sandboxes/agents/cagent.md +++ b/content/manuals/ai/sandboxes/agents/cagent.md @@ -1,21 +1,21 @@ --- -title: cagent sandbox +title: Docker Agent sandbox description: | - Use Docker cagent in Docker Sandboxes with multi-provider authentication + Use Docker Agent in Docker Sandboxes with multi-provider authentication supporting OpenAI, Anthropic, and more. -keywords: docker, sandboxes, cagent, ai agent, multi-provider, authentication +keywords: docker, sandboxes, docker agent, ai agent, multi-provider, authentication weight: 60 --- {{< summary-bar feature_name="Docker Sandboxes" >}} -This guide covers authentication, configuration, and usage of Docker cagent in -a sandboxed environment. [cagent](/ai/cagent/) is Docker's open source coding +This guide covers authentication, configuration, and usage of Docker Agent in +a sandboxed environment. [Docker Agent](/ai/docker-agent/) is Docker's open source coding agent that supports multiple providers. ## Quick start -Create a sandbox and run cagent for a project directory: +Create a sandbox and run Docker Agent for a project directory: ```console $ docker sandbox run cagent ~/my-project @@ -30,7 +30,7 @@ $ docker sandbox run cagent ## Authentication -cagent uses proxy-managed authentication for all supported providers. Docker +Docker Agent uses proxy-managed authentication for all supported providers. Docker Sandboxes intercepts API requests and injects credentials transparently. You provide your API keys through environment variables, and the sandbox handles credential management. @@ -48,7 +48,7 @@ export NEBIUS_API_KEY=xxxxx export MISTRAL_API_KEY=xxxxx ``` -You only need to configure the providers you want to use. cagent detects +You only need to configure the providers you want to use. Docker Agent detects available credentials and routes requests to the appropriate provider. ### Environment variable setup @@ -72,25 +72,25 @@ The sandbox detects the environment variables and uses them automatically. ## Configuration -cagent supports YOLO mode that disables safety checks and approval prompts. +Docker Agent supports YOLO mode that disables safety checks and approval prompts. This mode grants the agent full access to your sandbox environment without interactive confirmation. ### Pass options at runtime -Pass cagent CLI options after the sandbox name and a `--` separator: +Pass Docker Agent CLI options after the sandbox name and a `--` separator: ```console $ docker sandbox run -- run --yolo ``` -The `run --yolo` command starts cagent with approval prompts disabled. +The `run --yolo` command starts Docker Agent with approval prompts disabled. ## Base image Template: `docker/sandbox-templates:cagent` -cagent supports multiple LLM providers with automatic credential injection +Docker Agent supports multiple LLM providers with automatic credential injection through the sandbox proxy. Launches with `run --yolo` by default. See [Custom templates](../templates.md) to build your own agent images. diff --git a/content/manuals/ai/sandboxes/architecture.md b/content/manuals/ai/sandboxes/architecture.md index 12816511ae72..9a513b51b273 100644 --- a/content/manuals/ai/sandboxes/architecture.md +++ b/content/manuals/ai/sandboxes/architecture.md @@ -166,7 +166,7 @@ inside the sandbox VM. The agent makes API requests without credentials, and the proxy injects them transparently. When the sandbox is removed, no credentials remain inside. -For multi-provider agents (OpenCode, cagent), the proxy automatically selects +For multi-provider agents (OpenCode, Docker Agent), the proxy automatically selects the correct credentials based on the API endpoint being called. See individual [agent configuration](agents/) for credential setup instructions. diff --git a/content/manuals/ai/sandboxes/workflows.md b/content/manuals/ai/sandboxes/workflows.md index 2b5779079274..ac2885c2150a 100644 --- a/content/manuals/ai/sandboxes/workflows.md +++ b/content/manuals/ai/sandboxes/workflows.md @@ -256,7 +256,7 @@ $ docker sandbox ls SANDBOX AGENT STATUS WORKSPACE sb1 claude running /Users/bob/src/project-a sb2 claude running /Users/bob/src/project-a, /Users/bob/src/project-b -sb3 cagent running /Users/bob/src/project-a +sb3 Docker Agent running /Users/bob/src/project-a ``` Each sandbox runs in isolation with separate configurations while sharing the diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 8699d129d59c..056cc7ad5d6a 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -498,7 +498,7 @@ For more frequently asked questions, see the [FAQs](/manuals/desktop/troubleshoo ### New -- [cagent](/manuals/ai/cagent/_index.md) is now available through Docker Desktop. +- [Docker Agent](/manuals/ai/docker-agent/_index.md) is now available through Docker Desktop. - [Docker Debug](/reference/cli/docker/debug/) is now free for all users. ### Upgrades diff --git a/data/summary.yaml b/data/summary.yaml index 372286c657fe..64b2b672ac36 100644 --- a/data/summary.yaml +++ b/data/summary.yaml @@ -68,7 +68,7 @@ Buildx no default: requires: Docker Buildx [0.10.4](https://github.com/docker/buildx/releases/tag/v0.10.4) and later Cache backend API: availability: Experimental -cagent: +Docker Agent: availability: Experimental Company: subscription: [Business] From 91a53346d9987f2a28a53b496b1c7ee1159cc445 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Wed, 4 Mar 2026 12:10:03 +0100 Subject: [PATCH 2/4] Fix `docker agent serve xxx` commands Signed-off-by: Guillaume Tardif --- .../ai/docker-agent/integrations/a2a.md | 12 +++++----- .../ai/docker-agent/integrations/acp.md | 8 +++---- .../ai/docker-agent/integrations/mcp.md | 22 ++++++++++--------- .../manuals/ai/docker-agent/reference/cli.md | 22 +++++++++---------- .../manuals/ai/docker-agent/sharing-agents.md | 4 ++-- 5 files changed, 35 insertions(+), 33 deletions(-) diff --git a/content/manuals/ai/docker-agent/integrations/a2a.md b/content/manuals/ai/docker-agent/integrations/a2a.md index 7bb58002169d..e2952baa8efe 100644 --- a/content/manuals/ai/docker-agent/integrations/a2a.md +++ b/content/manuals/ai/docker-agent/integrations/a2a.md @@ -29,7 +29,7 @@ Before starting an A2A server, you need: Basic usage: ```console -$ docker agent a2a ./agent.yaml +$ docker agent serve a2a ./agent.yaml ``` Your agent is now accessible via HTTP. Other A2A systems can discover your @@ -38,19 +38,19 @@ agent's capabilities and call it. Custom port: ```console -$ docker agent a2a ./agent.yaml --port 8080 +$ docker agent serve a2a ./agent.yaml --port 8080 ``` Specific agent in a team: ```console -$ docker agent a2a ./agent.yaml --agent engineer +$ docker agent serve a2a ./agent.yaml --agent engineer ``` From OCI registry: ```console -$ docker agent a2a agentcatalog/pirate --port 9000 +$ docker agent serve a2a agentcatalog/pirate --port 9000 ``` ## HTTP endpoints @@ -142,7 +142,7 @@ Here's a concrete scenario where A2A is useful. You have two agents: Run the specialist as an A2A server: ```console -$ docker agent a2a ./code-reviewer.yaml --port 8080 +$ docker agent serve a2a ./code-reviewer.yaml --port 8080 Listening on 127.0.0.1:8080 ``` @@ -198,7 +198,7 @@ agents: ## What's next -- Review the [CLI reference](../reference/cli.md#a2a) for all `docker agent a2a` +- Review the [CLI reference](../reference/cli.md#a2a) for all `docker agent serve a2a` options - Learn about [MCP mode](./mcp.md) to expose agents as tools in MCP clients - Learn about [ACP mode](./acp.md) for editor integration diff --git a/content/manuals/ai/docker-agent/integrations/acp.md b/content/manuals/ai/docker-agent/integrations/acp.md index d8e7c210a751..9a16306056c5 100644 --- a/content/manuals/ai/docker-agent/integrations/acp.md +++ b/content/manuals/ai/docker-agent/integrations/acp.md @@ -131,11 +131,11 @@ reference: ```console # Local file path -$ docker agent acp ./agent.yml +$ docker agent serve acp ./agent.yml # OCI registry reference -$ docker agent acp agentcatalog/pirate -$ docker agent acp dockereng/myagent:v1.0.0 +$ docker agent serve acp agentcatalog/pirate +$ docker agent serve acp dockereng/myagent:v1.0.0 ``` Use the same syntax in your editor configuration: @@ -177,7 +177,7 @@ If the agent starts but can't access files or perform other actions, check: - Explore the [toolsets reference](../reference/toolsets.md) to learn what tools are available - Add [RAG for codebase search](../rag.md) to your agent -- Check the [CLI reference](../reference/cli.md) for all `docker agent acp` options +- Check the [CLI reference](../reference/cli.md) for all `docker agent serve acp` options - Browse [example configurations](https://github.com/docker/cagent/tree/main/examples) for inspiration diff --git a/content/manuals/ai/docker-agent/integrations/mcp.md b/content/manuals/ai/docker-agent/integrations/mcp.md index e32073a2701b..8b9cc1a1d98b 100644 --- a/content/manuals/ai/docker-agent/integrations/mcp.md +++ b/content/manuals/ai/docker-agent/integrations/mcp.md @@ -93,8 +93,10 @@ Example configuration: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/cagent", + "command": "/usr/local/bin/docker", "args": [ + "agent", + "serve", "mcp", "/path/to/agent.yml", "--working-dir", @@ -111,7 +113,7 @@ Example configuration: Configuration breakdown: -- `command`: Full path to your `cagent` binary (use `which cagent` to find it) +- `command`: Full path to your `docker` binary (use `which docker` to find it), or path to docker-agent if not using the docker CLI plugin - `args`: MCP command arguments: - `mcp`: The subcommand to run cagent in MCP mode - `dockereng/myagent`: Your agent configuration (local file path or OCI @@ -142,7 +144,7 @@ Command breakdown: - `myagent`: Name for this MCP server in Claude Code - `--env`: Pass environment variables (repeat for each variable) - `--`: Separates Claude Code options from the MCP server command -- `docker agent mcp /path/to/agent.yml`: The cagent MCP command with the path to your +- `docker agent serve mcp /path/to/agent.yml`: The cagent MCP command with the path to your agent configuration - `--working-dir $(pwd)`: Set the working directory for agent execution @@ -153,7 +155,7 @@ sessions. For other MCP-compatible clients, you need to: -1. Start cagent with `docker agent mcp /path/to/agent.yml --working-dir /project/path` +1. Start cagent with `docker agent serve mcp /path/to/agent.yml --working-dir /project/path` 2. Configure the client to communicate with Docker Agent over stdio 3. Pass required environment variables (API keys, etc.) @@ -166,11 +168,11 @@ reference: ```console # Local file path -$ docker agent mcp ./agent.yml +$ docker agent serve mcp ./agent.yml # OCI registry reference -$ docker agent mcp agentcatalog/pirate -$ docker agent mcp dockereng/myagent:v1.0.0 +$ docker agent serve mcp agentcatalog/pirate +$ docker agent serve mcp dockereng/myagent:v1.0.0 ``` Use the same syntax in MCP client configurations: @@ -179,8 +181,8 @@ Use the same syntax in MCP client configurations: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/cagent", - "args": ["mcp", "agentcatalog/pirate"] + "command": "/usr/local/bin/docker", + "args": ["agent", "serve", "mcp", "agentcatalog/pirate"] } } } @@ -299,7 +301,7 @@ around. - Explore the [toolsets reference](../reference/toolsets.md) to learn what tools agents can use - Add [RAG for codebase search](../rag.md) to your agent -- Check the [CLI reference](../reference/cli.md) for all `docker agent mcp` options +- Check the [CLI reference](../reference/cli.md) for all `docker agent serve mcp` options - Browse [example configurations](https://github.com/docker/cagent/tree/main/examples) for different agent types diff --git a/content/manuals/ai/docker-agent/reference/cli.md b/content/manuals/ai/docker-agent/reference/cli.md index f9e3e89b913a..16c652c330a5 100644 --- a/content/manuals/ai/docker-agent/reference/cli.md +++ b/content/manuals/ai/docker-agent/reference/cli.md @@ -53,7 +53,7 @@ systems to discover and interact with your agent. Auto-selects an available port if not specified. ```console -$ docker agent a2a agent-file|registry-ref +$ docker agent serve a2a agent-file|registry-ref ``` > [!NOTE] @@ -77,8 +77,8 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ docker agent a2a ./agent.yaml --port 8080 -$ docker agent a2a agentcatalog/pirate --port 9000 +$ docker agent serve a2a ./agent.yaml --port 8080 +$ docker agent serve a2a agentcatalog/pirate --port 9000 ``` ### acp @@ -87,7 +87,7 @@ Start agent as ACP (Agent Client Protocol) server on stdio for editor integratio See [ACP integration](../integrations/acp.md) for setup guides. ```console -$ docker agent acp agent-file|registry-ref +$ docker agent serve acp agent-file|registry-ref ``` Arguments: @@ -146,7 +146,7 @@ Arguments: HTTP API server. ```console -$ docker agent api agent-file|agents-dir +$ docker agent serve api agent-file|agents-dir ``` Arguments: @@ -166,9 +166,9 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ docker agent api ./agent.yaml -$ docker agent api ./agents/ --listen :9000 -$ docker agent api docker.io/user/agent --pull-interval 10 +$ docker agent serve api ./agent.yaml +$ docker agent serve api ./agents/ --listen :9000 +$ docker agent serve api docker.io/user/agent --pull-interval 10 ``` The `--pull-interval` flag works only with OCI references. Automatically pulls and reloads at the specified interval. @@ -304,7 +304,7 @@ MCP (Model Context Protocol) server on stdio. Exposes agents as tools to MCP clients. See [MCP integration](../integrations/mcp.md) for setup guides. ```console -$ docker agent mcp agent-file|registry-ref +$ docker agent serve mcp agent-file|registry-ref ``` Arguments: @@ -316,8 +316,8 @@ Supports [runtime flags](#runtime-flags). Examples: ```console -$ docker agent mcp ./agent.yaml -$ docker agent mcp docker.io/user/agent:latest +$ docker agent serve mcp ./agent.yaml +$ docker agent serve mcp docker.io/user/agent:latest ``` ### new diff --git a/content/manuals/ai/docker-agent/sharing-agents.md b/content/manuals/ai/docker-agent/sharing-agents.md index d3c201af739c..77f0a883d850 100644 --- a/content/manuals/ai/docker-agent/sharing-agents.md +++ b/content/manuals/ai/docker-agent/sharing-agents.md @@ -82,8 +82,8 @@ Agents can be exposed as tools in MCP clients: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/cagent", - "args": ["mcp", "agentcatalog/pirate"] + "command": "/usr/local/bin/docker", + "args": ["agent", "serve", "mcp", "agentcatalog/pirate"] } } } From a17b4800417cb15b7de40c1d533183b307cd1464 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Wed, 4 Mar 2026 12:34:57 +0100 Subject: [PATCH 3/4] Mention Docker Agent was previously cagent, availabe since Desktop 4.49, docker agent is available in desktop 4.63 and later Signed-off-by: Guillaume Tardif --- content/manuals/ai/docker-agent/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/manuals/ai/docker-agent/_index.md b/content/manuals/ai/docker-agent/_index.md index 35c1f4759d74..e950408d8125 100644 --- a/content/manuals/ai/docker-agent/_index.md +++ b/content/manuals/ai/docker-agent/_index.md @@ -61,7 +61,7 @@ its specialty. ## Installation -Docker Agent is included in Docker Desktop 4.49 and later. +Docker Agent is included in Docker Desktop 4.63 and later. In Docker Desktop versions 4.49 through 4.62, this feature was called cagent. For Docker Engine users or custom installations: @@ -72,6 +72,8 @@ For Docker Engine users or custom installations: - **From source**: See the [Docker Agent repository](https://github.com/docker/cagent?tab=readme-ov-file#build-from-source) +The `docker-agent` binary should be copied to `~/.docker/cli-plugins` and then can be used with the `docker agent` command. Alternatively, it can be used as a standalone binary. + ## Get started Try the bug analyzer team: From ecf203718d1fef5d5acca8ed58e130c466ee6665 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Wed, 4 Mar 2026 15:50:14 +0100 Subject: [PATCH 4/4] Fix vale comments Signed-off-by: Guillaume Tardif --- content/manuals/ai/docker-agent/best-practices.md | 4 ++-- content/manuals/ai/docker-agent/integrations/_index.md | 8 ++++---- content/manuals/ai/docker-agent/integrations/a2a.md | 4 ++-- content/manuals/ai/docker-agent/integrations/acp.md | 6 +++--- content/manuals/ai/docker-agent/integrations/mcp.md | 10 +++++----- content/manuals/ai/docker-agent/rag.md | 2 +- content/manuals/ai/docker-agent/reference/config.md | 2 +- content/manuals/ai/docker-agent/sharing-agents.md | 2 +- content/manuals/ai/docker-agent/tutorial.md | 6 +++--- 9 files changed, 22 insertions(+), 22 deletions(-) diff --git a/content/manuals/ai/docker-agent/best-practices.md b/content/manuals/ai/docker-agent/best-practices.md index 550247864c74..75a1f28a8231 100644 --- a/content/manuals/ai/docker-agent/best-practices.md +++ b/content/manuals/ai/docker-agent/best-practices.md @@ -1,11 +1,11 @@ --- title: Best practices -description: Patterns and techniques for building effective Docker Agent agents +description: Patterns and techniques for building effective agents keywords: [docker agent, best practices, patterns, agent design, optimization] weight: 40 --- -Patterns you learn from building and running Docker Agent agents. These aren't +Patterns you learn from building and running agents with Docker Agent. These aren't features or configuration options - they're approaches that work well in practice. diff --git a/content/manuals/ai/docker-agent/integrations/_index.md b/content/manuals/ai/docker-agent/integrations/_index.md index a31c04ffd265..a9ab7235a503 100644 --- a/content/manuals/ai/docker-agent/integrations/_index.md +++ b/content/manuals/ai/docker-agent/integrations/_index.md @@ -1,6 +1,6 @@ --- title: Integrations -description: Connect Docker Agent agents to editors, MCP clients, and other agents +description: Connect agents to editors, MCP clients, and other agents keywords: [docker agent, integration, acp, mcp, a2a, editor, protocol] weight: 60 --- @@ -12,7 +12,7 @@ want to use them. Each integration type serves a specific purpose. ### ACP - Editor integration -Run Docker Agent agents directly in your editor (Neovim, Zed). The agent sees your +Run agents directly in your editor (Neovim, Zed). The agent sees your editor's file context and can read and modify files through the editor's interface. Use ACP when you want an AI coding assistant embedded in your editor. @@ -21,7 +21,7 @@ See [ACP integration](./acp.md) for setup instructions. ### MCP - Tool integration -Expose Docker Agent agents as tools in MCP clients like Claude Desktop or Claude +Expose agents as tools in MCP clients like Claude Desktop or Claude Code. Your agents appear in the client's tool list, and the client can call them when needed. Use MCP when you want Claude Desktop (or another MCP client) to have access to your specialized agents. @@ -30,7 +30,7 @@ See [MCP integration](./mcp.md) for setup instructions. ### A2A - Agent-to-agent communication -Run Docker Agent agents as HTTP servers that other agents or systems can call using +Run agents as HTTP servers that other agents or systems can call using the Agent-to-Agent protocol. Your agent becomes a service that other systems can discover and invoke over the network. Use A2A when you want to build multi-agent systems or expose your agent as an HTTP service. diff --git a/content/manuals/ai/docker-agent/integrations/a2a.md b/content/manuals/ai/docker-agent/integrations/a2a.md index e2952baa8efe..afbe0d7a8dc2 100644 --- a/content/manuals/ai/docker-agent/integrations/a2a.md +++ b/content/manuals/ai/docker-agent/integrations/a2a.md @@ -1,12 +1,12 @@ --- title: A2A mode linkTitle: A2A -description: Expose Docker Agent agents via the Agent-to-Agent protocol +description: Expose agents via the Agent-to-Agent protocol keywords: [docker agent, a2a, agent-to-agent, multi-agent, protocol] weight: 40 --- -A2A mode runs your Docker Agent agent as an HTTP server that other systems can call +A2A mode runs your agent as an HTTP server that other systems can call using the Agent-to-Agent protocol. This lets you expose your agent as a service that other agents or applications can discover and invoke over the network. diff --git a/content/manuals/ai/docker-agent/integrations/acp.md b/content/manuals/ai/docker-agent/integrations/acp.md index 9a16306056c5..6caebfe128f4 100644 --- a/content/manuals/ai/docker-agent/integrations/acp.md +++ b/content/manuals/ai/docker-agent/integrations/acp.md @@ -1,12 +1,12 @@ --- linkTitle: ACP title: ACP integration -description: Configure your editor or IDE to use Docker Agent agents as coding assistants +description: Configure your editor or IDE to use agents as coding assistants keywords: [docker agent, acp, editor, ide, neovim, zed, integration] weight: 40 --- -Run Docker Agent agents directly in your editor using the Agent Client Protocol (ACP). +Run agents directly in your editor using the Agent Client Protocol (ACP). Your agent gets access to your editor's filesystem context and can read and modify files as you work. The editor handles file operations while cagent provides the AI capabilities. @@ -36,7 +36,7 @@ same files, same state. Before configuring your editor, you need: -- **cagent installed** - See the [installation guide](../_index.md#installation) +- **Docker Agent installed** - See the [installation guide](../_index.md#installation) - **Agent configuration** - A YAML file defining your agent. See the [tutorial](../tutorial.md) or [example configurations](https://github.com/docker/cagent/tree/main/examples) diff --git a/content/manuals/ai/docker-agent/integrations/mcp.md b/content/manuals/ai/docker-agent/integrations/mcp.md index 8b9cc1a1d98b..7f5dfa7b9db2 100644 --- a/content/manuals/ai/docker-agent/integrations/mcp.md +++ b/content/manuals/ai/docker-agent/integrations/mcp.md @@ -1,7 +1,7 @@ --- title: MCP mode linkTitle: MCP -description: Expose Docker Agent agents as tools to MCP clients like Claude Desktop and Claude Code +description: Expose agents as tools to MCP clients like Claude Desktop and Claude Code keywords: [ cagent, @@ -65,7 +65,7 @@ manage MCP servers interactively. Before configuring MCP integration, you need: -- **cagent installed** - See the [installation guide](../_index.md#installation) +- **Docker Agent installed** - See the [installation guide](../_index.md#installation) - **Agent configuration** - A YAML file defining your agent. See the [tutorial](../tutorial.md) or [example configurations](https://github.com/docker/cagent/tree/main/examples) @@ -93,7 +93,7 @@ Example configuration: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/docker", + "command": "docker", "args": [ "agent", "serve", @@ -113,7 +113,7 @@ Example configuration: Configuration breakdown: -- `command`: Full path to your `docker` binary (use `which docker` to find it), or path to docker-agent if not using the docker CLI plugin +- `command`: Full path to your `docker` binary (use `which docker` to find it), or path to `docker-agent` if not using the Docker CLI plugin - `args`: MCP command arguments: - `mcp`: The subcommand to run cagent in MCP mode - `dockereng/myagent`: Your agent configuration (local file path or OCI @@ -181,7 +181,7 @@ Use the same syntax in MCP client configurations: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/docker", + "command": "docker", "args": ["agent", "serve", "mcp", "agentcatalog/pirate"] } } diff --git a/content/manuals/ai/docker-agent/rag.md b/content/manuals/ai/docker-agent/rag.md index 3fbd7ec6f041..025535f52b93 100644 --- a/content/manuals/ai/docker-agent/rag.md +++ b/content/manuals/ai/docker-agent/rag.md @@ -1,6 +1,6 @@ --- title: RAG -description: How RAG gives your Docker Agent agents access to codebases and documentation +description: How RAG gives your agents access to codebases and documentation keywords: [docker agent, rag, retrieval, embeddings, semantic search] weight: 70 --- diff --git a/content/manuals/ai/docker-agent/reference/config.md b/content/manuals/ai/docker-agent/reference/config.md index 2b49bb5e832b..09be1981e6f9 100644 --- a/content/manuals/ai/docker-agent/reference/config.md +++ b/content/manuals/ai/docker-agent/reference/config.md @@ -6,7 +6,7 @@ keywords: [ai, agent, cagent, configuration, yaml] weight: 10 --- -This reference documents the YAML configuration file format for Docker Agent agents. +This reference documents the YAML configuration file format for agents suing Docker Agent. It covers file structure, agent parameters, model configuration, toolset setup, and RAG sources. diff --git a/content/manuals/ai/docker-agent/sharing-agents.md b/content/manuals/ai/docker-agent/sharing-agents.md index 77f0a883d850..44cadf21b814 100644 --- a/content/manuals/ai/docker-agent/sharing-agents.md +++ b/content/manuals/ai/docker-agent/sharing-agents.md @@ -82,7 +82,7 @@ Agents can be exposed as tools in MCP clients: { "mcpServers": { "myagent": { - "command": "/usr/local/bin/docker", + "command": "docker", "args": ["agent", "serve", "mcp", "agentcatalog/pirate"] } } diff --git a/content/manuals/ai/docker-agent/tutorial.md b/content/manuals/ai/docker-agent/tutorial.md index 360f1560c777..5d5e58782942 100644 --- a/content/manuals/ai/docker-agent/tutorial.md +++ b/content/manuals/ai/docker-agent/tutorial.md @@ -25,7 +25,7 @@ A coding agent that can: ## What you'll learn -- How to configure Docker Agent agents in YAML +- How to configure agents in YAML with Docker Agents - How to give agents access to tools (filesystem, shell, etc.) - How to write effective agent instructions - How to compose multiple agents for specialized tasks @@ -43,7 +43,7 @@ Before starting, you need: ## Creating your first agent -A Docker Agent agent is defined in a YAML configuration file. The minimal agent needs +An agent is defined in a YAML configuration file. The minimal agent needs just a model and instructions that define its purpose. Create a file named `agents.yml`: @@ -288,4 +288,4 @@ You now know how to: different use cases - See the full [golang_developer.yaml](https://github.com/docker/cagent/blob/main/golang_developer.yaml) - that the Docker team uses to develop Docker Agent + that the Docker Team uses to develop Docker Agent