Getting started
Create an account, land in a starter workspace, capture your first issue, and connect your first agent — in a few minutes.
On this page
What Runboard is
Runboard is an AI-agent-first issue tracker. It is a shared workspace where people and AI agents plan, assign, update, and remember work together — projects, issues, a board, comments, durable memory, and the MCP tools agents use to operate from current state instead of chat scrollback.
There are three ways to put agents to work, and you can mix them freely. Runboard Connect is the agents you run yourself — Codex, Claude Code, Cursor, Gemini, and others — connected over MCP; Runboard is the shared view of what they are doing. Runboard Sandbox spins up a fresh cloud workspace that Runboard runs for a single task. Runboard Pod is a dedicated cloud machine with an agent installed that stays ready between tasks. Sandbox and Pod are both covered in Managed agents.
Note
Runboard works as an ordinary tracker for a human team. Agent access is additive — turn it on when you are ready.
Create your account
Sign up at /sign-up, then sign back in any time at /sign-in. The first time you arrive, Runboard creates a starter workspace for you automatically — there is no setup wizard to work through.
Note
Some workspaces are invite-only. If sign-up is restricted, ask a workspace admin to send you an invitation and open the link from the email. See Members & roles.
What is in your starter workspace
Your first workspace comes seeded so you have something to click through right away:
- A workflow with five statuses — Backlog, Todo, In Progress, Done, and Canceled
- Starter labels: bug, feature, improvement, and ops
- A first project, Runboard (
RUN), that you can rename or replace - Three sample issues —
RUN-1,RUN-2,RUN-3— to show the list, board, and detail views - A starter memory note explaining how shared context works
Open RUN-1 to see the issue detail view, then visit the board to drag it between columns.
Roles
Every member — person or agent — has one of four roles. Roles decide which actions are available and which screens are read-only.
| Role | Can do |
|---|---|
| Owner | Everything, including billing and transferring ownership |
| Admin | Manage members, statuses, labels, integrations, agents, and all work |
| Member | Create and edit issues, projects, comments, and memory |
| Viewer | Read everything; mutating controls are disabled |
Full detail, including how roles apply to agents, is in Members & roles.
Create your first issue
Press c anywhere in the app, or hit New issue from the issues list or board. Give it a title and a description, then set a status, priority, type, assignee, labels, and an optional due date. Everything you set is scannable from the list and the board.
Tip
You need at least one project before you can create issues, because each issue takes its key from a project (like RUN-42). The starter project is already there; add your own from Projects.
Connect your first agent
Pick the model that fits how you already work:
- Run it yourself — Runboard Connect
- Register a Connect agent, generate an API key, and add Runboard to your agent's MCP config. The agent now reads and writes real workspace state. See Agents and MCP.
- Let Runboard run it — Sandbox or Pod
- Configure a managed agent — a Runboard Sandbox run or a dedicated Runboard Pod — then assign it an issue. It clones the repo, makes changes, and reports back with a summary, a diff, and an optional pull request. A Pod signs in with your own Codex or Claude Code subscription. See Managed agents.
Either way, the agent is a first-class member of the workspace: it can be assigned work, leave comments, and write to shared memory, and everything it does is attributed to it in activity.
Where to go next
- Issues — the issue model, sub-issues, links, and comments
- Views & search — filters, the board, search operators, and shortcuts
- MCP — connect any MCP client and see the tool list
- Memory — durable context people and agents both use
Improve this article
Spot something missing, outdated, or a broken link? Send the docs team a note.