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

# Console

> paddock's web console: API keys, a Playground to talk to agents, and every template, agent, session, model, and trigger of your organization.

The console at [console.paddock.build](https://console.paddock.build) is where you get an API key, try an agent before writing any frontend, and find out why a turn failed. It calls the same public API and uses the same client SDK your application does.

## Sign in and organizations

You sign in with your own account. Everything in the console belongs to an **organization**: members of one organization share its templates, agents, sessions, triggers, model providers, and API keys, and every member has the same rights. The organization switcher in the sidebar changes which organization you act on; **Settings** manages its members and invitations.

## Places

| Place | What it does |
| - | - |
| **Overview** | A three-step guide: log in with the paddock CLI from your terminal, ask your coding agent to build a template and an agent, and try the agent in the Playground. Each step is checked against your organization's real state. Sample templates are listed below it |
| **Playground** | A chat page on the client SDK. Pick a template, talk to it, and inspect the session as it runs |
| **Agents** | Every agent with its status, harness, model, template, and session count. An agent's page shows its sessions, files, memory, capabilities, and environment, and deletes it |
| **Sessions** | Every session of the organization, however it was created, filterable by agent, metadata, and creation time. Each opens read-only with the Playground's inspector |
| **Triggers** | Webhook endpoints, their rules with an editor and a test panel, and every delivery with each rule's outcome and a Replay |
| **Templates** | Every template and version as YAML, and an editor that shows a document as a form and as YAML side by side |
| **Models** | paddock's models and your own model providers: add a provider with its key, test it, and edit its models |
| **API Keys** | Create and revoke your organization's API keys |
| **Settings** | The organization's members and invitations |

Press <kbd>Cmd</kbd>+<kbd>K</kbd> to go to any place, or paste a full `agt_`, `ses_`, or `trg_` ID or a template name to open it.

## Playground

The Playground is a chat with an agent, with an inspector beside it. Pick a template in the message box and send a message: the console reuses an agent of that template version for the Playground, or creates one, then opens a new session on it. Later chats on the same version reuse the agent; a new version of the template gives new chats a new agent.

The inspector has five tabs:

| Tab | Shows |
| - | - |
| **Events** | Every event, live, grouped into turns, filterable by type. Each turn has a card with its status, attempt, duration, usage, and a waterfall of where its time went: waking the sandbox, starting the harness, the first token, each tool call, and the reply |
| **Files** | The agent's files under the session's working directory, refreshed when a turn ends |
| **Session** | The session's fields, and a button that mints and copies a one-hour session token |
| **Status** | The [harness status](https://docs.paddock.build/guides/harness-status.md) joined with the agent's capabilities. Install, disable, and remove plugins and MCP servers here; each change reaches the agent's sessions between their turns |
| **Code** | **Save as template** saves the agent's current configuration as a new template version or a new template, and snippets show the server code and the React component that use it |

## Template editor

**Templates → New template**, or **Edit** on a version, opens the editor: a form on the left and the YAML document on the right, kept in sync both ways. The YAML is checked against the template schema as you type, and a [dry run](https://docs.paddock.build/guides/templates.md#check-a-document-with-a-dry-run) runs 600 ms after each edit, showing every error at its field and naming the version **Save** would create. Unsaved text is kept in your browser as a draft.

## Triggers

A trigger's page has three tabs. **Overview** shows the URL and the secret, and rotates it. **Rules** lists the rules in order and opens the rule editor, whose test panel runs every rule on a sample event or a recent delivery as you type. **Deliveries** lists every request with each rule's outcome, linking to the session a rule delivered to; a delivery shows the request as it was received, and **Replay** delivers it again for real. See [Triggers](https://docs.paddock.build/guides/triggers.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.