Set Up Your Agent

Install Cap, authenticate with least privilege, and connect your preferred agent

Agent-readable page: You can send this URL to your agent. It should follow the verification and confirmation rules below, never overwrite an existing agent configuration blindly, and stop for you when a browser or secure terminal handoff is required.

One prompt setup

Make Cap Your Agent’s Video Assistant

Copy one prompt into Codex, Claude Code, Cursor, OpenCode, or any shell-capable agent. It installs Cap, connects the full skill and MCP, authenticates safely, and teaches your agent to record, share, search, transcribe, summarize, and manage Cap for you.

Installs the Cap CLI
Adds the full Cap skill
Connects local MCP
Verifies access and capabilities

Set up Cap as my complete video assistant, then use it to help with the task at the end.

Read these pages and treat them as operating instructions:
- https://cap.so/docs/agents
- https://cap.so/docs/agents/setup
- https://cap.so/docs/agents/workflows
- https://cap.so/docs/agents/safety

Do not rely on remembered Cap commands. Discover the installed contract with cap guide --json and cap <command> --help. Use JSON stdout as the source of truth, stderr as diagnostics, exit code 1 as a runtime failure, and exit code 2 as invalid usage.

Set up Cap:
1. Identify my operating system and the agent you are running in. Select only the current agent; never install into every detected agent.
2. Run cap version --json. If the cap command is missing, show me the exact platform install command and what it changes, then wait for my confirmation before running it:
   - macOS or Linux: curl -fsSL https://cap.so/install-cli.sh | sh
   - Windows PowerShell: irm https://cap.so/install-cli.ps1 | iex
   Open a new shell if PATH changes, then verify cap version --json and cap guide --json.
3. Run cap auth status --json. If authentication is required, run cap auth login --json with the least-privileged creator profile and let me complete the browser approval directly. Use admin or full only when my task requires the additional scopes and I agree.
4. If you are Codex, Claude Code, or Cursor, preview the complete integration with:
   cap agents install --target <codex|claude|cursor> --component all --dry-run --json
   Show me the exact skill and MCP configuration paths and values. After I approve, apply the same command with --yes instead of --dry-run. This must install the full Cap skill and the local cap mcp serve integration without replacing unrelated agent configuration. If you are OpenCode or another MCP client, follow the setup page and merge only the documented local MCP entry.
5. Tell me if the agent must restart to load the new skill or MCP server. Continue the current task through the CLI when a restart is not practical.
6. Verify the setup with cap version --json, cap guide --json, cap auth status --json, and cap caps list --limit 1 --json. If MCP is loaded, list its Cap tools and confirm that passwords and storage credentials are not accepted as MCP inputs.

Use Cap as an ongoing helper. Learn the complete surface from the installed guide and skill, including:
- Recording: check cap doctor --json, discover inputs with cap targets --json, ask before capture, use the detached cap record start and cap record stop lifecycle, require recordingMetaExists: true, validate the .cap project, export it, ask again before upload, and return the verified share link.
- Understanding videos: use cap caps list for discovery, cap caps get for lightweight metadata and capabilities, and cap caps context for the complete title, AI title, summary, chapters, transcript, comments, reactions, views, sharing, permissions, and processing state. Cite useful transcript timestamps.
- Files and processing: stream transcripts with cap caps transcript, download recordings with cap caps download, and observe existing work with cap caps status or cap caps wait. Never claim that a read or wait started transcription or AI work.
- Collaboration and sharing: draft comments, replies, reactions, title changes, visibility changes, moves, and public-page changes; show me the exact proposal before posting or applying it.
- Full management: use cap account, cap organizations, cap library, cap notifications, cap analytics, cap developers, and cap jobs for profile, team, folder, space, storage, billing, analytics, developer, migration, and durable-operation workflows. Discover flags with --help instead of guessing.
- Complete local surface: learn cap screenshot, cap update, cap recordings, cap project, cap desktop, cap automations, and cap completions from the guide too. Treat every command listed by cap guide --json as supported, even when it is not named in this prompt.
- MCP and CLI: prefer MCP for structured reads, confirmed safe writes, resources, and browser handoffs. Use the CLI for recording, local files, secure prompts, passwords, S3 credentials, images, and newly issued developer credentials.

Operating rules:
- Start with read-only discovery. Before any mutation, upload, paid processing, recording, comment or reaction, sharing or visibility change, deletion, organization, billing, storage, developer, or credential action, show me the exact proposed action and wait for my explicit confirmation. Pass --yes or confirmed=true only after I confirm.
- Never ask me to paste passwords, CAP_AGENT_TOKEN, API keys, S3 credentials, or newly issued developer secrets into chat or MCP. Ask me to run the exact secure Cap command in my terminal. For a password-protected Cap, ask me to run cap caps unlock <id-or-url>.
- Preserve returned Cap, organization, folder, space, member, comment, and operation IDs. Never infer IDs from names or invent results.
- Wait for asynchronous operations with cap jobs wait and verify the affected resource before reporting success. Clearly separate what you verified from reasonable interpretation and anything you could not verify.
- Be proactive after setup: briefly report what is connected, suggest useful Cap workflows for my situation, and use existing Cap context before asking questions the library can answer.

My task: Set up Cap completely, tell me what you can now help me do, and ask which Cap task I want to start with.

cap agent setup

Set up Cap as my complete video assistant, then use it to help with the task at the end.

Read these pages and treat them as operating instructions:
- https://cap.so/docs/agents
- https://cap.so/docs/agents/setup
- https://cap.so/docs/agents/workflows
- https://cap.so/docs/agents/safety

Do not rely on remembered Cap commands. Discover the installed contract with cap guide --json and cap <command> --help. Use JSON stdout as the source of truth, stderr as diagnostics, exit code 1 as a runtime failure, and exit code 2 as invalid usage.

Set up Cap:
1. Identify my operating system and the agent you are running in. Select only the current agent; never install into every detected agent.
2. Run cap version --json. If the cap command is missing, show me the exact platform install command and what it changes, then wait for my confirmation before running it:
- macOS or Linux: curl -fsSL https://cap.so/install-cli.sh | sh
- Windows PowerShell: irm https://cap.so/install-cli.ps1 | iex
Open a new shell if PATH changes, then verify cap version --json and cap guide --json.
3. Run cap auth status --json. If authentication is required, run cap auth login --json with the least-privileged creator profile and let me complete the browser approval directly. Use admin or full only when my task requires the additional scopes and I agree.
4. If you are Codex, Claude Code, or Cursor, preview the complete integration with:
cap agents install --target <codex|claude|cursor> --component all --dry-run --json
Show me the exact skill and MCP configuration paths and values. After I approve, apply the same command with --yes instead of --dry-run. This must install the full Cap skill and the local cap mcp serve integration without replacing unrelated agent configuration. If you are OpenCode or another MCP client, follow the setup page and merge only the documented local MCP entry.
5. Tell me if the agent must restart to load the new skill or MCP server. Continue the current task through the CLI when a restart is not practical.
6. Verify the setup with cap version --json, cap guide --json, cap auth status --json, and cap caps list --limit 1 --json. If MCP is loaded, list its Cap tools and confirm that passwords and storage credentials are not accepted as MCP inputs.

Use Cap as an ongoing helper. Learn the complete surface from the installed guide and skill, including:
- Recording: check cap doctor --json, discover inputs with cap targets --json, ask before capture, use the detached cap record start and cap record stop lifecycle, require recordingMetaExists: true, validate the .cap project, export it, ask again before upload, and return the verified share link.
- Understanding videos: use cap caps list for discovery, cap caps get for lightweight metadata and capabilities, and cap caps context for the complete title, AI title, summary, chapters, transcript, comments, reactions, views, sharing, permissions, and processing state. Cite useful transcript timestamps.
- Files and processing: stream transcripts with cap caps transcript, download recordings with cap caps download, and observe existing work with cap caps status or cap caps wait. Never claim that a read or wait started transcription or AI work.
- Collaboration and sharing: draft comments, replies, reactions, title changes, visibility changes, moves, and public-page changes; show me the exact proposal before posting or applying it.
- Full management: use cap account, cap organizations, cap library, cap notifications, cap analytics, cap developers, and cap jobs for profile, team, folder, space, storage, billing, analytics, developer, migration, and durable-operation workflows. Discover flags with --help instead of guessing.
- Complete local surface: learn cap screenshot, cap update, cap recordings, cap project, cap desktop, cap automations, and cap completions from the guide too. Treat every command listed by cap guide --json as supported, even when it is not named in this prompt.
- MCP and CLI: prefer MCP for structured reads, confirmed safe writes, resources, and browser handoffs. Use the CLI for recording, local files, secure prompts, passwords, S3 credentials, images, and newly issued developer credentials.

Operating rules:
- Start with read-only discovery. Before any mutation, upload, paid processing, recording, comment or reaction, sharing or visibility change, deletion, organization, billing, storage, developer, or credential action, show me the exact proposed action and wait for my explicit confirmation. Pass --yes or confirmed=true only after I confirm.
- Never ask me to paste passwords, CAP_AGENT_TOKEN, API keys, S3 credentials, or newly issued developer secrets into chat or MCP. Ask me to run the exact secure Cap command in my terminal. For a password-protected Cap, ask me to run cap caps unlock <id-or-url>.
- Preserve returned Cap, organization, folder, space, member, comment, and operation IDs. Never infer IDs from names or invent results.
- Wait for asynchronous operations with cap jobs wait and verify the affected resource before reporting success. Clearly separate what you verified from reasonable interpretation and anything you could not verify.
- Be proactive after setup: briefly report what is connected, suggest useful Cap workflows for my situation, and use existing Cap context before asking questions the library can answer.

My task: Set up Cap completely, tell me what you can now help me do, and ask which Cap task I want to start with.

The prompt above can perform this setup with you. The rest of this page documents every step for manual installation and troubleshooting.

Install the Cap CLI

The CLI ships with Cap Desktop, so both stay on the same version.

From Cap Desktop

Open Settings → Command Line → Install CLI.

macOS or Linux

curl -fsSL https://cap.so/install-cli.sh | sh

Windows PowerShell

irm https://cap.so/install-cli.ps1 | iex

The installer adds cap to your PATH and installs Cap Desktop when it is missing. Open a new terminal after installation, then verify the binary:

cap version --json
cap guide --json

Authenticate with least privilege

First inspect the current state:

cap auth status --json

If authentication is required, authorize Cap in your browser:

cap auth login --json

Profile	Use it for
`creator`	Caps, uploads, comments, library, analytics, notifications, and profile tasks
`admin`	Creator access plus organization members, settings, billing, and storage integrations
`full`	Admin access plus developer apps, credentials, videos, and credits

cap auth login --profile admin --json
cap auth login --profile full --json

Cap CLI credentials are stored by the operating system when available. CAP_AGENT_TOKEN is supported for headless environments, but do not paste tokens into an agent conversation or commit them to a project.

Codex

Preview exactly what Cap will change:

cap agents install --target codex --component all --dry-run --json

After reviewing the paths and values, apply the integration:

cap agents install --target codex --component all --yes --json

This installs the Cap skill and adds a local cap mcp serve entry to Codex's configuration. Restart Codex so it reloads the integration.

Claude Code

cap agents install --target claude --component all --dry-run --json
cap agents install --target claude --component all --yes --json

Review the preview first, then restart Claude Code after applying it.

Cursor

cap agents install --target cursor --component all --dry-run --json
cap agents install --target cursor --component all --yes --json

Review the preview first, then restart Cursor after applying it.

OpenCode

OpenCode can use Cap immediately through its shell tools: paste the agent prompt and let it call cap guide --json.

To use Cap as a local MCP server too, merge this entry into your opencode.json configuration:

{
	"$schema": "https://opencode.ai/config.json",
	"mcp": {
		"cap": {
			"type": "local",
			"command": ["cap", "mcp", "serve"],
			"enabled": true
		}
	}
}

Do not replace unrelated OpenCode settings. After merging the entry, restart OpenCode and check the server:

opencode mcp list

See OpenCode's local MCP documentation for configuration details.

Any other agent or MCP client

If the agent can run shell commands, no integration is required. Give it the copyable prompt.

For an MCP client that supports local stdio servers, configure:

{
	"command": "cap",
	"args": ["mcp", "serve"]
}

Keep cap mcp serve on stdio. Its stdout is reserved for MCP protocol messages.

Verify the full setup

Ask the agent to run these read-only checks:

cap version --json
cap guide --json
cap auth status --json
cap caps list --limit 1 --json

A correct setup has:

valid JSON on stdout;
a successful authenticated status before account-backed work;
either a Cap result or an empty list from the library check, not a guessed answer;
no secret value printed by cap auth status;
no changes made during verification.

If MCP is installed, also ask the agent to list the available Cap tools. It should find read tools such as caps_list and caps_context. Passwords and storage credentials should not appear as MCP inputs.

Continue with Agent Workflows.