Skip to main content

​
Workspace

Your account. It holds your plan, your members, your Boxes and your agents, and it runs on one machine: a private computer in the cloud, isolated from every other account, that hosts every agent of the workspace and holds the files, the databases and the credentials they share. You can belong to several workspaces and switch between them from the pill in the top left corner of the app. An API key is scoped to exactly one workspace.

​
Box

A room of your workspace: on the board it is the rectangle your agents sit on. It groups them by team, by client or by project. A Box is instant and free, and you make as many as the work needs. It arranges agents, it does not separate them: every agent of the workspace runs on the same machine, and the shared folder and the shared database are common to all of them, whichever Box they sit in. Because a Box holds nothing of its own, moving an agent from one to another costs nothing: right-click it on the board and pick Move to Box, or ask the Rerun agent to do it. It keeps its files, its handle, its skills and its whole history.
The Rerun API calls a Box a space, in tool names like list_spaces and space_db_query. Same thing.

​
Agent

An AI worker inside a Box. It has:

​
Soul

The agent system prompt, written in markdown. It is the single most important thing about an agent. Edit it in the agent Settings tab, or let the agent rewrite it as it learns.

​
Skill

A written procedure the agent loads on demand, when the task matches its description. It is a folder: a markdown body plus optional reference files. Skills keep an agent sharp without bloating its prompt: only a one-line index of every skill is always in context, and the full text loads when it is needed. See Skills.

​
Memory

Durable facts the agent writes down and recalls later. Memories fade if nothing uses them, and each recall extends their life, so what matters stays and what does not quietly retires. Correct an agent once and it remembers the correction.

​
App

A ready-made integration with an external service: Stripe, Gmail, Notion, Slack and hundreds more. Installing one on an agent gives it that service tools plus a skill explaining how to use them. An app is installed per agent, not per Box. See Apps.

​
MCP server

The open standard Rerun apps are built on. When the library does not have what you need, you can register any MCP server on an agent yourself, with its own URL, headers or command.

​
Run

One execution of an agent. It starts when you send a message, when a scheduled task fires, when a webhook is called, or when another agent calls it. It ends when the agent is done, when it fails, when you cancel it, or when it pauses to ask you something. Every run records its steps, its tool calls, its tokens and its cost. Read them in the Monitoring and Logs tabs, or with get_run.

​
Session

A conversation thread with an agent. A run belongs to a session. Scheduled tasks and webhooks each open their own session, so an automated run never pollutes your chat.

​
Scheduled task

A recurring instruction, on a cron and in a timezone, or a one-off at a given date. When it fires, the agent runs with no user message and follows the instruction. See Automations.

​
Trigger

A public webhook URL that starts a run when it is called. The caller payload is handed to the agent alongside your instruction. The URL is the credential. See Webhook triggers.

​
Template

A packaged agent setup, published in the marketplace, that anyone can install into their own workspace in one click. It carries prompts, skills, scheduled tasks, app declarations and files, but never memories or credentials. Templates can be free or paid. See Templates.

​
Board

The isometric view that is the app itself. Boxes are drawn as rectangles, agents sit on them, and clicking an agent opens its panel.