diff --git a/docs/amazon-q.mdx b/docs/amazon-q.mdx
new file mode 100644
index 00000000..24f5e9d3
--- /dev/null
+++ b/docs/amazon-q.mdx
@@ -0,0 +1,84 @@
+---
+title: Amazon Q Developer
+description: "Setup guide for Amazon Q Developer with Container Use"
+icon: robot
+---
+
+## Add MCP Configuration
+
+Add this configuration to `~/.aws/amazonq/mcp.json`:
+
+```json
+{
+ "mcpServers": {
+ "container-use": {
+ "command": "cu",
+ "args": ["stdio"],
+ "env": {},
+ "timeout": 60000
+ }
+ }
+}
+```
+
+## Add Agent Rules
+
+Save agent instructions to your project root:
+
+```sh
+mkdir -p ./.amazonq/rules && curl https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md > .amazonq/rules/container-use.md
+```
+
+## Trust Only Container Use Tools (Optional)
+
+```sh
+q chat --trust-tools=container_use___environment_checkpoint,container_use___environment_file_delete,container_use___environment_file_list,container_use___environment_file_read,container_use___environment_file_write,container_use___environment_open,container_use___environment_run_cmd,container_use___environment_update
+```
+
+
+ Watch the Amazon Q Developer setup walkthrough
+
+
+## Verification
+
+After setting up Amazon Q Developer, verify Container Use is working:
+
+1. **Check MCP Connection**: Amazon Q should recognize Container Use tools
+2. **Test Environment Creation**: Ask Amazon Q to create a new environment
+3. **Verify Isolation**: Multiple environments should work independently
+
+## Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart Amazon Q after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Check your Amazon Q MCP server logs
+ - Verify Container Use tools are enabled in settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file
diff --git a/docs/claude-code.mdx b/docs/claude-code.mdx
new file mode 100644
index 00000000..cbb1ba4a
--- /dev/null
+++ b/docs/claude-code.mdx
@@ -0,0 +1,83 @@
+---
+title: Claude Code
+description: "Setup guide for Claude Code with Container Use"
+icon: robot
+---
+
+## Install Claude Code
+
+```sh
+npm install -g @anthropic-ai/claude-code
+```
+
+## Add MCP Configuration
+
+```sh
+cd /path/to/repository
+claude mcp add container-use -- stdio
+```
+
+## Add Agent Rules (Optional)
+
+Save the CLAUDE.md file at the root of your repository:
+
+```sh
+curl https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md >> CLAUDE.md
+```
+
+## Trust Only Container Use Tools (Optional)
+
+For maximum security, restrict Claude Code to only use Container Use tools:
+
+```sh
+claude --allowedTools mcp__container-use__environment_checkpoint,mcp__container-use__environment_create,mcp__container-use__environment_add_service,mcp__container-use__environment_file_delete,mcp__container-use__environment_file_list,mcp__container-use__environment_file_read,mcp__container-use__environment_file_write,mcp__container-use__environment_open,mcp__container-use__environment_run_cmd,mcp__container-use__environment_update
+```
+
+
+ Learn more: [Claude Code MCP
+ Documentation](https://docs.anthropic.com/en/docs/claude-code/tutorials#set-up-model-context-protocol-mcp)
+
+
+## Verification
+
+After setting up Claude Code, verify Container Use is working:
+
+1. **Check MCP Connection**: Claude Code should recognize Container Use tools
+2. **Test Environment Creation**: Ask Claude Code to create a new environment
+3. **Verify Isolation**: Multiple environments should work independently
+
+## Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart Claude Code after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Check your Claude Code MCP server logs
+ - Verify Container Use tools are enabled in settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file
diff --git a/docs/cursor.mdx b/docs/cursor.mdx
new file mode 100644
index 00000000..3a882a59
--- /dev/null
+++ b/docs/cursor.mdx
@@ -0,0 +1,68 @@
+---
+title: Cursor
+description: "Setup guide for Cursor with Container Use"
+icon: robot
+---
+
+## Install MCP Server
+
+Use the one-click deeplink to install (requires Cursor and Container Use already installed):
+
+[](https://cursor.com/install-mcp?name=container-use&config=eyJjb21tYW5kIjoiY3Ugc3RkaW8ifQ%3D%3D)
+
+## Add Agent Rules
+
+Add the rules file to your project or home directory:
+
+```sh
+curl --create-dirs -o .cursor/rules/container-use.mdc https://raw.githubusercontent.com/dagger/container-use/main/rules/cursor.mdc
+```
+
+
+ Learn more: [Cursor MCP
+ Documentation](https://docs.cursor.com/context/model-context-protocol)
+
+
+## Verification
+
+After setting up Cursor, verify Container Use is working:
+
+1. **Check MCP Connection**: Cursor should recognize Container Use tools
+2. **Test Environment Creation**: Ask Cursor to create a new environment
+3. **Verify Isolation**: Multiple environments should work independently
+
+## Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart Cursor after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Check your Cursor MCP server logs
+ - Verify Container Use tools are enabled in settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file
diff --git a/docs/docs.json b/docs/docs.json
index a390078d..7ffcf65c 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -29,7 +29,12 @@
{
"group": "Integrations",
"pages": [
- "agent-integrations"
+ "claude-code",
+ "cursor",
+ "amazon-q",
+ "vscode",
+ "zed",
+ "other-agents"
]
}
]
diff --git a/docs/other-agents.mdx b/docs/other-agents.mdx
new file mode 100644
index 00000000..3999b5bc
--- /dev/null
+++ b/docs/other-agents.mdx
@@ -0,0 +1,278 @@
+---
+title: Other Agents
+description: "Setup guides for additional coding agents with Container Use"
+icon: robot
+---
+
+## Windsurf
+
+### Install MCP Server
+
+In `~/.codeium/windsurf/mcp_config.json`, add the following configuration:
+
+```json
+{
+ "mcpServers": {
+ "container-use": {
+ "command": "cu",
+ "args": ["stdio"],
+ "env": {}
+ }
+ }
+}
+```
+
+### Add Agent Rules
+
+Add the rules file to your project or home directory:
+
+```sh
+curl --create-dirs -o .windsurf/rules/container-use.mdc https://raw.githubusercontent.com/dagger/container-use/main/rules/windsurf.mdc
+```
+
+## OpenCode
+
+Configure the Container Use MCP server in a `opencode.json` file.
+
+> Note: Provide the absolute path to your systems `cu` executable:
+
+```json
+{
+ "$schema": "http://opencode.ai/config.json",
+ "mcp": {
+ "container-use": {
+ "type": "local",
+ "command": ["/path/to/cu", "stdio"],
+ "enabled": true
+ }
+ }
+}
+```
+
+Add the `AGENTS.md` file using this command (this is optional but usually provides the best results):
+
+```sh
+curl https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md >> AGENTS.md
+```
+
+Run `opencode` and dispatch your agents to complete your tasks!
+
+## Goose
+
+### Method 1: Configuration File
+
+Add to `~/.config/goose/config.yaml`:
+
+```yaml
+extensions:
+ container-use:
+ name: container-use
+ type: stdio
+ enabled: true
+ cmd: cu
+ args:
+ - stdio
+ envs: {}
+```
+
+### Method 2: Interactive Setup
+
+```sh
+goose configure
+```
+
+Then add a command line extension with `cu stdio` as the command.
+
+### Method 3: Goose Desktop
+
+Paste this URL into your browser:
+
+```
+goose://extension?cmd=cu&arg=stdio&id=container-use&name=container%20use&description=use%20containers%20with%20dagger%20and%20git%20for%20isolated%20environments
+```
+
+
+ Learn more: [Goose MCP
+ Extensions](https://block.github.io/goose/docs/getting-started/using-extensions#mcp-servers)
+
+
+## Cline
+
+### Add MCP Configuration
+
+Add to your Cline MCP server configuration JSON:
+
+```json
+{
+ "mcpServers": {
+ "container-use": {
+ "disabled": false,
+ "timeout": 60000,
+ "type": "stdio",
+ "command": "cu",
+ "args": ["stdio"],
+ "env": {},
+ "autoApprove": []
+ }
+ }
+}
+```
+
+### Add Agent Rules
+
+```sh
+curl --create-dirs -o .clinerules/container-use.md https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md
+```
+
+Learn more: [Cline Documentation](https://cline.bot/)
+
+## Qodo Gen
+
+### Setup Steps
+
+1. Open Qodo Gen chat panel in VSCode or IntelliJ
+2. Click "Connect more tools"
+3. Click "+ Add new MCP"
+4. Add this configuration:
+
+```json
+{
+ "mcpServers": {
+ "container-use": {
+ "command": "cu",
+ "args": ["stdio"]
+ }
+ }
+}
+```
+
+
+ Learn more: [Qodo Gen MCP
+ Documentation](https://docs.qodo.ai/qodo-documentation/qodo-gen/qodo-gen-chat/agentic-mode/agentic-tools-mcps)
+
+
+## Kilo Code
+
+### Add MCP Configuration
+
+Add at global or project level:
+
+```json
+{
+ "mcpServers": {
+ "container-use": {
+ "command": "replace with pathname of cu",
+ "args": ["stdio"],
+ "env": {},
+ "alwaysAllow": [],
+ "disabled": false
+ }
+ }
+}
+```
+
+
+ Kilo Code allows setting MCP servers at the global or project level. Learn
+ more: [Kilo Code MCP
+ Documentation](https://kilocode.ai/docs/features/mcp/using-mcp-in-kilo-code)
+
+
+## OpenAI Codex
+
+### Add MCP Configuration
+
+Add to `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.container-use]
+command = "cu"
+args = ["stdio"]
+env = {}
+```
+
+
+ Learn more: [OpenAI Codex
+ Documentation](https://github.com/openai/codex/tree/main/codex-rs)
+
+
+## Warp
+
+### Add MCP Configuration
+
+In the Warp sidebar, under Personal → MCP Servers → New:
+
+```json
+{
+ "container-use": {
+ "command": "cu",
+ "args": ["stdio"],
+ "env": {},
+ "working_directory": null,
+ "start_on_launch": true
+ }
+}
+```
+
+Warp 2.0 introduces coding agents with MCP support.
+
+## Gemini CLI
+
+### Add MCP Configuration
+
+Add to `~/.gemini/settings.json` or `.gemini/settings.json`:
+
+```json
+{
+ "coreTools": [],
+ "mcpServers": {
+ "container-use": {
+ "command": "cu",
+ "args": ["stdio"],
+ "timeout": 60000,
+ "trust": true
+ }
+ }
+}
+```
+
+
+ Learn more: [Gemini CLI
+ Configuration](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/configuration.md)
+
+
+## General Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart your agent after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Some agents require explicit tool trust/approval
+ - Check your agent's MCP server logs
+ - Verify Container Use tools are enabled in agent settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file
diff --git a/docs/vscode.mdx b/docs/vscode.mdx
new file mode 100644
index 00000000..96b824fc
--- /dev/null
+++ b/docs/vscode.mdx
@@ -0,0 +1,82 @@
+---
+title: VSCode / GitHub Copilot
+description: "Setup guide for VSCode and GitHub Copilot with Container Use"
+icon: robot
+---
+
+## Configure MCP Server
+
+Update your VSCode settings with:
+
+```json
+"mcp": {
+ "servers": {
+ "container-use": {
+ "type": "stdio",
+ "command": "cu",
+ "args": ["stdio"]
+ }
+ }
+}
+```
+
+## Add Copilot Instructions (Optional)
+
+```sh
+curl --create-dirs -o .github/copilot-instructions.md https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md
+```
+
+
+ Watch the VSCode setup walkthrough
+
+
+
+ Learn more: [VSCode
+ MCP](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) | [GitHub
+ Copilot
+ MCP](https://docs.github.com/en/copilot/customizing-copilot/extending-copilot-chat-with-mcp)
+
+
+## Verification
+
+After setting up VSCode/GitHub Copilot, verify Container Use is working:
+
+1. **Check MCP Connection**: VSCode should recognize Container Use tools
+2. **Test Environment Creation**: Ask Copilot to create a new environment
+3. **Verify Isolation**: Multiple environments should work independently
+
+## Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart VSCode after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Check your VSCode MCP server logs
+ - Verify Container Use tools are enabled in settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file
diff --git a/docs/zed.mdx b/docs/zed.mdx
new file mode 100644
index 00000000..ccedf084
--- /dev/null
+++ b/docs/zed.mdx
@@ -0,0 +1,125 @@
+---
+title: Zed
+description: "Setup guide for Zed with Container Use"
+icon: robot
+---
+
+## Add Agent Rules
+
+First add the agent rules file, either as `.rules` in the root of your project or as one of the [other acceptable files/locations](https://zed.dev/docs/ai/rules?highlight=agent.md#rules-files).
+
+```sh
+curl -o .rules https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md
+```
+
+## Configure MCP Server
+
+Configure the Container Use MCP server in the Zed `settings.json`. Provide the absolute path to the `cu` executable:
+
+```json
+"context_servers": {
+ "container-use": {
+ "source": "custom",
+ "command": {
+ "path": "/opt/homebrew/bin/cu",
+ "args": ["stdio"],
+ "env": {}
+ }
+ }
+}
+```
+
+## Add Container Use Agent Profile (Optional)
+
+To lock the Zed agent out of your host system, you can create a dedicated agent profile that only enables Container Use tools. Add this to your `settings.json` under the `agent` section:
+
+```json
+"agent": {
+ "profiles": {
+ "container-use": {
+ "name": "Container Use",
+ "tools": {
+ "fetch": true,
+ "thinking": true,
+ "copy_path": false,
+ "find_path": false,
+ "delete_path": false,
+ "create_directory": false,
+ "list_directory": false,
+ "diagnostics": false,
+ "read_file": false,
+ "open": false,
+ "move_path": false,
+ "grep": false,
+ "edit_file": false,
+ "terminal": false
+ },
+ "enable_all_context_servers": false,
+ "context_servers": {
+ "container-use": {
+ "tools": {
+ "environment_create": true,
+ "environment_add_service": true,
+ "environment_update": true,
+ "environment_run_cmd": true,
+ "environment_open": true,
+ "environment_file_write": true,
+ "environment_file_read": true,
+ "environment_file_list": true,
+ "environment_file_delete": true,
+ "environment_checkpoint": true
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+This profile ensures your agent can only use Container Use tools, preventing it from modifying your local files directly.
+
+Next open the Zed Agent Panel ✨ in the lower right, select the "Container Use" profile from the dropdown to the left of the model dropdown, and prompt away!
+
+## Verification
+
+After setting up Zed, verify Container Use is working:
+
+1. **Check MCP Connection**: Zed should recognize Container Use tools
+2. **Test Environment Creation**: Ask Zed to create a new environment
+3. **Verify Isolation**: Multiple environments should work independently
+
+## Troubleshooting
+
+
+
+ - Verify the `cu` command is in your PATH: `which cu`
+ - Check MCP configuration syntax
+ - Restart Zed after configuration changes
+
+
+
+ - Ensure Docker is running and accessible
+ - Check file permissions for configuration files
+ - Verify `cu stdio` command works: `echo '{}' | cu stdio`
+
+
+
+ - Check your Zed MCP server logs
+ - Verify Container Use tools are enabled in settings
+
+
+
+## Next Steps
+
+
+
+ Return to the quickstart guide to create your first environment
+
+
+ Get help and share experiences in #container-use
+
+
\ No newline at end of file