50 of 51 criteria have a sourced finding; 41 were also cross-checked by a second agent. Every comparison that includes Kander links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Terminal-only: a Go binary with a terminal kanban board and CLI on macOS (Homebrew), Linux (tarball, amd64/arm64) and Windows (zip, MSIX). No GUI, browser, mobile or editor extension.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
POSIX-only terminal backends (tmux, dsh, herdr) do not run natively on Windows; Windows uses the foreground/console backend.
notifications: kander notify and terminal backends deliver instructions to agent windows; OS notification support was not found.
9 atomic answers
Desktop os [supported] README quick start offers Homebrew for macOS, a Linux tarball for amd64 and arm64 and a Windows zip; Windows MSIX packaging for x64 and arm64 exists. Sources: kander:readme, kander:windows, kander:terminal.
Mobile apps [unsupported] No mobile app; the author's QuickTUI is a separate product. Sources: kander:srch-clients.
Notifications [partial] kander notify and terminal backends deliver instructions to agent windows; OS notification support was not found. Sources: kander:dispatch, kander:terminal.
Cross device continuity [unsupported] Local files and terminals only. Sources: kander:srch-clients.
Nine built-in agents (Codex, Claude, Grok, Cursor, Pi, Devin, OpenCode, Kimi, Droid) as embedded definitions, plus user-defined agents by argv templates; separate agents per card size and per reviewer role.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
model_providers: Model choice is each agent's own; multi-model routing is guidance.
5 atomic answers
Harnesses [supported] codex, claude, grok, cursor, pi, devin, opencode, kimi and droid are built in. Sources: kander:agents.
Model providers [partial] Model choice is each agent's own; multi-model routing is guidance. Sources: kander:routing.
Custom adapters [supported] Custom agents are defined in config.json with executable and argv templates, including a review template. Sources: kander:agents.
Session integration [supported] Kander launches the real CLIs in terminal panes through backends and tracks identity. Sources: kander:terminal, kander:dispatch.
Mixed harness operation [supported] Different execution agents for small and large cards and different reviewers for PMQA and Security. Sources: kander:routing.
Install via Homebrew, tarball or zip; first launch runs an interactive wizard and doctor; then discuss a task in an agent session and have it create the card. Needs Git; works with GitHub through gh or fully local; no cloud.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
no_git: A first-file lookup outside Git exists for configuration, but cards and worktrees need Git.
7 atomic answers
First task setup [supported] Four documented steps: discuss with an agent, confirm kanban launch, repeat, check with kander. Sources: kander:readme.
No git [partial] A first-file lookup outside Git exists for configuration, but cards and worktrees need Git. Sources: kander:agents, kander:readme.
Local git without remote [supported] Without origin every push and remote cleanup is skipped. Sources: kander:group-rules.
Hosted git [supported] gh integration browses and imports issues and can add result comments. Sources: kander:readme, kander:issue-import.
Prerequisite guidance [supported] kander doctor checks dependencies, agents, launchers and rules. Sources: kander:readme, kander:install.
Managed cloud setup [unsupported] No hosted cloud. Sources: kander:srch-remote.
Byo vps onboarding [unsupported] No remote setup. Sources: kander:srch-remote.
A large CLI for create, inspect, move, review, dispatch, coordinate and subscribe operations with JSON output; no REST API, SDK, MCP server or webhooks.
Scope
Surfaces: kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
api: No server API.
stability: No API stability policy documented; schema commands exist for review inputs.
Cards are created from agent conversations or the CLI and stored as markdown files under kanban/; GitHub issues import idempotently into the backlog and result comments go back; the local board stays authoritative.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
chat_git_triggers: No chat or Git event triggers.
sync: Import and result comments are explicit commands, not continuous sync.
supported_edits: Result comments may be added; closing needs separate confirmation.
9 atomic answers
Local creation [supported] kander new and agent-created cards through controlled commands. Sources: kander:readme, kander:guard.
Prompt intake [supported] Task intake rules turn a discussion into a card with goal and acceptance criteria. Sources: kander:readme, kander:card-content.
External import [supported] kander issue import and the g overlay. Sources: kander:issue-import.
Chat git triggers [unsupported] No chat or Git event triggers. Sources: kander:srch-sched.
Authoritative tracker [supported] The local kanban directory is authoritative; the GitHub issue stays external. Sources: kander:issue-import, kander:transactions.
Every card has a spec with goal and acceptance criteria and saved plans; reviews seal plans; task groups carry a dependency graph; cards persist in git-excluded files under kanban/.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
revisions: Coordinator checkpoints are versioned per revision; card edits rely on files and git.
7 atomic answers
Plans [supported] Card templates include plans and a review plan is sealed before done. Sources: kander:card-content, kander:review.
Acceptance criteria [supported] Cards state a goal and acceptance criteria and agents confirm them before launch. Sources: kander:readme, kander:card-content.
Revisions [partial] Coordinator checkpoints are versioned per revision; card edits rely on files and git. Sources: kander:coordinator, kander:transactions.
Implementation links [supported] Cards record TASK_BRANCH, RESULT and commit evidence in review dispositions. Sources: kander:card-content, kander:review.
Amendment [supported] Cards can be updated and review plans extended with extend-plan. Sources: kander:review, kander:transactions.
Task groups with members, dependency graphs, group branches and coordinator checkpoints; blocked dependencies are checked, including mainline containment; cards carry TYPE and SIZE. No arbitrary-depth epics.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
epics: Task groups act as epics.
hierarchy: Group to member cards; one level.
enforcement: Rules and check commands enforce; dispatch stops are rule-driven.
state_propagation: Coordinator reconcile derives group state from members.
task_to_epic: Cards can be regrouped; promotion is a rule-driven step.
Rule modules (base, code, git, issue, kanban, review, task-group, intake, reporting) are injected into agents; cards and review records persist; no managed cross-session memory.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
skills: Snippets for phases are loaded by rules; the Pi extension injects rules each turn.
project_docs: Cards hold specs and attachments; no doc store.
memory: Coordinator checkpoints store orchestration facts; no general memory.
scope: Rules are global or project-scoped.
provenance: Rule state hashes are recorded.
correction: Edit rules files; doctor detects local edits.
freshness: Doctor reruns once per binary version and refreshes embedded rules.
Freshness [partial] Doctor reruns once per binary version and refreshes embedded rules. Sources: kander:install.
Takeover continuity [supported] Cards, checkpoints and review records let another agent take over a card or group. Sources: kander:readme, kander:coordinator.
File-based kanban with Backlog, Todo, Working, Review, Done and archived/trash; cards have TYPE, SIZE, group, owner and result; board filter and search; GitHub issue overlay; no comments, priorities or assignees beyond OWNER.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
discuss: Standalone chat sessions; no comment threads.
prioritize: SIZE and TYPE; no priority field.
label: TYPE and TASK_GROUP fields.
assign: OWNER, SESSION and WINDOW fields record the agent.
17 atomic answers
Create [supported] kander new and agent-created cards. Sources: kander:clicode.
Assign [partial] OWNER, SESSION and WINDOW fields record the agent. Sources: kander:card-content.
Search [supported] / filters and searches cards. Sources: kander:readme.
Filter [supported] Board filter and search. Sources: kander:readme.
Archive [supported] archived and trash states. Sources: kander:guard.
Reopen [supported] move between states. Sources: kander:readme.
Project epic views [supported] Task group views on the board. Sources: kander:readme.
Idea parking [supported] Backlog cards wait until started. Sources: kander:readme.
Explicit dispatch [supported] m menu or kander start launches a card. Sources: kander:readme.
Task session separation [supported] Cards are separate from agent sessions, recorded in SESSION and WINDOW. Sources: kander:card-content, kander:dispatch.
Agents are expected to create, update and move cards only through controlled kander commands (new, move, review, coordinator, dispatch); the write guard blocks direct file creation; humans see the same board; attribution is by OWNER and review records.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
assign: OWNER field.
attribution: OWNER and SESSION fields; review runs record roles.
permissions: Write guard and authorization for coordinator writes.
14 atomic answers
Shared ids [supported] Same task_id for humans and agents. Sources: kander:transactions.
Read [supported] kander show --json and list. Sources: kander:clicode.
Create [supported] kander new through controlled commands. Sources: kander:guard.
Several agents run in parallel in separate terminal windows and worktrees; parallelism is bounded by file-overlap rules rather than a numeric cap; the board shows working, review and done cards.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
quotas: No numeric concurrency quota found.
observed_concurrency: Maintainer reports one developer with six agents over 90 days; vendor claim.
5 atomic answers
Concurrent sessions [supported] Each card runs in its own terminal container/pane. Sources: kander:terminal, kander:readme.
Concurrent tasks [supported] Ready cards with isolated files run in parallel. Sources: kander:group-rules.
Quotas [unsupported] No numeric concurrency quota found. Sources: kander:srch-sched.
Observed concurrency [partial] Maintainer reports one developer with six agents over 90 days; vendor claim. Sources: kander:stats.
Status visibility [supported] Columns Backlog, Todo, Working, Review, Done and liveness checks. Sources: kander:readme, kander:check.
Cards are assigned to execution agents by size or routing rules; a coordinator agent claims a group; dispatch ids give at-most-once delivery; conflict-aware scheduling prevents overlapping writes; ownership recorded in cards.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
7 atomic answers
Human assignment [supported] The user starts a card with an agent. Sources: kander:readme.
Product-owned coordination: a coordinator agent takes over a task group with kander coordinator, dispatch, notify and subscribe, delegates to member agents in separate panes, reads receipts and review results; roles, model choice and cross-harness routing are configured.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Orchestration owner [supported] Kander ships the rules, commands and checkpoints; the coordinator is a third-party agent. Sources: kander:coordinator, kander:readme.
Activation [supported] Ask an agent with Kander rules loaded to act as coordinator for a task group. Sources: kander:readme.
Task cards can be handed off, stopped and resumed; the coordinator reconciles after crashes; board menu moves cards; chat sessions allow discussion; no push notifications.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
pause: Stop the agent and keep the card; no pause verb.
notifications: Terminal-level only.
pending_decisions: Review dispositions and confirmations for closing issues.
escalation: Review findings block done; no timed escalation.
10 atomic answers
Pause [partial] Stop the agent and keep the card; no pause verb. Sources: kander:readme.
Stop [supported] Stop the agent and move the card. Sources: kander:readme.
Resume [supported] kander resume with --agent and coordinator recover. Sources: kander:coordinator.
Terminal board shows five columns with task groups, owners, size and type, plus a GitHub overlay; liveness and review progress commands; no dependency graph view.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
dependencies: Dependency graph is in cards and rules; board does not draw it.
attention: Review column and liveness checks.
workload: Card counts per column.
navigation_errors: check reports problems.
8 atomic answers
Fleet fixture [supported] The first-party screenshot shows a 59-card board. Sources: kander:readme.
Parent child [supported] Groups and members collapse on the board. Sources: kander:readme.
Dependencies [partial] Dependency graph is in cards and rules; board does not draw it. Sources: kander:group-rules.
Attention [partial] Review column and liveness checks. Sources: kander:check.
History [supported] Done column and archived cards. Sources: kander:readme.
Workload [partial] Card counts per column. Sources: kander:readme.
The flow is rule-driven and mandatory for kanban tasks, with configurable agents and reviewers; natural-language intake through agent conversations; discoverability through docs and doctor.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
quick_task: Quick discussions use standalone chat without a card.
growing_epic: Cards can be regrouped into task groups.
presets: Multi-model routing profile is an example, not a default.
in_run_changes: Review plans can be extended.
10 atomic answers
Quick task [partial] Quick discussions use standalone chat without a card. Sources: kander:readme.
Growing epic [partial] Cards can be regrouped into task groups. Sources: kander:group-rules.
Presets [partial] Multi-model routing profile is an example, not a default. Sources: kander:routing.
Natural language [supported] Cards come from agent conversation. Sources: kander:readme.
Local only: agents run in tmux, herdr, dsh or console panes on the same machine; the work survives closing the board but not the machine; no remote or cloud execution.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
byo_remote: Bounded search finds no remote host, VPS or cloud execution.
resources: Local hardware only.
region: No hosted region.
expiry: tmux sessions persist; console backend does not.
client_disconnect: Agents in tmux or herdr panes keep running when the board closes; foreground backend does not.
12 atomic answers
Local [supported] Panes on the local machine. Sources: kander:terminal.
Byo remote [unsupported] Bounded search finds no remote host, VPS or cloud execution. Sources: kander:srch-remote.
Self hosted [unsupported] Bounded search finds no remote host, VPS or cloud execution. Sources: kander:srch-remote.
Managed cloud [unsupported] Bounded search finds no remote host, VPS or cloud execution. Sources: kander:srch-remote.
Hybrid [unsupported] Bounded search finds no remote host, VPS or cloud execution. Sources: kander:srch-remote.
Git worktree per task card and group branches; terminal containers separate processes; reviewers run read-only with isolation arguments; agents run with permissions bypassed; no container or VM.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Agent definitions bypass approval and sandbox flags.
filesystem: Worktrees separate files; reviewer runtime directories are isolated.
12 atomic answers
Checkout [supported] Cards can use the main checkout for non-Git directories. Sources: kander:readme.
Probes have deadlines and cancellation; review runs are bounded; no turn, token or spend limits.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
provider_failures: Agent CLI errors such as rate limit or context exhaustion make the orchestrator mark the card blocked and report it, by rule; no automatic retry.
8 atomic answers
Time limits [partial] Probe deadlines only. Sources: kander:srch-cost.
Timeouts [partial] Probe and update-check deadlines. Sources: kander:install.
Retries [partial] Dispatch records retries and settle states. Sources: kander:dispatch.
Provider failures [partial] Orchestrator rules treat an agent CLI error in the pane (rate limit, context exhaustion, crashed tool) as a blocked card and report it to the user; no built-in retry or provider failover. Sources: kander:rv-blocked-agents.
Enforcement [partial] Probe deadlines are enforced. Sources: kander:install.
Dispatch, review and checkpoint records, liveness classification, check delivery and overlap, and maintainer production statistics; no usage export or cost statistics.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
logs: Dispatch and review records.
traces: Versioned checkpoints.
task_stats: Per-card records.
time_stats: STARTED_AT and FINISHED_AT on cards.
performance_method: No published measurements; Kander is not in ADEMark.
responsiveness: No published responsiveness measurements.
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
14 atomic answers
Task cost [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Session cost [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Child cost [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Epic cost [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Harness aggregation [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Billed vs estimated [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Tokens [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Subscription allowance [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Provider reconciliation [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Compute cost [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Refresh delay [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Alerts [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Export [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Drilldown [unsupported] Bounded search of internal/ and cmd/ for cost, usd, spend and budget code finds none relevant to agent spend. Sources: kander:srch-cost.
Agents run with approvals and sandbox bypassed (Claude --dangerously-skip-permissions, Codex --dangerously-bypass-approvals-and-sandbox, Cursor --yolo); the product gate is the review disposition and completion gate before done, a write guard on the board and a reviewer read-only posture.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No command, tool, network or secret approvals during a run.
allow: Confirm launch and close.
deny: Reject findings.
safer_modes: Reviewer isolation arguments; execution agents have none.
Delivery [supported] Cards cannot move to done without a sealed review plan and closed batch; closing a GitHub issue needs explicit confirmation. Sources: kander:review, kander:issue-result.
Approver identity [unsupported] Single local user. Sources: kander:srch-team.
Lifetime [unsupported] No scoped lifetimes. Sources: kander:srch-team.
Card documents, review dispositions with commit evidence, dispatch records and checkpoints persist as files; no user attribution or export; records can be edited.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
actions: Dispatch and review records.
approvals: Review dispositions record outcomes.
edits: Card transactions record updates.
decisions: Dispositions with evidence.
mutability: Plain files with journaled controlled writers; direct edits are possible.
Structured review runs by independent reviewers with findings, author disposition and batch close; board detail view with Vim-style navigation; no diff viewer or inline comments.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
change_understanding: Reviewer reports; no diff view.
evidence_navigation: Card detail views and attachments.
comments: Findings assigned to cards.
shipping_guidance: Check delivery and wrap-up dispatch.
Card specs, attachments, review reports and findings, checkpoints and delivery evidence persist per card; no screenshots, recordings, previews or gallery.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Mandatory independent two-stage review (PMQA, Security) with sealed plans, check delivery and overlap analyzers, and completion gate; tests and lint are rules for agents and evidence in dispositions.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
tests: Rules require tests and dispositions record test evidence.
Independent review [supported] Reviewer physically isolated from the executor; 89% of reviews use a different model per maintainer stats. Sources: kander:review, kander:review-iso, kander:stats.
Worktrees, task and group branches, wrap-up integration, delivery checks and issue result comments; rules cover commits, rebases and PR flows through agents; direct PR creation is not a product command.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
pull_requests: No product command or rule opens pull requests; Git rules default to local merge-back and only honor a user requirement to use a PR.
9 atomic answers
Branches [supported] Task and group branches. Sources: kander:group-rules.
Worktrees [supported] Worktree per task. Sources: kander:readme.
Pull requests [unsupported] A bounded search of code, rules and docs finds no rule or command that opens or manages pull requests; the Git rules default to local merge-back and only defer to an explicit user requirement to use a PR. Sources: kander:rv-search-pr.
Rebase [partial] Task branch sync and integration conflicts are handled by dispatch-back; group branch is not rebased once the review plan exists. Sources: kander:group-rules.
Cards link to branch, RESULT and review evidence; delivery check verifies commits on the base; issue result comments link back; no deployment or rollback features.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
pr_links: Issue result comments may reference delivery.
stale_approval_invalidation: Advance target moves the batch commit forward and plans are sealed.
Everything stays local except agent traffic to their providers; no telemetry; the update check calls the GitHub releases API; gh credentials are reused and never stored.
Scope
Surfaces: Kander terminal kanban board (kander; macOS, Linux, Windows), kander command set (new, start, move, review, dispatch, coordinator, subscribe, issue, check, doctor) · Version: v1.4.3 (commit fda60fb, released 2026-11-17) · Plan: Open source (MIT), free, local-only · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
retention: Files stay until deleted.
deletion: Archive, trash and delete card files.
training: Providers' policy.
residency: Depends on providers.
telemetry_disclosure: No telemetry is claimed; absence is established by source search only.
15 atomic answers
Code data [supported] Local; agents send code to providers. Sources: kander:readme.
Prompts [supported] Local files and the chosen agents. Sources: kander:readme.
Credentials [supported] Kander never asks for, reads or stores a token. Sources: kander:readme.
Telemetry disclosure [partial] No telemetry is claimed; absence is established by source search only. Sources: kander:srch-tele.
Telemetry defaults [supported] No telemetry code; GitHub release lookup at TUI start. Sources: kander:srch-tele, kander:update.
Telemetry controls [unsupported] No telemetry to control; the update check cannot be disabled in the pages inspected. Sources: kander:srch-tele, kander:install.
Consent prompt [unsupported] No telemetry consent prompt exists. Sources: kander:srch-tele.
Provider separation [supported] Orchestration data is local. Sources: kander:readme.
Trial [supported] No trial needed. Sources: kander:readme.
Credits trial [supported] No credits. Sources: kander:readme.
Self host cost [supported] User hardware. Sources: kander:readme.
Paid only [supported] No paid-only features. Sources: kander:readme.
Early access [supported] None. Sources: kander:readme.
Free scenarios [partial] BYO subscriptions, review and issues work free; no mobile, collaboration or remote compute. Sources: kander:readme, kander:srch-clients.
Rule-driven multi-agent kanban with two-stage independent review gates, conflict-aware scheduling, git worktree plus tmux/herdr isolation and zero-token GitHub integration via gh; Homebrew, Linux tarball and Windows zip; needs Git and one of Codex, Claude, Grok, Cursor or Pi; MIT.
Binary installs itself (kander install), TUI start checks the latest GitHub release with a five-second deadline and offers an update, rules are written to ~/.agents/kander or a project .kander/rules, install_rules switch gates writes to agent files.
Backends dsh, herdr, herdr-core, luvus, tmux, tmux-session and foreground/console; POSIX-only except foreground/console and herdr; backend features degrade by capability.
Only a terminal binary and a kander-dsh integration exist; no web server, desktop GUI, mobile app or editor extension (the author's separate QuickTUI product is a different closed app).
Kind
source-inspected
Locator
ls cmd internal integrations; grep -rniE "http.ListenAndServe|websocket|electron|android|vscode" internal cmd
Nine built-in agents (codex, claude, grok, cursor, pi, devin, opencode, kimi, droid) defined by embedded JSON; user-defined agents via config.json argv templates; project .kander-config.json overlay.
kander issue import NUMBER creates an idempotent backlog card from a GitHub issue in one exclusive board transaction, storing raw remote text as attachments; uses gh credentials.
Groups list members and a dependency graph; parallel only for cards ready together whose modified files are isolated at file level; hotspot files go to exactly one card.
Kind
documented
Locator
Dependency graph; Running task cards in parallel (L31, L43-L48)
Every active card needs a sealed review plan with roles (PMQA, Security) before done; independent reviewer runs, findings assigned to cards, author disposition with commit SHAs and test evidence, batch close unblocks move done.
Kind
documented
Locator
Workflow pipeline (L1-L40); execution cycles and plans
kander coordinator claim/reconcile/recover stores versioned group checkpoints under kanban/.kander/groups for recovery; it does not run the loop, notify, move cards or delete worktrees.
Reviewers are the nine built-in agents or configured agents with a review template; isolation arguments per agent; kander review is the single gate entry.
Only command environment handling in terminal definitions, probes and Git checks; no dependency installation, cache, service, port or secret management for worktrees.
At every heartbeat the orchestrator inspects working cards and judges a card blocked when its pane shows a dialog, question, repeated error or an agent CLI error (rate limit, context exhaustion, crashed tool), or liveness is stopped or drifted, and reports a card undeterminable for three heartbeats to the user; this is an agent-followed rule, not a built-in retry.
Only issue-listing code filtering pull requests out, the Git rules sentence that explicit user or project requirements to use a PR still apply, and merge-back wording; no rule or code opens, reads or merges pull requests or reads CI checks. The Git rules default to local merge-back to the mainline.