Kanban Board
A project can contain several boards. Each board has its own columns, default agent/model, optional external integration, and saved display state. A board attached to a project connection inherits the connection's remote target; one attached to a server connection selects its own.
Private boards and your own board display
When the project allows them, the + of the board selector offers New private board. A private board sits after the shared boards with a lock, is never the default board and carries no integration. It and its cards are visible to you only; moving a card to a shared board publishes it, and the reverse move is refused. From Project settings › Boards you can rename, delete or convert a private board to a shared one — irreversible.
Board display… (in the + menu) lets you choose which boards you show and in what order, for you only. At least one board stays visible. A hidden board stays reachable from the selector's dropdown, and opening one of its cards from a link shows it for the session.
Navigate the workspace
- Use the organization selector at the top to change scope.
- Use the left sidebar to open a project or create one.
- Use the board selector in the project header to switch boards.
- Open Views to save or reuse cross-project filters and layouts.
- Open Agents or press the configured shortcut (default display:
⌘Jon macOS) to review active and waiting agent conversations.
The bottom bar keeps recently opened cards as tabs. A card conversation can remain open while you move between boards.
Search cards
⌘P(Ctrl+Pelsewhere) opens the command palette. Before you type, it lists the cards waiting for you and your recent ones; once you type, it searches every project you can access, across organizations, whatever view is open.⌘F(Ctrl+F) searches the open project only, including the text of its conversations; with no project open, it searches the current view or organization.
A result shows the card number, its title with every occurrence of the searched term highlighted (accents ignored), and where it lives: organization (when it is not yours), project, board (when the project has several, or when it is archived) and column. On the right: the agent state when it needs a look (running, waiting, error) and the time since its last activity. When a card matches only by its prompt or a conversation message, the matching excerpt appears under the title.
Results are ranked by relevance (number or reference, then title, then prompt, then conversation), then by most recent agent activity. Opening a card from another organization switches to it.
Board presets and filters
A thin bar sits above the columns. On the left, the presets of the board as tabs; on the right, a search field, the card counter and the Archived / Trash drawers.
- All shows every card. Mine shows the cards assigned to you and only appears when you are signed in.
- Filter refines the current preset: assignee (you, any member, unassigned), labels, agent state (running, waiting for an answer, in error, done, idle), priority, "created by me", "unread only". Dimensions combine with AND; values inside a dimension combine with OR.
- The search field matches the title, the prompt preview and the
#id, accents ignored. Press/to focus it. - Cards that do not match are hidden. Each column header then reads
n / total, and the counter on the right does the same for the board. Column-wide actions such as Clean all and Archive all are held back while a filter is active, since they act on the hidden cards too.
Filters are remembered per board on this device. To keep a combination, click Save, which appears as soon as the filter departs from the active preset: give it a name (32 characters at most) and a scope.
A preset is not a view: a view groups projects in the workspace, a preset remembers a filter on a board.
| Scope | Who sees it | Where it lives |
|---|---|---|
| Personal | You only, on this board | Your user settings, synchronized between your devices |
| Shared with the board | Every member of the board | The board itself; anyone who can edit the board can create, rename, update or delete it |
Once you change a preset's filter, Save and Restore appear next to Filter. On All or Mine, Save creates a preset; on a preset, it updates it, or saves a personal copy when you cannot edit the shared one. Restore goes back to the saved filter. Right-click a tab to rename, share, unshare, copy or delete a preset.
Assignees
A card can carry several assignees, chosen among the project members. Assign from the card's context menu, from the bulk action bar when several cards are selected, or when creating or editing a card. Assignees appear as round avatars on the tile, next to the creator's square avatar. Anyone who can edit the backlog can assign; readers cannot.
On a card tracked against a provider, the person the provider assigned also appears — on the tile and, in the edit dialog, beside the assignee picker. That face is the provider's to change, not stib's: it cannot be removed from here, and its tooltip says so. The edit dialog also signs the card under its title with who created it (the item's author on a tracked card, the stib user otherwise) and when.
Column modes
The mode is chosen when the column is created and controls what the agent may do when a card enters it.
| Mode | Behavior |
|---|---|
| Passive | Holds work without starting an agent; often used for backlog and done states |
| Discussion | Starts an agent that answers and explores without changing the code; what it produces (a mockup, a report) is delivered in the conversation |
| Plan | Starts an agent that explores without changing the code, then proposes a plan you approve before it runs |
| Development | Starts an execution agent with normal development permissions |
Any column that starts an agent can also run a skill discovered by the server, for every card that enters it and within the limits of its mode: an interview in Plan, spec drafting in Discussion, a review in Development. The skill can change after creation; the mode stays fixed, except between Discussion and Plan.
The visible name is independent from the mode. A column called “Review” can be passive, a discussion or development work, with or without a skill, depending on the workflow you want.
Configure a column
Open the column menu and select Configure column. Which tabs appear depends on the column type:
- General — name, mode, skill, auto-mode action, color, icon, and width;
- Behavior (passive columns) — column role, actions on entry and exit, header bulk buttons;
- Agent and Automations (other modes) — default credential, model per runner and prompt behavior; status conditions, automatic responses and move rules. A card entering the column takes the model it sets for the card's runner, replacing a model chosen by hand on the card; the model can be changed again in the conversation;
- Webhooks — actions fired when cards enter or leave;
- Sort — manual or field-based ordering;
- Advanced — pipeline participation and column deletion;
- History — the column audit log, if your role grants access to it.
Column role
The Role and access section affects exactly one role: the product owner. It lives under Behavior for a passive column, and under General for every other type.
- Open to product owners — they create, edit, delete and move cards here. On an active column (discussion, plan, development) they can also write to the agent and stop a run they started.
- Closed — only contributors and admins write here.
A product backlog is open by default, and the switch is locked there: it is the product owner's column by definition.
A product owner can never move a card out of the columns opened to them: both the source and the target must be open. Archiving, locking, marking done, retrying, and a card's worktree, terminal and credential stay with the team.
The case the setting exists for: a Discussion column named "Spec drafting", with its skill, opened to the product owner. They write their request in the backlog, drag it into the workshop, and the agent helps them turn it into a spec — without ever touching the code. Opening a Development column stays possible, with a warning: it runs agents that write code and create branches.
The setting hides nothing: a product owner sees the whole board either way, they are simply read-only elsewhere. The permission table shown under the switch sums it up.
Clicking a card in a passive column opens its title and prompt as long as no agent has worked on it: that is how a product owner writes their cards. Once an agent has started, the click opens the conversation; Edit in the card's right-click menu still opens the title and prompt. Other columns always open the conversation.
Some settings depend on the mode: the auto-mode action only applies to a Plan column.
Column after plan (General tab, any active column): an approved plan goes to this column before any other rule, including for a card in auto mode. The plan bar then offers it in one click, with a chevron to pick another column instead. A board has at most one: turning it on for a column takes it away from the previous one, and the row names the column that holds it today.
A column with a skill always invokes it first, and the Agent tab decides what follows it: the card's prompt (the default — with its attachments and its approved plan when it has one), no argument (the skill is invoked bare, for the ones that find their own context, like a review reading the Git diff), or a template you write with , and . The rule is the same in all three cases: what the body does not name is not sent. , the former name of , is still accepted.
Groups and full-width mode
Columns can contain groups to separate streams of work without creating another board. A group can be collapsed and reordered. Use View full width from a column menu when one stage needs more room.
Board templates and history
Create a board from a server template or build it manually. Project settings let you manage boards; column and board history help explain configuration changes. When attaching a board to a project connection, the remote target is inherited from the connection and shown read-only, so the "select remote project" step only exists for server connections; a board keeps the target it was attached with even if the connection is re-pinned later. Deleting or restructuring a board can affect automation and imported external items, so review integration mappings first.