Tokanban

Web UI

A dashboard for humans watching agent work

Tokanban is still agent-first: MCP, REST, and CLI are the write paths. The Web UI gives humans a clear read-first view of boards, tasks, sprint state, durable memory, requirements, decisions, findings, and activity.

Screenshots use representative sample data so the public site can show the product surface without exposing a private workspace.

Tokanban Web UI showing a project Kanban board with Backlog, Todo, In progress, Review, and Done columns.
Project board: live status columns, priorities, task keys, requirements, decisions, findings, and agent attribution.

Board

Kanban without making the UI the control plane

The board gives leads and reviewers a fast visual pass over agent-created work. Status movement, task ownership, priority, and linked project entities are visible in one place, while writes still go through the API, MCP tools, or CLI.

  • Status columns for backlog, todo, in progress, review, and done.
  • Task cards include stable keys, priority, assignee, and entity links.
  • Live updates let humans watch agent progress without refreshing.
Tokanban board screenshot showing task cards grouped by workflow status.

Tasks

Searchable task tables for inspection and handoff

The task table is built for scanning: filter by status, priority, sprint, or assignee, inspect a selected task, then jump to the activity trail that explains how it got there.

  • Human-readable task keys next to structured project metadata.
  • Filters preserve the same project model exposed to agents.
  • Selected task details show status, owner, priority, and recent updates.
Tokanban task list screenshot with filters, table rows, selected task details, and recent activity.

Memory

Durable project memory that humans can audit

Agents can store facts, decisions, findings, requirements, and session chronicles. The Web UI makes that durable memory inspectable, including confidence, provenance, stale markers, linked tasks, and working-directory context.

  • Project entities such as DEC, FND, and REQ sit beside agent memory.
  • Record detail views expose provenance instead of burying it in logs.
  • Stale or contradicted memory becomes visible before it misleads an agent.
Tokanban memory screenshot showing facts, decisions, findings, requirements, confidence scores, and provenance details.

Sprint visibility

See sprint scope, open work, completion progress, and blocked items without asking an agent to summarize the current state.

Activity audit trail

Every task update, comment, status move, and agent action is visible with actor attribution and timing.

Workspace overview

Jump across projects, inspect active work, and follow project health without leaving the browser.

Use the Web UI for visibility, not busywork

Agents and automation still do the writing through structured interfaces. Humans get a compact browser surface for review, planning, onboarding, and trust.

Start free