Skip to main content
Resources define which external tools, repositories, and secrets each mode can access. Create project resources once, then assign only the resources that each mode needs.

​
Assign resources to a mode

Open Kapso Agent → Modes, select a mode, then open Resources. Only enabled resources assigned to that mode are available during a run. Assigned MCP tools appear directly in the current mode. Conflicting tool names receive a {connection}__{tool} namespace so both tools remain available. Assigning a GitHub repository gives the mode read-only file access and turns on its sandbox. Secret values never appear in the agent instructions.

​
Connect an MCP server

Add the server URL and its required headers under Kapso Agent → Resources. Use ${ENV:NAME} in a header to reference an encrypted project variable. Test the connection, then assign it to each mode that needs its tools.

​
Connect GitHub

Connect the GitHub App once, then select repositories for the project. You can also add a repository manually with its owner, name, branch, and personal access token. A personal access token is optional for public repositories. Assign each repository to the modes that need its files.

​
Environment variables

Create encrypted project variables under Kapso Agent → Resources. MCP connections can reference them in headers, and custom-mode sandboxes can receive selected variables. Kapso masks stored values in the settings page. It injects values only into the MCP connections and sandboxes that use them.

​
Sandbox

A sandbox gives a custom mode an isolated workspace. Open Kapso Agent → Modes, select a custom mode, then open Sandbox. Built-in modes use sandbox settings managed by Kapso. Assigning a repository to a custom mode keeps its sandbox enabled.