The Board tab, beside Studio, Cranks and Meetings above the scene, shows the project’s work as sticky notes in columns. A new board contains Backlog → To do → In progress → Done. Each card becomes a request when it starts: its title and description form the prompt, and the card then follows the status of that request. The board belongs to the selected project.
Add and edit cards
- Choose Add a card at the bottom of a column, type a title and choose Add card. Cards cannot be added directly to an In progress column.
- Click a card to open it. Edit its title (up to 200 characters) and its description, which becomes the request text: give context, the expected result and constraints. Choose a note color if you want one, then Save.
- Drag cards to reorder them or move them to another column. The order inside a column is its priority. A column at its card limit refuses further cards.
- Delete a card from its dialog. A running card cannot be deleted or moved to another column until you stop its request.
Configure columns
Choose Columns in the board toolbar. Names are free; the type tells the team what a column means, where auto-run takes cards, where running cards go and where finished or failed cards land. Each column also has an optional description for the team, which agents read, and an optional card limit between 1 and 20.
| Type | Meaning |
|---|---|
| Backlog | Not ready yet. The team never starts these cards. |
| Ready | Auto-run starts cards from the top of the first ready column. When it is empty, the orchestrator picks the next ones from Backlog. |
| In progress | Each card here runs as one request. Moving a card here starts it. |
| To review | Finished or partial work waiting for your check, when such a column exists. |
| Blocked | Failed or stopped cards land here, when such a column exists. |
| Done | Completed work lands here when there is no review column. |
- A board holds up to 12 columns and 500 cards. Keep at least one In progress column and one Done column.
- A column that still contains cards cannot be removed: move its cards first.
- A column holding a running card must stay an In progress column.
- The default In progress column has a limit of 3 cards. Reorder columns with the left and right arrows in the Columns dialog, then choose Save columns.
Start, stop and finish a card
- Drag a card into In progress, or open it and choose Start now. The card is queued as a request with its title and description as the prompt. If the start fails, the card returns to its previous column.
- While its request runs, the card is locked in its column. Open it and choose Stop to stop the request, or Show request to follow it in the conversation.
- When the request completes, the card moves to the first To review column, or to Done if there is none.
- A partial result (open points remain, or the implementation is saved with review remaining) moves to To review, otherwise to Blocked, otherwise stays in In progress. A failed or stopped request moves the card to Blocked if such a column exists; otherwise it stays in In progress. The card shows the error or the open points.
These automatic moves apply only while the card is in an In progress column; a card you moved yourself afterwards stays where you put it. If its request is deleted, the card is unlinked and shows “Its request was deleted.”
Resume or start again
- Resume continues a failed, stopped or partial card’s own request, keeping its completed stages. For a request that finished with open points, it asks the team to fix them.
- Start again appears when the card text changed since its request started. The card runs the new text as a new request; the stopped request stays in History.
- A completed card started again always runs as a new request.
- Editing a card whose request is still queued, before any stage has started, updates that request’s text too. Once the request has started, it keeps its own text until the card starts again.
You can also choose Edit on the request message in the conversation. A request still in the queue takes the new text with Save. One that has already run uses Run edited request: it starts again from the beginning as a new request, and the old one stays in History. A running request must be stopped first. The linked card follows the new text and the new request.
Let auto-run start ready cards
Auto-run is a switch in the board toolbar. While it is on, the team works through the board on its own: whenever In progress has room under its card limit (3 by default), auto-run starts the top card of the first Ready column. A card added to To do later, by you or by a Trello or Jira sync, starts the same way. The In progress card limit is the only setting: it decides how many cards run at once. Without a limit, every ready card starts.
The orchestrator fills To do from Backlog
When the Ready column has nothing left to start and In progress has room, the orchestrator reads the Backlog and moves the cards to run next to the top of To do, most important first. Auto-run then starts them as usual. Without an enabled orchestrator, the planner does it, or else the first enabled agent. It uses that agent’s connection and model.
- The orchestrator receives the backlog cards (title, description excerpt and note), the titles of running and finished cards, and nothing else. It does not read project files, uses no tools, and can only move backlog cards to To do. Each pass is one short model call.
- It picks at most as many cards as In progress has free places, and never more than 5. It may pick none, for example when the remaining cards are vague or depend on unfinished work, and says why.
- The toolbar shows the latest pass: who chose, when, and the reason. An unchanged backlog is not read twice; adding, editing or approving a backlog card, or turning auto-run off and on, lets the orchestrator look again.
- A pass that fails is reported in the toolbar and does not stop auto-run.
Cards that start after others
A card can wait for other cards: actions agreed in a meeting do, and agents can set it when they add cards. Until those cards are done, the card shows “After” and their titles, and auto-run neither starts it nor picks it from Backlog, wherever it sits in To do. A card counts as done in a Done column or once its request completed. A deleted card no longer holds anything back.
- Open the card to see what it waits for under Starts after. Remove a card from that list to stop waiting for it, then Save.
- Start now runs a waiting card anyway.
Cards that wait for your approval
- A card added by an agent shows Approve. Auto-run neither starts it nor lets the orchestrator pick it until you choose Approve on the card, or open it and choose Approve or Save. This keeps agents from feeding themselves work without end.
- The Ticketer proposes its next task this way after each successful request: one card in Backlog, noted “Proposed after” and the request’s title. Approve it to let the orchestrator schedule it, or delete it.
- On a board synced with Trello or Jira, a card an agent added is sent there only once you approve it.
- A card added or rewritten in Trello or Jira shows To review and waits the same way, unless you trust the remote board (see below).
- When cards in To do wait for approval, the toolbar says how many.
When auto-run stops
- Any card that does not complete fully (partial, failed or stopped) pauses auto-run, and the toolbar shows why. The next card would otherwise inherit uncommitted files. Check the card, then turn auto-run back on.
- A start that fails also pauses auto-run. Auto-run also waits while the team is paused.
- Auto-run is turned off each time the project opens. It never resumes on its own after a restart.
Plan with AI
- Choose Plan with AI and describe the goal, the feedback to address or the feature to plan under “What should the team build?”.
- Choose Propose cards. Vopit sends the goal and the titles of existing cards (with their column) to your default connection, which proposes up to 20 cards. It does not read project files and uses no tools.
- Edit the proposed titles and descriptions, clear the cards you do not want, or choose Propose again.
- Pick the target column in Add to, then choose Add N cards. Nothing is added to the board before this step.
A default model must be configured in Settings → Connections. The planning prompt can be adjusted in the project profile JSON under generation.prompts.board (Settings → Project).
Let agents organize the board
In the agent editor, Board actions grants board_read, board_create, board_move and board_update. They work with the Vopit engine and native CLI engines. Like other tools, they follow each agent’s own grants; no agent has a privileged role.
| Action | What it does |
|---|---|
| board_read | Returns the columns with their ID, type, description and limit, the cards with their status and notes, and the auto-run state. It flags the card that started the current request. |
| board_create | Adds up to 20 cards at the bottom of a column, within its limit and the 500-card board limit. A card can name existing cards it starts after. |
| board_move | Moves a card to another column or position. |
| board_update | Rewrites a card’s title or description. |
- Agents never start, stop or delete cards. They cannot add a card to an In progress column, move a card into one, or move a running card. You and auto-run decide what runs.
- Agents read the column types and descriptions to choose where to place cards. Describe what each column is for to guide them.
- Cards created by an agent show “Added by” and the agent’s name, and wait for your approval before auto-run can run them.
- An agent cannot add a card whose title is already on the board, in any column. Agents that run after each request, such as the Ticketer, add one card per run by default.
Sync with Trello or Jira
- Choose Sync in the board toolbar and pick Trello or Jira. Trello needs the API key of a Power-Up you create in Trello and a token generated from that key. Jira Cloud needs your site (your-team.atlassian.net), your email and an Atlassian API token.
- Choose Connect, then the Trello board or Jira project.
- Under Columns, choose the Trello list or Jira status that matches each Vopit column. Vopit suggests matches by name; each list or status can be used once. Choose Not synced to keep a column local.
- Leave Sync automatically on, review the rules shown, then choose Start syncing.
- Title, description and column sync in both directions: every minute while Vopit is open, a few seconds after your changes, or when you choose Sync now. Card order within a column is not synced.
- Cards in mapped columns are created on the other side. Remote cards in lists or statuses you did not map are ignored.
- When a card changed on both sides between two syncs, Vopit’s version wins.
- Moving a card into the In progress list or status remotely never starts it: Vopit sends it back. A new remote card in that list lands in a ready column instead.
- Deleting a card in Vopit archives it in Trello, where you can restore it. Jira issues are never deleted, only unlinked. A card archived, deleted or out of scope remotely is unlinked in Vopit, never deleted.
- Jira syncs open issues and those finished in the last 30 days. New issues use the Task type when the project has one, and reach their status through the workflow’s transitions. A missing transition is reported and retried.
- Credentials are encrypted by your operating system and stay on this computer, for this project only. Disconnect unlinks every card, leaves cards on both sides and removes the saved credentials. Choosing another account, board or service also unlinks existing cards.
Storage and Quick actions
The board is stored in .vopit/history.sqlite with the project history. It is not included in a team export. In Quick actions (Ctrl/Cmd+K), you can search card titles and descriptions to jump to a card, turn board auto-run on or off, and add typed text to the board: “Add to To do: …” creates a card in the first Ready column, or in Backlog when there is none.