Taskboard
The taskboard is the project task management view, and it can dispatch tasks to LanMate for execution.
Six Columns
| Column | Meaning |
|---|---|
| Backlog | New cards land here by default, not scheduled yet |
| To Do | Scheduled; dragging a card in triggers agent auto-claim |
| In Progress | Executing |
| In Review | Execution finished, waiting for you to review the diff and artifacts |
| Blocked | Missing dependencies or permissions, or blocked by something else |
| Done | Accepted, wrapped up and archived |
Tasks are draggable across columns.
Creating Tasks
- Click “New Task” at the top-right of the taskboard page
- Fill in the title, description, priority, and labels
- Assignee: yourself or an agent / expert profile
A new card lands in Backlog first. Dragging it to To Do triggers auto-claim, and the agent starts based on the task type; you can also drag it to other columns to move it manually.
Card creation and isolation: coding tasks in Git projects bind a lanmate/<card-id> branch and a dedicated worktree, so parallel tasks don’t interfere; office/design tasks and non-Git projects still run in the project directory. When a card finishes, the worktree is reclaimed, the branch is kept, and the card is flagged “pending merge branch”; deleting a card, deleting a project, or wiping the board all take the same reclaim path. Branches and worktrees can be inspected under Settings → Git.
Agent Dispatch
For tasks assigned to LanMate, click the “Dispatch” button:
- The agent reads the task title, description, and project context, and picks its own tool surface
- It creates a real session (visible in the sidebar; you can observe or step in)
- When it finishes normally, the task moves to “In Review” automatically; on error it moves to “Blocked” with an error comment; when you abort it manually, it goes back to “To Do”
- After you accept it, it moves to “Done”; if you reject it, it goes back to “In Progress”
Re-dispatching a task that is already running won’t interrupt it — the new instruction is queued and picked up after the current run finishes.
When the bound profile is an expert and the task explicitly selects “Expert persistent session”, dispatch routes to that expert’s forever-chat (not in the sidebar); otherwise it creates a separate forked session.
Task Details
Click a task card to open its details:
- Description, status, priority, labels, and assignee
- Comment area (LanMate’s activity during execution also shows here); comments carry two meanings—a plain note only records, while comment and execute hands the content to the running LanMate as an instruction
- Linked session (click to jump)
- Attachments
Chat to Task
In the right panel’s “Tasks” tab, click “Convert to task”: LanMate generates a task summary (title ≤20 characters, description ≤100 characters) prefilled into a confirmation dialog; after you confirm, it creates a board card and binds the current session.
Promote a MateBot item
An item in MateBot’s ledger can become a board card in one step: in the item row click “⋯ → Promote to board card” and pick a board project. The item becomes a card in Backlog and keeps its due time, owner, and linked session.
When the card finishes, it writes back to the item; the board can also jump back to the original item. The personal note and the project schedule stay on one thread instead of being tracked twice.
Node View & Backup
- Node view: task dependencies render as a relationship graph — what’s blocking what, at a glance
- Backup & migrate: export the board as a backup file and import it on another computer — no cloud involved end to end
Workflows
The board supports custom workflows (column transition rules), configured visually through the workflow editor at the top-right. Hard constraint at execution time: state transitions outside the workflow rules are rejected outright with the reason shown; batch status changes are all-or-nothing.