> ## 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. # Build in the console > Create an agent, prepare its environment, launch a session, and find every screen in the Recursion console. The [Recursion console](https://recursion.labelbox.com) 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](/recursion/organizations-and-roles). ## Follow Get started Until you finish it or dismiss it, **Sessions** shows **Get started** under its heading. It numbers the steps to a first session: create an agent, set up an environment, and launch a session. Creating an API key is an optional fourth step. The next step's button is highlighted. Get started first says how agents, environments, and sessions fit together, then lists the steps. * A step shows **Done** once your organization has an agent, an environment, or a session, or once you have an active API key. * Get started goes away once your organization has an agent, an environment, and a session, whether or not you have an API key. * **Create agent** opens the create form on its starting points. **Open Environments** and **Open API keys** open those pages. **Launch session** opens the launch form once you have an agent and an environment. * Links under the steps open the [Quickstart](/recursion/quickstart) and the guides to [connecting a coding agent](/recursion/ai-coding-agents) and [automating your agents](/recursion/automations). * **Dismiss** hides it for you in this browser. * Members who can view but not create see the same introduction and the automations guide link without the steps, until the organization has an agent. ## Create an agent Start from a template, which also creates a paired environment, or build an agent yourself. 1. When your organization has no agents and **Get started** is not showing, **Sessions** shows starter cards. **Create agent** in **Get started** offers the same choices. 2. Choose **Issue fixer** or **PR reviewer** to start with an agent definition and a paired environment. 3. Coding templates ask you to connect GitHub and select the repositories the agent may use. 4. Click **Create and launch**. This saves both resources and opens the launch form. 5. Review the prefilled task, then click **Launch session**. 1. Open **Agents**, click **Create agent**, and choose **Blank**. 2. Set a model and system prompt. 3. Add tools and integrations as needed. The Skills, Multiagent, Credentials, and Tags sections start as summary rows while they hold defaults; open a row to change it. 4. Save the agent. Saving an agent publishes a new version. Sessions already running keep the version they started with. The [Quickstart](/recursion/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](/recursion/environments). ## Give agents access * **Integrations**: connect GitHub or another supported app, then grant the connection in an agent's **Integrations** section. See [Integrations](/recursion/integrations). * **Credential vaults**: store tokens and secrets. Secret values are write-only in the console. See [Vaults](/recursion/vaults). * **Skills**: add reusable instructions and attach them to an agent. See [Skills](/recursion/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**, enter an optional opening message. 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](/recursion/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](/recursion/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](/recursion/automations). * For API use, open **Settings** and choose **API keys**. A new key is shown only once. See [API keys](/recursion/api-keys). ## Find a screen The console opens on **Sessions** when no section is named in the link. A link to a section you cannot open lands on the first section available to you. Your account menu at the bottom of the sidebar lets you change tenant, switch color mode, or sign out. | Screen | Use it to | | - | - | | **Sessions** | Launch work, search and filter sessions, and read their transcripts and costs. | | **Agents** | Create or edit an agent's model, prompt, tools, skills, integrations, and default credential access. | | **Environments** | Choose the sandbox, its internet access, compute, and setup script. | | **Analytics** | See your organization's usage, completions, and environment startup over a time window. See [Analytics](/recursion/analytics). | | **Skills** | Create skills and groups for agents to load. | | **Credential vaults** | Store tokens and secrets for agents to use. | | **Integrations** | Connect GitHub, Slack, and apps from the built-in catalog, choose their tools, and grant them to agents. | | **Automations** | Start sessions on a schedule, from Slack or GitHub events, or by hand. The **Event sources** view lists the sources that deliver events, with their health, and lets you pause or resume them. | | **Billing** | Buy prepaid credits, manage cards, and read receipts. Appears only for billing managers. | | **Settings** | Open the settings area: **General**, **Members**, **Organizations**, **Enterprise SSO**, **API keys**, and **Audit log**. | 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. | Settings section | Use it to | | - | - | | **General** | See your tenant and its ID, manage its email domains, sign-in methods, and multi-factor authentication, edit your profile, or leave the tenant. See [Domains](/recursion/domains). | | **Members** | Find members, send and track invitations, answer requests to join, and change or remove tenant roles. | | **Organizations** | Create, archive, and open organizations, and manage who belongs to each one. See [Organizations and roles](/recursion/organizations-and-roles). | | **Enterprise SSO** | Let your people sign in through your company's SAML identity provider. See [Enterprise SSO](/recursion/enterprise-sso). | | **API keys** | Create and revoke your personal API keys. See [API keys](/recursion/api-keys). | | **Audit log** | Review who changed what in your tenant, filtered by action, person, organization, or date. | ## Next steps Run a first session in the console and with cURL. Every launch field and session control. Configure an agent's model, prompt, and tools. Set up the sandbox an agent runs in.