> ## Documentation Index
> Fetch the complete documentation index at: https://docs.labelbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Managed Agents

> Run agents in managed sandboxes with tools and credentials, follow every step, and collect the files they produce.

Recursion Managed Agents runs agents that need a sandbox, tools, and more than one model turn. Each session keeps a durable record that you can inspect, continue, or audit.

> [!WARNING]
>
> Recursion Managed Agents is designed around persistent, stateful sessions. Agent sessions may remain active over extended periods, resume after interruptions, and retain conversation history, sandbox state, and generated outputs on the server.
>
> Because Managed Agents relies on this server-side state, it is currently not supported for customers requiring Zero Data Retention (ZDR) or HIPAA Business Associate Agreement (BAA) coverage. Customers with an active BAA or ZDR arrangement, or with a use case that requires either, cannot use Recursion Managed Agents at this time.

## What do you want to do?

> **[Run your first session](/recursion/quickstart.md)**
>
> Create an API key, an environment, and an agent, then start a session and read the reply. About 10 minutes.

> **[Understand the model](/recursion/how-it-works.md)**
>
> See how agents, environments, sessions, vaults, and integrations fit together.

> **[Build in the console](/recursion/console.md)**
>
> Find the screen for each setup, launch, and inspection task.

> **[Call the API](/recursion/api.md)**
>
> Authenticate REST requests and learn the retry and paging rules.

> **[Connect your apps](/recursion/integrations.md)**
>
> Let agents work in 164+ apps, choose their tools, or add any MCP server.

> **[Split work across agents](/recursion/multi-agent.md)**
>
> Delegate to subagents or let a team share a task board.

> **[Automate sessions](/recursion/automations.md)**
>
> Run agents on a schedule, by hand, or when Slack or GitHub sends an event.

> **[Connect a coding agent](/recursion/ai-coding-agents.md)**
>
> Let your AI coding agent read these docs and call the API for you.

> **[Fix a problem](/recursion/troubleshooting.md)**
>
> Match an error code or symptom to its cause and fix.

## What you can do

| Capability | What it gives you |
| - | - |
| Versioned agents | A model, system prompt, tools, skills, MCP servers, and credential grants, saved as immutable versions. See [Agent setup](/recursion/agents.md). |
| Managed sandboxes | A workspace per session tree, with a setup script you verify once, sized compute, and an egress policy. See [Environments](/recursion/environments.md). |
| Durable sessions | Every message, tool call, and result is recorded. Stream it live, resume after it ends, or send a follow-up. See [Sessions](/recursion/sessions.md). |
| Work in your apps | Connect GitHub, Slack, Jira, Confluence, and 164+ catalog apps such as Salesforce, Zendesk, HubSpot, and Snowflake, choose which tools agents may use, and grant them to agents. See [Integrations](/recursion/integrations.md) and [GitHub access](/recursion/github.md). |
| Files in and out | Upload inputs once and attach them to any session, show images and documents in a message, and download every deliverable. See [Files](/recursion/files.md). |
| Automations | Start sessions on a schedule, from Slack or GitHub events, or by hand, with the same pinned agent version and credentials every run. See [Automations](/recursion/automations.md). |
| Credentials without pasting secrets | Vaults hold tokens and keys. MCP tokens are attached outside the sandbox. See [Vaults](/recursion/vaults.md). |
| Multi-agent work | Delegate to subagents, consult an advisor, or run a team with a shared board, all in one sandbox. See [Teams](/recursion/teams.md). |
| Deliverables | Agents save named files that are kept at the end of each turn, ready to preview and download. See [Artifacts](/recursion/artifacts.md). |
| Usage and cost | One cost per session, covering its helper agents, tools, and compute. See [Usage and cost](/recursion/usage-and-cost.md). |
| API keys and roles | Personal API keys scoped to your tenant or one organization, with role-based access checked on every request. See [API keys](/recursion/api-keys.md). |

## How it fits together

```mermaid theme={"theme":"css-variables"}
flowchart TD
  agent["Agent version"] --> session["Session: your task"]
  environment["Environment"] --> session
  grants["Vaults and<br>integrations"] --> session
  session --> sandbox["Sandbox"]
  session --> events["Event log"]
  session --> deliverables["Deliverables"]
```

You start a session with an agent and an environment. The session freezes both, so later edits never change work in progress unless you [move the session to another agent version](/recursion/sessions.md#move-a-session-to-another-version). The agent works in its sandbox, every step lands in the event log, and the files it saves are kept as deliverables. [How it works](/recursion/how-it-works.md) explains each piece.

## When to use Managed Agents

Use Managed Agents when the work needs one or more of these:

* Several model turns and tool calls.
* A shell, files, package installation, or a browser in a sandbox.
* Work in other systems, such as Salesforce, Jira, or Snowflake, an API with a token, or an MCP server.
* A durable record you can review, audit, or continue later.

For a single model response with no tools or sandbox, call the model directly instead.

## Next steps

> **[Quickstart](/recursion/quickstart.md)**
>
> Run your first session in the console or with cURL.

> **[How it works](/recursion/how-it-works.md)**
>
> Learn the concepts and see the session and credential flows.

> **[API conventions](/recursion/api.md)**
>
> Set up a REST client and learn the shared request rules.

> **[Glossary](/recursion/glossary.md)**
>
> Look up any term used in these docs.