Skip to main content
The console at 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

Press Cmd+K 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:

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 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.