Skip to main content
The Recursion console is where you create agents, prepare environments, connect tools, launch sessions, and follow their work. Sessions started through the API appear here too.
Sign in to the console and choose the organization you want to work in from the switcher near the top of the sidebar. Every write action depends on your role. See Organizations and roles.

Start from Home

The console opens on Home. Describe what you want an agent to do in the box at the top, and the assistant designs the agent with you, sets it up once you approve its plan, and tries it in a test session. Or start from a template, as Create an agent shows. Until your organization’s first session has run, Home also shows two other ways to get there:
  • Build from your coding agent walks you through creating an API key and connecting your coding agent, which can then create agents and start sessions for you.
  • Or set up in the console lists the steps to a first session: create an agent, set up an environment, and run a session. The next step’s button is highlighted.
  • Each step is checked off once your organization has what it makes: an agent, an environment, or a session that ran to an answer.
  • The steps go away once all three are done. Creating an API key is not one of them.
  • Create agent opens the create form on its starting points. Open Environments opens that page. Launch session opens the launch form once you have an agent and an environment.
  • Links at the foot of Home open the Quickstart and the guides to connecting a coding agent and automating your agents.
  • Dismiss hides the steps for you in this organization, in this browser.
  • Members who can view but not create see a short Get started note instead, saying what the product is and who creates agents, until the organization has an agent. Their Home links only to the automations guide.

Create an agent

Start from a template, which also creates a paired environment, or build an agent yourself.
  1. On Home, under Start from a template, click a template such as Issue fixer or PR reviewer. The assistant asks the template’s setup questions, and any of its own it needs, such as who the agent is for or what it should focus on. It suggests the apps the agent needs and tailors the template’s instructions to your answers. To skip the questions, click Use defaults under the template instead.
  2. The assistant proposes the agent, a paired environment, and a sample task for review. With Use defaults, the plan opens ready to review, and coding templates first ask you to choose a GitHub connection.
  3. Review the plan, then click Approve and run. The assistant creates both resources and starts a test session.
To fill in the form yourself, open Agents, click Create agent, and choose a template. Coding templates ask you to connect GitHub and select the repositories the agent may use. Click Create and launch to save both resources and open the launch form, review the prefilled task, then click Launch session.
Saving an agent publishes a new version. Sessions already running keep their version until you move them. The Quickstart walks through the same flow without a template, in the console and with cURL.

Prepare an environment

Templates create a matching environment for you. For a custom one, open Environments, click Create environment, and set its name, internet access, compute, and optional setup script. A setup script must pass a test run before sessions can use the environment. See Environments.

Give agents access

  • Integrations: connect GitHub or another supported app, then grant the connection in an agent’s Integrations section. See Integrations.
  • Credential vaults: store tokens and secrets. Secret values are write-only in the console. See Vaults.
  • Skills: add reusable instructions and attach them to an agent. See Skills.

Launch a session

  1. Click Launch session on Sessions or on an agent’s page. The agent page preselects that agent.
  2. Under Configuration, check the agent and environment.
  3. Under Task, write the opening message: what the agent should do in this session.
  4. Expand Credentials, Team, Files, or Custom metadata when this session needs a change from its defaults, such as input files to copy into the sandbox. Changes in this form apply only to this session.
  5. Click Launch session to start the work.
Your tenant needs available credits to launch. If none are available, someone who manages billing can add them and you can retry. See Sessions for all launch fields and session controls.
The form remembers your last successful agent and environment. When there is only one choice and nothing remembered, it selects that choice for you.

Follow the work

Open a session to read its Transcript: messages, tool calls, and results arrive as the agent works. The header shows status and cost. The Files tab holds the session’s inputs and the outputs it saved, ready to preview or download. Send a follow-up from the composer, or use the session actions to interrupt or stop work. See Session operations.

Automate and use the API

  • To run agents on their own, open Automations and create one with a schedule or an event trigger. See Automations.
  • For API use, open Settings and choose API keys. A new key is shown only once. See API keys.

Find a screen

The console opens on Home when the link names no section, or a section you cannot open. Your account menu at the bottom of the sidebar lets you change tenant, open Account settings (and Tenant settings, for admins), switch color mode, or sign out.
In Settings, API keys is open to every member with Managed Agents access. What you can change in the other sections depends on your role.

Next steps

Quickstart

Run a first session in the console and with cURL.

Sessions

Every launch field and session control.

Agents

Configure an agent’s model, prompt, and tools.

Environments

Set up the sandbox an agent runs in.