50 of 51 criteria have a sourced finding; 50 were also cross-checked by a second agent. Every comparison that includes kandev 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.
Browser is the primary client (served at localhost:38429, also reachable from phones over VPN/tunnel); Tauri desktop ships macOS arm64/x64, Linux x64/arm64 and Windows x64 installers; kandev launcher CLI runs and manages the backend; no native mobile app or editor extension exists in this release.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No installable native mobile app; phones use the browser UI over a private network path.
No editor extension; code editing happens in the embedded editor/panels.
Unsigned macOS/Windows desktop builds need manual OS security bypasses in this release.
9 atomic answers
Desktop os [supported] Tauri desktop installers ship for macOS arm64/x64, Linux x64/arm64 and Windows x64; Windows ARM64 has no native artifact. Sources: kandev:desktop, kandev:windows.
Mobile apps [unsupported] No native iOS/Android app in the release artifact list (macOS/Linux/Windows desktop only) and none documented; phones use the browser UI. Sources: kandev:desktop, kandev:mobile.
Browser [supported] The web app is the primary client, served by the backend on localhost:38429 by default. Sources: kandev:cli, kandev:readme.
Mobile browser [supported] Phone browsers reach the same origin over Tailscale/Cloudflare/private VPN with phone task controls and narrow-screen layouts. Sources: kandev:mobile.
Cli [supported] The kandev launcher CLI (run/start, ports, service management) plus agentctl runtime helpers ship in every runtime bundle. Sources: kandev:cli.
Editor extensions [unsupported] Bounded search of docs and the pinned release (terms: extension, vsix, open-vsx, marketplace extension) finds only the embedded editor/VS Code panel, no installable editor extension. Sources: kandev:sessions, kandev:features.
Task actions [supported] Start, steer, approve, review and resume from browser and phone task controls; desktop adds native notifications without deep-link navigation. Sources: kandev:tasks, kandev:sessions, kandev:mobile, kandev:desktop.
Notifications [supported] Desktop native plus browser notifications for turn-finished/needs-answer/failures; web-push and webhook providers are configurable; clicking a desktop notification is not a navigation path. Sources: kandev:desktop, kandev:config, kandev:webhook.
Cross device continuity [supported] State lives in the backend database, so any device reaching the origin continues the same tasks; services persist across logout and sessions resume after restarts. Sources: kandev:service, kandev:resume, kandev:mobile.
About 25 named ACP/CLI harnesses (Claude Code, Codex incl. experimental app-server, Copilot, Gemini, OpenCode, Pi, Cursor, Grok, Antigravity and more) launched with native logins; any CLI can also run via PTY passthrough; per-step profiles allow mixing harnesses in one workflow.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Model/provider choice is inherited from each CLI rather than contracted directly by Kandev.
5 atomic answers
Harnesses [supported] Registry lists Auggie, Claude, Codex, Copilot, Gemini, OpenCode, Amp, Qwen, iFlow, Droid, Kilocode, Pi, Cursor, Kimi, Kiro, Qoder, Trae, omp, Devin, Grok, Hermes, Goose, Muse, Antigravity, MiniMax, each usable with a host-supported executable. Sources: kandev:agents.
Model providers [partial] Models come from the installed CLIs (composer model picker shows the session CLI); Kandev documents no direct model-provider contracts of its own. Sources: kandev:agents.
Custom adapters [supported] ACP adapters plus bring-your-own TUI passthrough for any CLI and installable plugin remote executors. Sources: kandev:agents, kandev:executors.
Session integration [supported] Kandev launches and controls sessions through ACP/the CLI and its agentctl runtime (native resume or history injection), reusing native CLI logins. Sources: kandev:agents, kandev:arch, kandev:resume.
Mixed harness operation [supported] Agentic workflows mix-and-match agents per step (e.g. plan with one CLI, implement with another, review with a third). Sources: kandev:readme, kandev:features.
Bring your own agent subscription via native CLI login; API keys via executor secrets/env (e.g. OPENAI_API_KEY) and PATs for external clients; no Kandev vendor credits, billing or local-model route; multiple profiles hold distinct credentials.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No Kandev-side billing, credits or subscription metering exist.
No first-party local-model support was found.
7 atomic answers
Agent subscriptions [supported] Existing coding-agent subscriptions work through native CLI logins; Kandev sells no tokens and creates no provider accounts. Sources: kandev:usek, kandev:readme.
Api accounts [supported] Provider API keys reach agents via executor secrets/environment (e.g. OPENAI_API_KEY); external MCP/API clients authenticate with personal access tokens. Sources: kandev:executors, kandev:auth.
Vendor credits [unsupported] No vendor billing, credits or token sale exist in this self-hosted release; bounded search of site, docs and release notes finds no paid surface. Sources: kandev:site, kandev:readme.
Local models [unsupported] Bounded search of the agent registry docs and pinned release (terms: ollama, llama, local model, lm studio) finds no local-model route; models arrive via installed CLIs. Sources: kandev:agents.
Account switching [partial] Separate agent profiles can carry distinct credentials and be chosen per session/step; per-CLI multi-account handling is inherited from the CLI. Sources: kandev:agents.
Vendor account requirement [supported] No Kandev account is required; provider accounts/keys for the chosen CLIs are required. Sources: kandev:usek, kandev:site.
Provider restrictions [partial] Sprites execution accepts provider lifecycle/billing; agent availability follows the host platform and installed CLIs. Sources: kandev:executors, kandev:agents.
Install via Homebrew/Scoop/npm, add a local repo, configure an agent profile and start a first task; local and GitHub-backed repos supported; repository-free tasks exist; SSH plus service guides cover own-server onboarding; no managed-cloud path exists.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No vendor-managed cloud onboarding exists by design (self-hosted product).
7 atomic answers
First task setup [supported] Get-started path: install, add a local repository, configure an agent profile keeping Worktree selected, start and review the first task. Sources: kandev:usek.
No git [supported] Repository-free tasks exist (repository-less configuration chat; hidden automation runs with no repository). Sources: kandev:automation, kandev:fstatus.
Local git without remote [supported] Repository settings accept existing local Git paths and local executors operate on those checkouts; only push/change-request creation uses origin. Sources: kandev:usek, kandev:gitops.
Prerequisite guidance [supported] Prerequisites are listed (Git, agent-CLI credentials, npm 7+ for the npm channel only, Docker only for Docker profiles) with trust-boundary guidance. Sources: kandev:usek.
Managed cloud setup [unsupported] No vendor cloud or managed compute offering exists; the product runs on user infrastructure and bounded search of site/docs/releases finds no cloud onboarding. Sources: kandev:site, kandev:readme.
Byo vps onboarding [supported] Own-server path via SSH executors, systemd/launchd service installs (incl. Linux VPS system mode) and private phone access over Tailscale/Cloudflare/VPN. Sources: kandev:executors, kandev:service, kandev:mobile.
Complete WebSocket action API plus REST /api/v1, versioned Go/npm plugin SDK, external MCP (streamable HTTP + SSE) for create/manage from outside agents, incoming authenticated webhooks and outgoing notification webhooks; launcher CLI covers run/service management.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
External MCP intentionally omits stop_task plus live session question/plan/spawn/message tools.
The kandev CLI is a launcher/service manager, not a task-operation CLI.
8 atomic answers
Cli [partial] kandev run/start/service plus agentctl runtime helpers ship in bundles; task create/inspect/steer/stop/review go through the WebSocket/REST/MCP surfaces, not a task CLI. Sources: kandev:cli, kandev:wsapi.
Api [supported] REST /api/v1 routes plus the documented single-/ws JSON action protocol (request/response/notification/error envelope, named error codes) covering boards, tasks, sessions and runs. Sources: kandev:wsapi, kandev:auth.
Sdk [supported] Go/npm plugin SDK (module github.com/kdlbs/kandev/pluginsdk, Serve entrypoint, manifest checker), versioned independently with a published 0.2.1 tag. Sources: kandev:sdk.
Mcp server [supported] External MCP endpoint at /mcp (modern negotiation plus legacy initialize) with SSE compatibility at /mcp/sse and /mcp/message; copyable snippets for popular CLIs. Sources: kandev:automation, kandev:fstatus.
Webhooks [supported] Incoming authenticated webhooks trigger automations; outgoing notification webhooks are a configured provider (10s timeout, SSRF guards) alongside web push. Sources: kandev:automation, kandev:config, kandev:webhook.
Operations [supported] Create, inspect, steer, stop and review operations exist across WS/REST/MCP; exact-run stop, title snapshots and durable cleanup retry are documented. Sources: kandev:wsapi, kandev:automation.
Authentication [supported] Bearer personal access tokens for programmatic clients; same-origin browser sessions when auth is on; synthetic administrator identity when auth is off. Sources: kandev:auth.
Stability [partial] API paths are versioned (/api/v1) but no published stability or deprecation policy was found in the bounded doc search. Sources: kandev:wsapi, kandev:auth.
Instructions import [partial] Saved and custom prompts, move-time instruction blocks and workflow prompts are product-managed; agent skills live in experimental Office. Sources: kandev:features, kandev:office.
Authentication [partial] Integration credentials use the encrypted secret store and narrowest-scope guidance; per-definition MCP authentication detail is not fully established by this pass. Sources: kandev:integrations, kandev:config.
Desktop is a Tauri shell (Rust launcher, system WebView) over the backend-served SPA; mobile clients are the responsive web app plus a shipped PWA manifest; no native mobile or Electron client exists.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No store listing or documented install flow for the PWA manifest.
Unsigned macOS/Windows desktop builds need manual OS bypasses in this release.
4 atomic answers
Desktop implementation [supported] Tauri: Rust starts the bundled headless backend on an owned loopback origin inside a system WebView (tauri.conf.json productName Kandev, identifier dev.kandev.desktop). Sources: kandev:pubarch, kandev:tauri.
Mobile implementation [supported] Web/PWA: responsive phone UI served by the backend plus a shipped web manifest (standalone display); no native phone codebase. Sources: kandev:mobile, kandev:pwa.
Hybrids [supported] Tauri native shell hosting the backend-served SPA; backend remains one Go process across channels. Sources: kandev:pubarch, kandev:arch.
Implementation evidence [supported] Source-inspected tauri.conf.json and PWA manifest plus official architecture and desktop-app docs at the pinned commit. Sources: kandev:tauri, kandev:pwa, kandev:pubarch.
Native task creation plus prompt intake (Quick/Config chat), provider issue/MR import and watches from GitHub, GitLab, Jira, Linear, Sentry and Azure; Kandev tasks own workflow state while provider links are retained; PR-open/PR-merged triggers shipped, push/CI triggers in progress.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Jira launch copies data without a durable association.
GitHub push/CI triggers are coming-soon stubs, not working triggers.
9 atomic answers
Local creation [supported] New Task flow with searchable workflow, profile, repository and branch controls. Sources: kandev:tasks, kandev:automation.
Prompt intake [supported] Prompt-driven intake via Quick Chat, configuration chat and per-task composers with file attachments. Sources: kandev:sessions, kandev:automation.
External import [supported] Issues/work items/MRs from GitHub, GitLab, Jira, Linear, Sentry and Azure can be browsed and launched as tasks; watches create tasks from provider events. Sources: kandev:integrations, kandev:automation.
Chat git triggers [partial] GitHub PR-open and PR-merged automations are shipped; push and CI triggers are documented as in-progress stubs. Sources: kandev:fstatus, kandev:automation.
Authoritative tracker [partial] The Kandev task owns workflow position while provider objects stay linked; Jira copies data rather than keeping a durable two-way association. Sources: kandev:tasks, kandev:integrations.
Stable ids [partial] Durable Kandev task IDs plus retained provider links (PR/MR numbers, URLs, states surfaced on related-task responses). Sources: kandev:tasks, kandev:integrations.
Sync [partial] Watch polling (with documented caps) and PR/MR lifecycle messages keep states aligned; Azure/Jira/Linear sync is constrained and one-directional in places. Sources: kandev:integrations, kandev:automation.
Supported edits [partial] Provider-scoped edits: GitHub checks/reviews/comments, GitLab approvals/discussions, Jira transitions, Linear state changes; Azure arbitrary editing not supported. Sources: kandev:integrations, kandev:sessions.
External roundtrips [partial] Submodule PRs stay separate provider workflows and some operations need provider permissions or UI; the task PR panel covers the GitHub path fully. Sources: kandev:sessions, kandev:integrations.
One structured Markdown plan per regular task with Plan panel, version history, compare/revert, plan-mode Implement flow, human and agent (task-MCP) editing, and persistence across restarts; amendment while running is supported via moves and wait steps.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No explicit acceptance-criteria field; plan comments on steps carry the reviewable detail.
Passthrough-only sessions lack the plan contract.
7 atomic answers
Plans [supported] Each task keeps one editable Markdown plan with a dedicated Plan panel and plan mode. Sources: kandev:tasks, kandev:fstatus.
Acceptance criteria [partial] Completion policies, explicit completion gating and plan comments on exact steps exist; a named acceptance-criteria construct was not found. Sources: kandev:tasks, kandev:fstatus.
Editors [supported] Humans edit in the panel; agents create/read/update/delete plans through task MCP (passthrough sessions excluded). Sources: kandev:fstatus, kandev:sessions.
Revisions [supported] Plan revision history with compare and revert; consecutive writes can coalesce into one revision. Sources: kandev:tasks, kandev:fstatus.
Implementation links [partial] Plan Implement flow continues into sessions with linked repositories and associated PRs; direct plan-step-to-commit links are not established. Sources: kandev:tasks, kandev:fstatus.
Amendment [supported] Plans and moves can change while work runs (moves queue behind running agents with options preserved); human wait steps gate auto-advance. Sources: kandev:tasks.
Restart persistence [supported] Plans persist in SQLite and survive backend restarts with lazy session recovery. Sources: kandev:resume, kandev:arch.
One-level subtasks with workspace inheritance choice, stored blocker/dependency relations with cycle rejection and a dependency-graph view, WIP-gated moves, and workflow changes that preserve task identity; arbitrary-depth trees and epic promotion are Office-only in-progress work.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No epic entity and no grow-a-task-into-an-epic path.
Blocker/dependency create/edit/filter pickers are Office UI; regular kanban surfaces stored relations without a complete editing path.
Arbitrary-depth trees are in progress.
9 atomic answers
Epics [unsupported] No epic backlog entity exists; bounded search of task/workflow docs and the pinned release (terms: epic, initiative, theme) finds only workflow groupings. Sources: kandev:tasks, kandev:fstatus.
Hierarchy [partial] Regular kanban supports parent plus direct children through UI and MCP; arbitrary-depth trees are Office-only in progress. Sources: kandev:fstatus, kandev:coord.
Blockers [partial] Blocked_by relations are stored, cycle-checked and block automated starts, with related-task inspection; the full create/edit/filter picker is Office UI. Sources: kandev:features, kandev:fstatus.
Readiness [partial] A blocked task is not started by any automated path and fires once predecessors succeed; chained creates build chains. Sources: kandev:features.
Enforcement [partial] Blocked tasks are held from auto-start and moves re-check routing, permissions, WIP and session state; display-level enforcement beyond holds is not established. Sources: kandev:features, kandev:tasks.
State propagation [partial] Direct-child completion feeds workflow events and actions; no roll-up or epic-level propagation exists. Sources: kandev:fstatus, kandev:tasks.
Task to epic [unsupported] No promotion path from task to epic exists; bounded search finds only subtask creation and workflow changes that preserve identity. Sources: kandev:tasks, kandev:coord.
Identity retention [supported] Changing a workflow keeps task identity, description, repositories and existing conversations, with optional per-task profile mapping. Sources: kandev:tasks.
Workflow constraints [partial] WIP/pull controls, fixed per-step profiles and guard-checked transitions constrain flow; scoped exceptions are possible via move-with-options and profile mapping. Sources: kandev:tasks, kandev:fstatus.
Workflow/custom prompts, per-task documents with revisions, retained session conversations with resume-time history injection, utility-agent summaries for handoff, and takeover that preserves context; no product-managed cross-session memory outside experimental Office.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Managed cross-session/cross-harness memory is Office-only in progress.
Generated summaries can omit constraints or decisions.
Skills [partial] Utility agents and custom one-shot helpers are shipped; named agent skills are experimental Office surface. Sources: kandev:features, kandev:office.
Project docs [partial] Per-task documents with revision history (plans, specs, notes, reviews); no workspace-level persistent product-spec store outside Office documents in progress. Sources: kandev:features, kandev:fstatus.
Memory [partial] Session history persists and is re-injected on resume or summarized for handoffs; no managed long-term memory beyond experimental Office. Sources: kandev:resume, kandev:sessions, kandev:fstatus.
Scope [partial] Workspace/task/session scoping for prompts, MCP packages and secrets is documented; cross-workspace memory scoping is not established. Sources: kandev:mcpbuiltin, kandev:config.
Provenance [partial] Message attribution, human-action attribution and utility-agent summary labeling exist; full source provenance for injected context is not established. Sources: kandev:team, kandev:sessions.
Correction [partial] Plan compare/revert, thread comments on extracts and editable prompts allow correction; managed stale-context controls are not established. Sources: kandev:sessions, kandev:tasks.
Freshness [partial] Watch polling and provider re-checks refresh linked state with documented caps; no staleness model for injected memory. Sources: kandev:integrations, kandev:resume.
Takeover continuity [supported] Colleague takeover (reassign plus continue) and agent handoff preserve task, session history, decisions and artifacts. Sources: kandev:team, kandev:sessions.
Agents work with full repo checkouts and provider-linked context (issues, PRs, Sentry) while Kandev itself provides diff/review surfacing, divergence detection and human gates; no product-owned code index, semantic retrieval, citation model or spec-conformance enforcement exists.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No product-owned semantic index or embeddings service; retrieval is agent-CLI capability plus file panels.
No spec-conformance enforcement at review time.
10 atomic answers
Code search [partial] File editor/tree/terminal search plus agent-CLI search over full checkouts; no product search index. Sources: kandev:sessions, kandev:executors.
Indexing [unsupported] Bounded search of backend services and docs (terms: embedding, vector, semantic index, repository index) finds no product-owned indexing service. Sources: kandev:arch, kandev:fstatus.
External knowledge [partial] Provider objects (issues, PRs, Sentry events) and web links are brought into task context; general web knowledge is agent-side. Sources: kandev:integrations, kandev:sessions.
Multimodal inputs [supported] Image/file attachments on answers and prompts (bounded counts and sizes) delivered to agent execution as readable paths. Sources: kandev:sessions.
Freshness [partial] Watch polls and provider re-resolution refresh linked state; comparison bases are re-checked before mutating actions. Sources: kandev:integrations, kandev:gitops.
Access scope [supported] Per-task repository attachments with base/checkout branches bound what agents and reviewers see. Sources: kandev:tasks, kandev:executors.
Api retrieval [partial] Backend reads provider APIs for issues/PRs/checks within workspace scope; agent-side retrieval is CLI capability. Sources: kandev:integrations.
Citations [partial] Canonical PR URLs in lifecycle templates and anchored plan/thread comments; no formal citation model. Sources: kandev:sessions, kandev:gitops.
Conflict detection [partial] Divergent task-vs-PR history detection with neutral wording and compare flows; no semantic conflict detection. Sources: kandev:gitops.
Review enforcement [partial] Human gates plus provider required-check enforcement on merge; agent assertions alone never satisfy a gate. Sources: kandev:sessions, kandev:gitops.
Full native task lifecycle on kanban/pipeline boards (create, edit, discuss, assign, search, archive, reopen, workflow views, dispatch control, task/session separation, durable states) without any external tracker; labels and full dependency editing are Office-surface in progress.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Label catalogs, pickers and filters live on the flagged Office surface, not regular kanban.
Create [supported] New Task flow with workflow, profile, repository and branch selection. Sources: kandev:tasks.
Edit [supported] Title, prompt, workflow moves, profile mapping and repository attachments are editable. Sources: kandev:tasks.
Discuss [supported] Task conversations, plan/thread comments on exact extracts and message threads. Sources: kandev:sessions, kandev:releases.
Prioritize [partial] Workflow ordering, WIP rules and Needs-you/Queue surfacing prioritize; no dedicated priority field is established. Sources: kandev:tasks, kandev:coordinator.
Label [partial] Label storage exists but catalogs, pickers and filters are Office-surface in progress per Feature Status. Sources: kandev:features, kandev:fstatus.
Assign [supported] Independent human assignee and agent assignee rows with Assign-to-me. Sources: kandev:team.
Search [supported] Task search plus board filters. Sources: kandev:tasks.
Filter [partial] Board and view filters exist; label-based filtering is Office-surface. Sources: kandev:tasks, kandev:fstatus.
Archive [supported] Archive/unarchive with async runtime cleanup and phone confirmation sheets. Sources: kandev:tasks, kandev:mobile.
Reopen [supported] Unarchive restores tasks; deleted-task recovery is not claimed. Sources: kandev:tasks.
Project epic views [supported] Kanban and pipeline views per workflow with columns, counts and PR badges. Sources: kandev:tasks, kandev:sessions.
Idea parking [supported] Backlog steps and destinations without auto-start let ideas wait without dispatching agents. Sources: kandev:tasks, kandev:fstatus.
Explicit dispatch [supported] Manual start, auto-start preferences and explicit step-move dispatch with previews. Sources: kandev:tasks.
Task session separation [supported] Tasks own workflow state while multiple named sessions attach to one task environment. Sources: kandev:sessions, kandev:tasks.
Metadata [partial] Assignees, repositories, workflow position and states are first-class; label/dependency metadata editing is Office-surface. Sources: kandev:team, kandev:fstatus.
Durable states [supported] Workflow steps, archive state and Done completion persist in the database. Sources: kandev:tasks, kandev:arch.
External tracker requirement [supported] No external tracker is required; integrations are optional attachments. Sources: kandev:tasks, kandev:integrations.
Agents read, create, update, move, link and report on the same durable task IDs humans use through documented task-MCP tools, with attribution, workspace policy and cycle/permission guards; direct stop and cross-task message tools are scoped accordingly.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
External MCP omits stop and live session question/plan/spawn/message tools.
Claim semantics are assignment-based; no exclusive agent lock exists.
14 atomic answers
Shared ids [supported] Agents operate on the same durable task/session IDs and fields humans see. Sources: kandev:features.
Read [supported] List/inspect workspaces, workflows, tasks, related tasks, conversations and plans. Sources: kandev:features.
Create [supported] Create top-level tasks and subtasks with optional auto-start, inheritance choice and dependency declarations. Sources: kandev:features, kandev:automation.
Update [supported] Move steps, attach branches, adjust diff bases, archive/delete with handoff prompts and completion signals. Sources: kandev:features.
Claim [partial] Agent assignment rows record ownership; claiming is assignment, not an exclusive lock (takeover reassigns without locking). Sources: kandev:team, kandev:coord.
Assign [supported] Agent assignee rows plus human Assigned-to rows are settable independently. Sources: kandev:team.
State changes [supported] Move tasks across steps and emit explicit step-completion signals gating auto-advance. Sources: kandev:tasks, kandev:features.
Dependencies [supported] Declare blocked_by at creation or add/remove relations later; cycles rejected; blocked tasks held from automated starts. Sources: kandev:features.
Children [supported] Subtask creation with inherited or new workspaces; direct-child completion feeds workflow events. Sources: kandev:features, kandev:coord.
Results [supported] Completion signals with summary/handoff/blockers, session-shared walkthroughs and PR associations. Sources: kandev:features, kandev:sessions.
Human visibility [supported] Boards, sessions, review panels and lifecycle messages reflect agent writes to humans. Sources: kandev:sessions, kandev:tasks.
Attribution [supported] Agent-spawned sessions carry sender/route attribution; human actions record the acting person. Sources: kandev:coord, kandev:team.
Per-task plans and documents with revisions exist, but no persistent cross-task product-specification system with attributable upkeep, implementation links, retrieval, drift detection or review integration was found in the pinned release.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Per-task plans/documents are covered under PLAN-02; they do not constitute a living cross-task spec.
9 atomic answers
Persistent requirements [unsupported] Bounded search of docs and backend (terms: living spec, product spec, persistent requirements, drift) finds only per-task plans and experimental Office documents. Sources: kandev:fstatus, kandev:office.
Human edits [unsupported] No cross-task spec editing surface exists outside per-task documents and Office documents in progress. Sources: kandev:fstatus, kandev:features.
Agent edits [unsupported] Agent plan tools are task-scoped; no agent-editable cross-task spec exists. Sources: kandev:features, kandev:fstatus.
Revisions [unsupported] Revision history exists for per-task plans/documents only, not for a cross-task specification. Sources: kandev:features, kandev:tasks.
Approvals [unsupported] Approval flows are task/PR-scoped (review/approval stages); no spec approval rules exist. Sources: kandev:office, kandev:sessions.
Implementation links [unsupported] No requirement-to-task/implementation link model was found. Sources: kandev:fstatus.
Later retrieval [unsupported] No retrieval of persistent specs into later tasks is documented or implemented. Sources: kandev:fstatus.
Drift detection [unsupported] No drift detection between specs and implementation exists. Sources: kandev:fstatus.
Review integration [unsupported] Review gates reference tasks and PRs, never a persistent specification. Sources: kandev:sessions, kandev:office.
Independently running named sessions share a task environment while multiple tasks run in parallel; automation concurrency caps and one-active-run semantics bound load; boards, stats and Inbox expose running, waiting, failed and finished work.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No documented global session/task quota beyond automation concurrency and single-run semantics.
5 atomic answers
Concurrent sessions [supported] Multiple named sessions attach to one task environment and run concurrently. Sources: kandev:sessions, kandev:coord.
Concurrent tasks [supported] Multiple tasks across workflows run and are reviewed in parallel. Sources: kandev:readme, kandev:tasks.
Quotas [partial] Automation concurrency limits and one-active-run reusable mode exist; no general session quota is documented. Sources: kandev:automation.
Observed concurrency [supported] Parallel named sessions, parallel tasks and multi-repo fan-out are documented product behavior, not mere tabs. Sources: kandev:coord, kandev:features.
Status visibility [supported] Boards with step counts, session states, stats workload pages and question Inbox expose running/waiting/failed/finished work. Sources: kandev:tasks, kandev:stats, kandev:sessions.
Human and agent assignees, automation queues with concurrency limits, compatibility routing for profiles/executors, and cycle guards; ownership is assignment-based with takeover-by-reassign and no exclusive lock or duplicate prevention beyond documented checks.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No exclusive ownership lock; a colleague can take over without the holder releasing.
No general duplicate-work prevention beyond cycle checks and unsafe-reuse refusal.
7 atomic answers
Human assignment [supported] Human assignee rows with Assign-to-me and unit-based reachability. Sources: kandev:team.
Agent assignment [supported] Agent assignee rows per task plus per-step agent profiles and handoff profile choice. Sources: kandev:team, kandev:sessions.
Claims [partial] Assignment records ownership; claiming is not an exclusive lock. Sources: kandev:team.
Queues [partial] Automation runs queue with one-active-run semantics; the workspace coordinator Queue is in-progress behind a flag. Sources: kandev:automation, kandev:fstatus.
Routing [partial] Profile pickers filter to executor-compatible profiles and moves re-check routing/permissions/WIP/session state. Sources: kandev:sessions, kandev:tasks.
Duplicate prevention [partial] Cycle rejection and workspace_reuse_unsupported refusal; concurrent same-file edits are allowed to collide. Sources: kandev:features, kandev:coord.
Ownership enforcement [partial] Display plus reassignment; advisory/enforced exclusivity is not established. Sources: kandev:team.
Product task-MCP (spawn/message/stop scoped tools) lets sessions delegate to other sessions with attribution; coordinator-led teams are shipped for kanban delegation while persistent cross-harness Office teams remain experimental.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Cross-harness persistent teams, quorum/participant mechanics and Office routines are experimental/in-progress.
Model harness effort [supported] Per-profile model/flags/permissions and per-step agent selection, including mixed-harness steps. Sources: kandev:agents, kandev:features.
Messages [supported] Targeted task messages queue to running sessions or start idle ones with sender attribution. Sources: kandev:coord, kandev:features.
Results return [supported] Completion signals, summaries, walkthroughs and shared plans return results to parents/humans. Sources: kandev:features, kandev:sessions.
Cross harness [partial] Per-step mixed providers are shipped; persistent cross-harness Office teams are in progress. Sources: kandev:features, kandev:office.
Orchestration owner [supported] Delegation tools are product-owned task MCP; coordinator-led subtask execution is a shipped Done roadmap item. Sources: kandev:coord, kandev:roadmap.
Activation [supported] UI New Agent/handoff plus spawn_session/message tools from inside agents. Sources: kandev:sessions, kandev:coord.
Authentication [partial] Workspace policy, package scoping and permission checks gate tools; per-tool auth detail beyond policy is not fully established. Sources: kandev:mcpbuiltin, kandev:security.
Live progress [supported] Chat, tool activity, session states and background-work views expose live progress. Sources: kandev:sessions.
Retained results [supported] Conversations, plans, walkthroughs and review history persist after completion. Sources: kandev:sessions, kandev:tasks.
Followup [supported] Message threads, handoff, reopen and resume continue work after completion. Sources: kandev:sessions, kandev:coord.
Invocation [supported] Delegation invokes through documented UI and MCP paths, never hidden shell assembly. Sources: kandev:coord, kandev:automation.
Schedule (@every/cron presets), authenticated webhook and GitHub PR triggers create hidden or normal-task runs from the backend with concurrency limits and retry policy; fixed-cron timezones are not honored and push/CI triggers are stubs.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Fixed cron timezone values are not honored; prefer presets or @every.
GitHub push/CI triggers are coming-soon stubs.
Retry model is policy-based, not a general scheduler guarantee.
8 atomic answers
Schedules [supported] Manual, @every and cron-preset schedules with per-trigger enablement and timezone field (with the noted limitation). Sources: kandev:automation.
Events [partial] Authenticated webhooks and GitHub PR-open/PR-merged events fire runs; push/CI events are in-progress stubs. Sources: kandev:automation, kandev:fstatus.
Recurring tasks [supported] Recurring automation runs and experimental Office routines repeat work on schedule. Sources: kandev:automation, kandev:office.
Completion conditions [partial] Explicit completion gating and one-active-run semantics exist; no rich condition language is established. Sources: kandev:fstatus, kandev:tasks.
Scheduler location [supported] Triggers dispatch from backend automation runs, independent of any open client. Sources: kandev:automation, kandev:arch.
Overlaps [partial] Concurrency limit plus one-active-run reusable mode serialize overlap; general overlap policy beyond that is not established. Sources: kandev:automation.
Client independence [supported] Backend-owned dispatch keeps firing with the client closed; services keep it resident across reboots. Sources: kandev:automation, kandev:service.
Stop/resume/steer (with queued messages), clarification and permission questions with attachments, Inbox history, failure alerts and desktop notifications, plus retained SQLite history; generic pause and escalation chains are not established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No generic pause for regular sessions or escalation chain; coordinator pause/holds are experimental.
Passthrough sessions lack structured parity (no MCP, plans or resumable state).
10 atomic answers
Pause [partial] Stop plus human wait-step gating achieve pause-like control; a dedicated regular-session pause is not established. Sources: kandev:tasks, kandev:sessions.
Stop [supported] Stop sessions and exact-run automation stops with async runtime teardown. Sources: kandev:sessions, kandev:automation.
Resume [supported] Resume sessions including lazy recovery after backend restart (native resume or history injection). Sources: kandev:resume, kandev:sessions.
Steer [supported] Message running sessions (queued for next turn) or idle ones immediately; move-with-options redirects work. Sources: kandev:coord, kandev:tasks.
Notifications [supported] Turn-finished/needs-answer/failure alerts via desktop, browser, web-push and webhook channels. Sources: kandev:desktop, kandev:config.
Escalation [unsupported] No escalation chain (manager routing beyond experimental coordinator holds) was found in bounded doc/code search. Sources: kandev:coordinator, kandev:fstatus.
Visible errors [supported] Error states, failed sessions, lifecycle messages and background-work history surface visibly. Sources: kandev:sessions, kandev:fstatus.
Retained history [supported] Conversations, plans and review history persist in SQLite across restarts and client changes. Sources: kandev:arch, kandev:resume.
Multi-workflow kanban/pipeline boards with step counts, PR badges, dependency-graph view, Inbox attention, stats workload and guarded move-error handling; blocked/failed/awaiting states are visible per task while cross-epic roll-ups stay experimental.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No required-review batch queue or cross-epic roll-up outside experimental coordinator/Office.
Dependency editing pickers are Office UI.
8 atomic answers
Fleet fixture [supported] Boards span several workflows with columns, counts and workload stats pages. Sources: kandev:tasks, kandev:stats.
Parent child [supported] Subtask links with detachment UI and per-task grouping. Sources: kandev:coord, kandev:tasks.
Dependencies [partial] Dependency-graph view and stored relations; full editing picker is Office UI. Sources: kandev:tasks, kandev:fstatus.
Attention [partial] Question Inbox, PR badges and status strips flag attention; Needs-you/Queue roll-up is in progress. Sources: kandev:sessions, kandev:fstatus.
History [partial] Per-task conversation/plan/review history; workspace-level activity history is Office surface. Sources: kandev:sessions, kandev:office.
Workload [supported] Stats workload views by task, agent, project and time. Sources: kandev:stats.
Navigation errors [supported] Failed cross-step moves surface errors and the card keeps its previous step. Sources: kandev:tasks.
Fixture mode [unsupported] No product fixture/demo-data mode was found in bounded search of docs and the pinned release (terms: fixture, demo data, sample data). Sources: kandev:tasks, kandev:usek.
Quick tasks, subtask-grown scope with identity-preserving workflow changes, templates, configuration-chat natural language, per-agent configuration, in-run move options, live session roles and retained relationships are all shipped; discoverability is docs plus command palette and external auth needs PAT setup.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No promotion of a task into an epic; scope growth is subtasks plus workflow changes.
External programmatic auth requires PAT provisioning when auth is on.
10 atomic answers
Quick task [supported] Quick Chat and New Task start single tasks immediately. Sources: kandev:sessions, kandev:tasks.
Growing epic [partial] Subtasks add scope and workflow changes preserve identity; epic promotion does not exist. Sources: kandev:coord, kandev:tasks.
Natural language [supported] Configuration chat creates automations and workflow prompts configure behavior in prose. Sources: kandev:automation, kandev:features.
Agent configuration [supported] Per-profile model, flags, secrets, permissions and per-step agent assignment with mapping. Sources: kandev:agents, kandev:tasks.
In run changes [supported] Move-with-options, handoff, profile mapping and context reset change execution mid-run. Sources: kandev:tasks, kandev:sessions.
Live roles [supported] Session tabs, primary designation, agent logos and assignee rows expose live roles. Sources: kandev:sessions, kandev:team.
Retained relationships [supported] Subtask links, dependency graph and associated PR links persist after completion. Sources: kandev:tasks, kandev:integrations.
Discoverability [partial] Docs, command palette (Cmd/Ctrl+K), settings routes and copyable MCP snippets; no guided setup tour beyond first-run dialog. Sources: kandev:usek, kandev:tasks.
Auth friction [partial] Local use needs no auth; shared/programmatic use needs experimental-auth setup plus PAT provisioning. Sources: kandev:auth, kandev:mobile.
Local host, worktrees, Docker, Kubernetes, SSH and Sprites executors with a self-hostable control plane (binary, service, Docker, k8s example); no vendor cloud exists; backends run as persistent services so any device can reconnect and work survives client disconnects.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No vendor-managed cloud execution; remote compute is user-owned or third-party (Sprites).
Laptop sleep kills locally hosted backends; independence requires the backend on an always-on host.
12 atomic answers
Local [supported] Local and Worktree executors run on the Kandev host. Sources: kandev:executors.
Byo remote [supported] SSH hosts, Remote Docker over SSH and Sprites provider sandboxes run agent work remotely. Sources: kandev:executors.
Self hosted [supported] Self-hosted control plane via native binary, OS service, Docker image or k8s example. Sources: kandev:service, kandev:docker, kandev:k8s.
Managed cloud [unsupported] No vendor-operated cloud execution exists; bounded search of site, docs and releases finds only self-hosting plus third-party executors. Sources: kandev:site, kandev:readme.
Hybrid [partial] Local control plane with remote executors (or remote control plane with local reach-back) mixes modes per task. Sources: kandev:executors, kandev:service.
Provisioning [partial] Prepare scripts, env/credential seeding and per-profile executors; Sprites provisioning is provider-side. Sources: kandev:executors.
Payer [partial] No Kandev charges; provider subscriptions/keys and Sprites billing are user-paid. Sources: kandev:site, kandev:usek.
Region [unsupported] No region selection exists in executor profiles; provider placement is provider-side and undocumented by Kandev. Sources: kandev:executors.
Expiry [partial] Quick Chat 7-day sweep, task directories kept by default with opt-in reclamation; Sprites retention is provider-reported. Sources: kandev:fstatus, kandev:executors.
Client disconnect [supported] Backend persists state and services survive logout/SSH drop; sessions resume or continue. Sources: kandev:service, kandev:resume.
Other device continuation [supported] Any device reaching the origin (including phones over VPN/tunnel) continues the same tasks. Sources: kandev:mobile, kandev:service.
Worktree-per-task file isolation plus Local checkout, container (Docker/Kubernetes) boundaries and SSH-remote hosts with documented trust limits; no VM or OS-sandbox boundary; network/secret/process limits are executor-specific, never a hostile-code sandbox claim.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Worktrees isolate files only, not host account, processes, ports or network.
No VM, OS-sandbox or hostile-code containment is claimed.
12 atomic answers
Checkout [supported] Local executor uses the selected shared checkout. Sources: kandev:executors.
Vm [unsupported] Bounded code/doc search (terms: firecracker, gvisor, kata, microvm) finds no VM boundary; Sprites sandboxes are provider-defined, not a Kandev VM claim. Sources: kandev:executors.
Os sandbox [unsupported] No OS-level sandbox boundary is documented or implemented in the pinned release. Sources: kandev:security, kandev:executors.
Filesystem [partial] Worktree file separation; containers mount only explicit paths; SSH/remote paths are host-scoped. Sources: kandev:executors, kandev:security.
Process [partial] Host processes shared on local/worktree; container and remote boundaries per executor. Sources: kandev:security, kandev:executors.
Network [partial] Tunnels, proxy URLs and explicit container mounts; no product network policy beyond k8s admission templates. Sources: kandev:tasks, kandev:executors.
Secrets [partial] GitHub repo-scoped leases, GitLab workspace tokens and per-user secrets with ambient-token caveats. Sources: kandev:executors, kandev:security.
Code separation [supported] Concurrent agents work in separate worktrees/containers so changes do not collide. Sources: kandev:readme, kandev:executors.
Security boundary [partial] Trust boundaries are explicitly documented per executor with a no-hostile-containment stance. Sources: kandev:security.
SQLite-persisted state with lazy session recovery (native ACP resume or history injection) after restarts, reconnect-safe clients, backup snapshots, and documented caveats on summarization loss and non-idempotent creation; provider sandbox expiry stays provider-owned.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Agents without resume flags boot idle with no context restoration.
Automation creation is not idempotent; duplicate firings are possible.
12 atomic answers
Client disconnect [supported] State persists server-side; reconnecting clients reload transcripts and live status. Sources: kandev:resume, kandev:service.
Worker crash [partial] Agent failure recovery flows and session failure alerts exist; crashed processes are relaunched via resume, not live-migrated. Sources: kandev:sessions, kandev:resume.
Service restart [supported] Backups/snapshots around upgrades plus lazy recovery of sessions after restart. Sources: kandev:features, kandev:resume.
Transcript reload [supported] Persisted messages reload into sessions and history views. Sources: kandev:resume, kandev:sessions.
Process reconnect [partial] Native ACP resume where supported, history injection otherwise; unsupported agents boot idle. Sources: kandev:resume.
Task resume [supported] Tasks resume with workflow position, repositories, plans and conversations intact. Sources: kandev:resume, kandev:tasks.
State reconstruction [partial] NeedsResume flow rebuilds agentctl plus agent; uncommitted files stay in the workspace. Sources: kandev:resume.
Context loss [partial] Summarization may omit constraints/decisions and idle-boot agents lose context; both caveats are documented. Sources: kandev:sessions, kandev:resume.
Duplicate actions [partial] Move options survive queueing and restarts; automation creation is explicitly not idempotent. Sources: kandev:tasks, kandev:automation.
Multi day continuity [partial] Service persistence plus resume support long-running epics; sandbox/lease expiry bounds apply. Sources: kandev:service, kandev:resume.
Prepare scripts, ignored-file seeding, secret injection, port forwarding and per-profile remote setup are shipped with backup snapshots; product-level cache management, install dedup and collision handling are not established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No product cache/dependency management; setup scripts are operator-owned.
No cross-workspace install dedup or port-collision resolution.
10 atomic answers
Dependencies [supported] Prepare scripts, repository copy-file/seed patterns and setup hooks install dependencies per environment. Sources: kandev:executors, kandev:gitops.
Caches [unsupported] No dependency-cache management was found in bounded search of executor/config docs and the pinned release. Sources: kandev:executors, kandev:config.
Snapshots [supported] Manual and pre-upgrade snapshots with download, restore and deletion. Sources: kandev:features.
Services [partial] Port forwarding with tunnels and proxy URLs; no managed auxiliary services (databases, queues) are provided. Sources: kandev:tasks.
Ports [supported] Port manager detects, forwards, opens and stops per-task ports with per-port tunnel URLs. Sources: kandev:tasks.
Secrets [supported] Named secrets, per-user/workspace scoping and executor injection without pasting values into tasks. Sources: kandev:config, kandev:features.
Duplicate installs [unsupported] No deduplication of installs across workspaces is documented or implemented. Sources: kandev:executors.
Collisions [partial] Backend auto-selects free ports for itself; task port collisions are left to user diagnosis. Sources: kandev:cli, kandev:tasks.
Remote setup [supported] SSH/Sprites/Remote-Docker profile setup with helper distribution and digest verification. Sources: kandev:executors.
Automatic repair [partial] Workspace restore/repair and failed-preparation blocking; no autonomous environment healing. Sources: kandev:coord, kandev:executors.
Automation concurrency caps, one-active-run semantics, experimental Office/coordinator spend ceilings, retry policies and provider-failure surfacing bound load; generic turn/token/time caps and scheduler SLAs are not established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Spend ceilings and dynamic-routing retries are experimental and off in production profiles.
No generic per-turn time, turn-count or token caps outside experimental surfaces.
8 atomic answers
Time limits [partial] Cron intervals, stop-confirmation timing and session expiry bounds; no generic turn wall-clock is established. Sources: kandev:automation, kandev:fstatus.
Turn limits [unsupported] No per-turn or per-task turn-count cap was found in bounded search of config, automation and backend docs. Sources: kandev:config, kandev:automation.
Token limits [partial] Spend is observed (stats, session-cost plugin, coordinator meters) with experimental ceilings; no general token cap. Sources: kandev:stats, kandev:coordinator.
Spend limits [partial] Office default 50 USD/day/workspace and coordinator cost ceilings block unattended launches when hit; regular kanban has no spend cap. Sources: kandev:officeops, kandev:coordinator.
Timeouts [partial] Health-check, webhook (10s) and provider/transport timeouts exist; agent turn timeouts are provider-side. Sources: kandev:cli, kandev:webhook.
Boards, session states, Inbox, lifecycle messages, background-work history, debug logs, database views, OTLP tracing and workspace stats (task/agent/repo/time, failure and approval states) keep status consistent from the database; stats are on-demand with no realtime push.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Stats load on demand with no caching or realtime updates.
No vendor speed or success-rate figures are published to attribute.
13 atomic answers
Logs [supported] Debug logs plus database and status views in system settings. Sources: kandev:config, kandev:features.
Traces [supported] Tracing docs and OTLP export with task/session/execution IDs. Sources: kandev:config.
Failure reasons [supported] Session failure alerts, background-work history states and lifecycle messages state reasons. Sources: kandev:sessions, kandev:fstatus.
Usage export [partial] Stats pages expose usage; a usage CSV/API export is not established. Sources: kandev:stats.
Task stats [supported] Completed/in-progress counts, duration sums and daily activity from task tables. Sources: kandev:stats.
Agent stats [supported] Model usage grouped by profile snapshot, agent turns and tool calls. Sources: kandev:stats.
Project stats [supported] Repository stats including commits, files and contributor roll-ups. Sources: kandev:stats.
Time stats [supported] Week/month/all ranges with heatmaps and completed-activity charts. Sources: kandev:stats.
Failure status [supported] Working/blocked/failed/idle distinctions in sessions, runs and background-work views. Sources: kandev:sessions, kandev:automation.
Approval status [supported] PR/MR approval, check and merge-readiness states on linked items and cards. Sources: kandev:sessions.
Reconnect consistency [partial] Database-backed state survives reconnect; multi-org fan-out has known gaps. Sources: kandev:arch, kandev:orgs.
Performance method [unknown] Bounded search of site, docs and releases found no vendor speed or success-rate figures to attribute. Sources: kandev:site, kandev:stats.
Responsiveness [partial] WebSocket live updates for sessions; stats sections load independently with retry on pressure. Sources: kandev:wsapi, kandev:fstatus.
Token/spend visibility comes from chat footers, workspace stats and optional session-cost/provider-usage plugins plus experimental Office budgets; per-child/per-epic roll-ups, billed reconciliation, alerts beyond experimental ceilings, export and drill-down are limited or absent.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No built-in per-task billed-cost view; provider billing stays with the CLI vendor.
Cost export and drill-down are not established.
14 atomic answers
Task cost [partial] Session-cost plugin shows current-session spend and chat footers show some provider estimates; no unified per-task billed view. Sources: kandev:plugins, kandev:sessions.
Session cost [partial] Optional session-cost and provider-usage plugins plus stats model usage; not built in. Sources: kandev:plugins, kandev:stats.
Child cost [partial] Per-session visibility extends to subtask sessions; no child roll-up to the parent. Sources: kandev:plugins, kandev:coord.
Epic cost [unsupported] No epic entity and no cost roll-up across tasks exist in the pinned release. Sources: kandev:stats, kandev:fstatus.
Harness aggregation [partial] Stats group model usage across profile snapshots; cross-harness spend aggregation is not established. Sources: kandev:stats.
Billed vs estimated [partial] Calculated cost kept separate from provider estimates (e.g. native Codex thread estimates). Sources: kandev:agents, kandev:sessions.
Tokens [partial] Token/turn visibility for supporting agents and stats tool-call counts; coverage is agent-dependent. Sources: kandev:sessions, kandev:stats.
Subscription allowance [unsupported] BYO subscriptions are not metered by Kandev; bounded search finds no allowance tracking. Sources: kandev:site, kandev:stats.
Parallel sessions/tasks with automation concurrency limits, automation queueing, exact-run cancellation and resume/retry recovery are shipped; host-aware limits, check reuse/dedup, fairness, backpressure and merge queues are not established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No documented backpressure, fairness, check memoization or dependency-aware merge queue.
12 atomic answers
Concurrency [supported] Parallel named sessions, parallel tasks and multi-repo fan-out with documented limits. Sources: kandev:coord, kandev:features.
Queues [partial] Automation run rows queue with one-active-run semantics; no general scheduling queue UI outside experimental surfaces. Sources: kandev:automation, kandev:fstatus.
Cpu ram [partial] Host resource metrics are displayed; per-task CPU/RAM caps are not established. Sources: kandev:fstatus.
Backpressure [unsupported] No backpressure or admission-shedding mechanism was found in bounded search of backend and docs. Sources: kandev:arch, kandev:automation.
Host awareness [partial] Kandev-host metrics plus execution-environment metrics for separately owned consumers. Sources: kandev:fstatus.
Check reuse [unsupported] No check-result reuse across sessions is documented or implemented. Sources: kandev:gitops, kandev:fstatus.
Check deduplication [unsupported] No verification deduplication was found; 10-round auto-fix caps bound repetition instead. Sources: kandev:sessions, kandev:fstatus.
Bounded tests [unsupported] No product-owned bounded-test scheduling construct exists; checks run via providers and agents. Sources: kandev:fstatus.
Fairness [unsupported] No fairness policy across tasks or epics is documented. Sources: kandev:automation.
Recovery [partial] Resume, repair and retry flows recover work; no scheduler-level recovery guarantees. Sources: kandev:resume, kandev:automation.
Shared limits [partial] Automation concurrency and experimental cost ceilings are shared bounds; general shared-limit accounting is not established. Sources: kandev:automation, kandev:coordinator.
Shared boards, task conversations, comments and takeover (reassign plus continue) let successive colleagues direct the same work with attribution; simultaneous co-prompting with ordering/conflict handling and presence are not established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Multi-user sharing requires the experimental authenticated path.
No simultaneous co-prompting, presence or conflict-resolution model.
11 atomic answers
Visibility [supported] Shared boards, sessions, previews and review panels are visible to authorized colleagues. Sources: kandev:team.
Discussion [supported] Task conversations and thread comments support multi-human discussion. Sources: kandev:sessions.
Comments [supported] Comments on conversations, plans and diffs with anchored references. Sources: kandev:sessions.
Presence [unsupported] No presence indicators were found in bounded search of team/session docs and UI descriptions. Sources: kandev:team, kandev:sessions.
Coprompting [partial] Sequential steering via messaging and takeover; simultaneous co-prompting is not established. Sources: kandev:team, kandev:coord.
Ordering [unsupported] No input-ordering model for concurrent prompts exists. Sources: kandev:team.
Conflicts [unsupported] No prompt-conflict handling exists; takeover proceeds without locking. Sources: kandev:team.
Attribution [supported] Authenticated sessions attribute messages and actions to the acting person. Sources: kandev:team.
Permissions [supported] Unit inheritance plus direct grants; API-only guest role for limited reach. Sources: kandev:team, kandev:auth.
Plan restrictions [partial] No tiered plans exist; the multi-user path itself is experimental and gated by feature flag. Sources: kandev:auth, kandev:fstatus.
Owner online [supported] Takeover continues work after the first person disconnects; the owner need not stay online. Sources: kandev:team.
Admin/member/guest plus instance-operator and org-admin tiers, unit-based workspace reach, invite/disable lifecycle and revocation are documented on the experimental path; SSO is explicitly local-only for now and SCIM-style provisioning does not exist.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Authentication, team access and organizations are experimental with known cross-org gaps.
No SSO or SCIM provisioning.
9 atomic answers
Organization roles [supported] Admin, member and guest roles plus instance-operator versus organization-admin tiers. Sources: kandev:auth, kandev:orgs.
Project roles [partial] Unit membership reaches workspaces beneath it; per-workspace role granularity beyond inheritance is not established. Sources: kandev:team.
Task roles [partial] Human and agent assignees plus experimental reviewer/approver participants; no fine task-role matrix. Sources: kandev:team, kandev:office.
Membership [supported] Invite links (single-use, expiring, pinnable), direct creation and disable flows. Sources: kandev:auth.
Sso [unsupported] Local accounts only for now; the account model is ready for OIDC/SSO later per the authentication doc. Sources: kandev:auth.
Provisioning [partial] Invite/disable lifecycle exists; SCIM or directory-sync provisioning does not. Sources: kandev:auth.
Unauthorized access [partial] Workspace authorization boundary documented alongside known multi-org gaps; untrusted tenants need separate instances. Sources: kandev:orgs, kandev:security.
Revocation [supported] Disabling a user immediately revokes sessions and tokens. Sources: kandev:auth.
Plan scope [supported] No tiers exist: all controls ship in the self-hosted build behind the experimental auth flag. Sources: kandev:auth, kandev:site.
Network [partial] User-initiated tunnels and forwarding; no per-request agent network approval is established. Sources: kandev:tasks, kandev:security.
Secret [partial] Secrets redacted from confirmations with narrowest-scope guidance; no per-use secret approval. Sources: kandev:config, kandev:security.
Delivery [supported] Human gates before merge/ship; PR merges additionally gated on provider required checks. Sources: kandev:tasks, kandev:gitops.
Approver identity [partial] Acting person recorded on human actions; agent-side approver identity beyond session attribution is not established. Sources: kandev:team.
Lifetime [partial] Per-decision sheets; tunnel persistence and 30-day sliding browser sessions documented; approval expiry model not established. Sources: kandev:mobile, kandev:auth.
Allow [supported] Allow paths on permission requests and confirmation sheets. Sources: kandev:sessions, kandev:mobile.
Revoke [partial] User/token revocation, tunnel stop and session stop; no unified grant-revocation ledger. Sources: kandev:auth, kandev:tasks.
Tunnels [supported] Per-task port forwarding with dedicated tunnel URLs and proxy links. Sources: kandev:tasks.
Defaults [partial] Auth-off defaults to full administrator reachability; auto-approve and permissive profiles are operator choices. Sources: kandev:security, kandev:agents.
Safer modes [partial] Restricted permission profiles, plan mode and human-gated steps; no named hardened mode. Sources: kandev:agents, kandev:tasks.
Attributed actions, approvals, plan revisions, discussion and immutable lifecycle templates persist across users and sessions with gist-based sharing and backup portability; no formal audit model, retention schedule or history export is established.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
The word audit is avoided: no defined retention or integrity model exists.
No full-history export; portability is backups, workflow YAML, gist snapshots and git.
11 atomic answers
Actions [supported] Human actions recorded against the acting person; agent actions attributed in sessions. Sources: kandev:team, kandev:sessions.
Approvals [supported] Review and approval decisions recorded on tasks and linked PRs/MRs. Sources: kandev:sessions, kandev:office.
Edits [supported] Plan revisions, thread comments and conversation history track edits. Sources: kandev:tasks, kandev:sessions.
Discussion [supported] Task conversations persist and are re-readable by successors. Sources: kandev:sessions.
Decisions [supported] Step-completion signals, review decisions and immutable lifecycle templates record decisions. Sources: kandev:tasks, kandev:sessions.
Cross user persistence [supported] Shared boards and takeover keep history across people. Sources: kandev:team.
Cross session persistence [supported] SQLite persistence plus resume keeps history across sessions and restarts. Sources: kandev:arch, kandev:resume.
Export [partial] Redacted gist snapshots and backups; no dedicated history export. Sources: kandev:features.
Mutability [partial] Lifecycle templates are immutable server-owned text; general tamper-evidence is not established. Sources: kandev:sessions.
Retention [partial] Quick Chat 7-day sweep and Office 400-day report retention documented; no install-wide retention schedule. Sources: kandev:fstatus, kandev:coordinator.
Integrity [partial] Release checksums exist for artifacts; no history integrity model is published. Sources: kandev:releases.
Board review columns with PR badges, diff/Changes panels, walkthroughs, plan comments, feedback-to-agent and re-review loops, keyboard shortcuts and an extensively documented narrow-screen phone flow; no formal next-action engine or effort metrics.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Stale detection exists but anchored references can drift.
No batch review queue outside experimental surfaces.
Comments [supported] Anchored and thread comments with replies and resolve flows. Sources: kandev:sessions.
Request changes [supported] Feedback to agents, review requests, re-review and auto-fix rounds. Sources: kandev:sessions.
Shipping guidance [partial] Next-step move actions and merge-readiness display; no formal next-action engine. Sources: kandev:tasks, kandev:sessions.
Effort [partial] Command palette, shortcuts and saved prompts reduce effort; no effort estimation or measurement. Sources: kandev:sessions, kandev:features.
Missed evidence [partial] Stale detection, drift warnings on walkthrough anchors and head-change guards; silent gaps are not proven absent. Sources: kandev:sessions, kandev:gitops.
Keyboard [supported] Customizable keyboard shortcuts with command palette and focus-visible navigation. Sources: kandev:sessions.
Narrow screen [supported] Phone-first task, review, port and confirmation flows documented for narrow screens. Sources: kandev:mobile.
Context switching [partial] Multi-panel workbench, session tabs and preserved drafts; no measured context-switch cost. Sources: kandev:sessions.
Roles [partial] Agent logos, assignee rows and reviewer/approver seats clarify roles; coordinator-vs-agent clarity is experimental. Sources: kandev:team, kandev:office.
Retained context [supported] Conversations, plans, walkthroughs and review state persist for later review. Sources: kandev:sessions, kandev:resume.
Takeover is reassign plus continue with no lock: successors keep task, session history, decisions, artifacts and executor context, with attribution and documented summarization/idle-boot caveats; cross-harness transfer works via profile handoff.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No locking: simultaneous writers can collide.
Agents without resume support boot idle with no context restoration.
12 atomic answers
Ongoing takeover [supported] Ongoing work is taken over via reassign plus continue without tearing down sessions. Sources: kandev:team.
Same task [supported] Takeover keeps the same task, not a fork or copy. Sources: kandev:team.
Session history [supported] Full conversation history is visible to the successor. Sources: kandev:team, kandev:sessions.
Decisions [supported] Recorded decisions, plans and review state carry over. Sources: kandev:team, kandev:sessions.
Runtime context [partial] Same executor environment continues; agent-native resume or history injection restores context where supported. Sources: kandev:team, kandev:resume.
Owner disconnect [supported] Work continues after the first person disconnects; services and resume cover absence. Sources: kandev:team, kandev:service.
Attribution [supported] Actions attribute to the acting person after takeover. Sources: kandev:team.
Context loss [partial] Summaries may omit constraints and idle-boot agents lose context; passthrough transfers are lossy. Sources: kandev:sessions, kandev:resume.
Harness transfer [supported] Handoff to another agent profile moves work across harnesses within the same task. Sources: kandev:sessions, kandev:agents.
Diffs, task documents, walkthroughs, plans, previews, tunnels and PR evidence persist with tasks and sessions; image/file attachments supported; no recordings, no cross-task gallery, no test-report collection.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No screen/audio recordings.
No searchable cross-task artifact gallery; retrieval is per task plus stats pages.
No dedicated test-output collection.
13 atomic answers
Diffs [supported] Staged/unstaged/commit, multi-repo and submodule diff views with review hashes and stale detection. Sources: kandev:sessions, kandev:gitops.
Documents [supported] Per-task Markdown documents (plans, specs, notes, reviews) with revision history. Sources: kandev:features.
Screenshots [partial] Image attachments on answers and prompts; no screenshot-capture workflow is established. Sources: kandev:sessions.
Recordings [unsupported] No recording capture or playback was found in bounded search of docs and the pinned release. Sources: kandev:sessions, kandev:features.
Previews [supported] Browser preview, forwarded ports with tunnel/proxy URLs for live work. Sources: kandev:sessions, kandev:tasks.
Test outputs [partial] Provider check results and agent tool activity surface; no dedicated test-report gallery. Sources: kandev:sessions.
Reviewer outputs [partial] Walkthroughs, plan comments and review decisions persist per task; no cross-task reviewer roll-up. Sources: kandev:sessions.
Gallery [partial] Per-task panels plus stats pages; no unified searchable cross-task gallery. Sources: kandev:tasks, kandev:stats.
Task links [supported] Associated PR/MR links with numbers, URLs, titles and states on tasks. Sources: kandev:integrations, kandev:features.
Revision links [supported] Commits, plan revisions and recovery branches link work to exact revisions. Sources: kandev:gitops, kandev:sessions.
Persistence [supported] Artifacts persist in SQLite after sessions end, subject to documented sweeps. Sources: kandev:arch, kandev:fstatus.
Child findings [partial] Subtask outputs visible via related-task inspection; no aggregated child-findings view. Sources: kandev:coord, kandev:features.
Prompt leakage [partial] Redacted gist snapshots with preview and revoke; heuristic redaction is explicitly not exhaustive. Sources: kandev:features.
Tests/lint/CI surface through provider checks and agent runs with human gates and provider-enforced merge blocking; agent assertions never count as gates; no product-run verification and no persistent-spec conformance checks exist.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Kandev runs no tests itself; verification executes via agents/providers.
No persistent-spec conformance gates.
11 atomic answers
Tests [partial] Agent-run tests and provider CI checks surface in PR detail; Kandev itself executes no test runner. Sources: kandev:sessions.
Lint [partial] Lint/type feedback arrives via agent runs and CI; no product lint gate. Sources: kandev:sessions.
Types [partial] Type feedback via agents/CI only. Sources: kandev:sessions.
Ci [supported] GitHub/GitLab check and pipeline states display with merge-readiness roll-ups. Sources: kandev:sessions.
Independent review [supported] Human review/approval stages plus provider reviewer flows gate delivery. Sources: kandev:sessions, kandev:office.
Spec checks [unsupported] No persistent-spec conformance checks exist in the pinned release. Sources: kandev:fstatus, kandev:office.
Required checks [partial] Human gates and step-completion gating are product-required; test gates are provider-required. Sources: kandev:tasks, kandev:sessions.
Failure blocking [partial] Failing provider checks block auto-merge and merge; local pre-push verification is guidance. Sources: kandev:sessions.
Requirement conflicts [partial] Head-change guards and divergence handling block unsafe publishes; spec conflicts have no model. Sources: kandev:gitops.
Configured policy [partial] Workflow completion policies, WIP rules and profile permissions configure gating; test policy is provider-side. Sources: kandev:tasks, kandev:agents.
Enforced policy [partial] Provider merge gates and product MCP validation enforce; agent claims alone never satisfy a gate. Sources: kandev:gitops, kandev:automation.
PR/MR approvals submittable where permitted, provider-gated merges from the task panel, exact-revision head checks; no release management, no deployment authority and no deployment rollback exist.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Merge is the terminal product action; release and deploy are out of scope.
Provider permissions are authoritative throughout.
6 atomic answers
Approve [partial] Approvals submittable where the linked account permits; GitHub/GitLab policy decides. Sources: kandev:sessions.
Merge [supported] Merge from the panel once required checks, review state and mergeability pass. Sources: kandev:sessions, kandev:gitops.
Release [unsupported] No release creation or management exists in the pinned release. Sources: kandev:gitops, kandev:fstatus.
Deploy [unsupported] No deployment authority or environment promotion exists; Sprites sandboxes are ephemeral task runtimes. Sources: kandev:executors, kandev:fstatus.
Exact revision [partial] Exact provider-head checks precede publish actions; approvals are not provably pinned to revisions. Sources: kandev:gitops.
Authority enforcement [partial] Provider permissions plus scoped leases enforce; Kandev adds confirmation and gate checks. Sources: kandev:executors, kandev:sessions.
Task-to-commit/PR links, Done states, retained conversations/diffs/lifecycle records and guarded publish/restore with recovery branches; no deploy rollback and no general approval-invalidation model.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Rollback is Git-history scoped (restore with recovery branch), not deployment scoped.
Approval invalidation on edit is head-check scoped, not general.
Build links [partial] CI/build states surface on linked items; no build-artifact links are established. Sources: kandev:sessions.
Deployment links [unsupported] No deployments exist to link; bounded search finds no deployment records. Sources: kandev:executors, kandev:fstatus.
Delivery status [supported] Done steps, merged/closed lifecycle messages and card badges mark delivery. Sources: kandev:tasks, kandev:sessions.
Retained evidence [supported] Conversations, diffs, plans and lifecycle records persist after delivery. Sources: kandev:sessions, kandev:resume.
Rollback [partial] Restore-published-PR-version with recovery branch; no deployment rollback. Sources: kandev:gitops.
Revert [partial] Reset/discard and restore flows revert history with clean-tree guards; no one-click revert. Sources: kandev:gitops.
Stale approval invalidation [partial] Stale detection and head-change guards; no general approval-invalidation rule. Sources: kandev:sessions, kandev:gitops.
AGPL-3.0 covers the main application (backend, web, CLI, desktop, plugin SDK) in one public repository at the pinned commit; no proprietary or source-available component split was found; 1126 stars measure attention, not license parity.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
License statement covers the repository as a whole; no per-component license matrix is published.
6 atomic answers
Client license [supported] Web, CLI and Tauri desktop ship from the same AGPL-3.0 repository. Sources: kandev:license, kandev:repo.
Server license [supported] Go control plane is in the same AGPL-3.0 repository and commit. Sources: kandev:license, kandev:arch.
Hosted extensions [supported] Plugin SDK and first-party plugins live in public kdlbs repositories; no closed hosted extension is evidenced. Sources: kandev:sdk, kandev:repo.
Source visibility [supported] All product repositories observed are public. Sources: kandev:repo.
Source revision [supported] Pinned release v0.101.0 commit 3c2f7e9 inspected for this profile. Sources: kandev:repo, kandev:releases.
Hosted parity [supported] No vendor-hosted variant exists, so no parity gap can arise; self-built equals upstream. Sources: kandev:site, kandev:repo.
Fully self-hostable (binary, service, Docker, k8s example, source) with SQLite/Postgres data, backup download/restore, workflow YAML portability and git-held code; no vendor account exists so nothing is held hostage; per-task portable export is limited.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No unified full-fidelity export of tasks, context and history; portability composes backups, YAML, gists and git.
Remote helpers download from GitHub on first remote use (offline archives documented).
8 atomic answers
Self hosting [supported] Native binary, OS service, Docker image, k8s example and source builds all run the full control plane. Sources: kandev:service, kandev:docker, kandev:k8s.
Vendor dependencies [partial] GitHub release-asset downloads for remote helpers; optional NATS/Postgres; provider CLIs and Sprites are user-chosen. Sources: kandev:executors, kandev:usek.
Export [partial] Backup download/restore, workflow YAML export and redacted gist snapshots; no single full-fidelity export. Sources: kandev:features, kandev:wfie.
Formats [partial] SQLite, YAML, Markdown and git formats; no documented standard interchange beyond those. Sources: kandev:arch, kandev:wfie.
Cancellation [supported] No vendor account or subscription exists to cancel; uninstall removes the install. Sources: kandev:site, kandev:auth.
Account independence [supported] Everything works without any vendor account; only third-party provider accounts apply. Sources: kandev:site, kandev:usek.
History portability [partial] Database backups and gist snapshots carry history; per-task portable history files are not established. Sources: kandev:features.
Self-hosted data stays local with encrypted secret store, scoped credential leases and redacted sharing; no telemetry is collected so no opt-out or consent prompt exists; provider-side model data use follows the CLI vendors, not Kandev.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Model providers of the chosen CLIs have their own data policies outside Kandev control.
Auth-off installs give every reachable client administrator access.
15 atomic answers
Code data [supported] Code stays in user workspaces on user infrastructure; agents see only executor-scoped checkouts. Sources: kandev:security, kandev:executors.
Prompts [supported] Prompts stay local; OTLP export and debug endpoints can expose them only if the operator enables them. Sources: kandev:config.
Logs [partial] Local logs and database views; debug/OTLP detail can include prompts and tool data with operator-side controls required. Sources: kandev:config.
Artifacts [supported] Artifacts persist locally; sharing is explicit, redacted, previewed and revocable. Sources: kandev:features.
Retention [partial] Quick Chat 7-day sweep, retention settings and Office 400-day reports; no install-wide retention schedule. Sources: kandev:fstatus, kandev:coordinator.
Deletion [supported] Delete flows for tasks, sessions, documents, shares, users and backups with confirmations. Sources: kandev:tasks, kandev:sessions.
Training [partial] No Kandev training use (no telemetry, no vendor model); CLI vendors have their own policies. Sources: kandev:readme, kandev:site.
Residency [supported] Residency is wherever the operator hosts; no vendor storage or subprocessor geography applies. Sources: kandev:site, kandev:service.
Subprocessors [supported] No subprocessors: no vendor cloud processes customer data; provider calls go through user CLIs. Sources: kandev:site, kandev:readme.
Telemetry disclosure [supported] No telemetry is collected, stated in the README and marketplace docs. Sources: kandev:readme, kandev:plugins.
Telemetry defaults [supported] Nothing to disable: no telemetry exists in any shipped profile. Sources: kandev:readme.
Telemetry controls [supported] No telemetry control is needed; unrelated feature/debug toggles are documented separately. Sources: kandev:fstatus, kandev:config.
Consent prompt [supported] No consent prompt exists because no telemetry or vendor data collection exists. Sources: kandev:readme.
Provider separation [supported] Kandev-side handling is separated from CLI model-provider policies throughout the docs. Sources: kandev:security, kandev:integrations.
The ADE itself is free of charge: AGPL-3.0 open source, no pricing page, no plans, seats, trials, overages or taxes; model and compute spend goes to third parties chosen by the operator.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
12 atomic answers
Currency [supported] No charge in any currency; no billing surface exists. Sources: kandev:site.
Interval [supported] No billing interval; software is a free download. Sources: kandev:site, kandev:usek.
Seats [supported] No seat licensing; team sharing uses the self-hosted auth path. Sources: kandev:site, kandev:team.
Seat minimum [supported] No seat minimum exists. Sources: kandev:site.
Workspace fees [supported] No workspace or usage fees exist. Sources: kandev:site.
Included usage [supported] All product capabilities are included; agent/compute usage is third-party. Sources: kandev:site, kandev:readme.
Credits [supported] No credit system exists. Sources: kandev:site.
Trial [supported] No trial construct; the full product is free from first install. Sources: kandev:site, kandev:usek.
Overages [supported] No overages can occur; there is nothing metered by Kandev. Sources: kandev:site.
Taxes [supported] No taxed Kandev purchase exists. Sources: kandev:site.
Model cost [partial] Model spend is paid to CLI vendors via user subscriptions/keys, outside Kandev pricing. Sources: kandev:usek, kandev:site.
Compute cost [partial] Compute is user infrastructure or third-party (Sprites); no Kandev compute charge. Sources: kandev:executors, kandev:site.
Fixed ADE cost is $0 for one, two and five developers including collaboration, review and remote-execution features; variable model/provider/Sprites spend is operator-paid and unstated by Kandev; stats and optional cost plugins reconcile observed use.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
No stated per-task, per-token or per-compute-hour workload cost; variables stay unknown, never zero.
No budget alerts outside experimental Office/coordinator ceilings.
11 atomic answers
One person [supported] One developer: $0 ADE cost; provider keys and own host optionally paid to third parties. Sources: kandev:site.
Two people [supported] Two developers collaborating over experimental team access: $0 ADE cost. Sources: kandev:site, kandev:team.
Five people [supported] Five developers: $0 ADE cost; no per-seat licensing. Sources: kandev:site.
Task assumptions [partial] No canonical task/token assumptions published; stats group observed use by model snapshot. Sources: kandev:stats.
Tokens [partial] Token spend is third-party; Kandev observes but does not price it. Sources: kandev:stats.
Compute hours [partial] Compute hours are user infrastructure or Sprites-billed; unpriced by Kandev. Sources: kandev:executors.
Fixed cost [supported] Fixed ADE cost is $0 in every scenario. Sources: kandev:site.
Variable cost [partial] Variables are provider subscriptions/keys and Sprites; amounts are vendor-stated, not Kandev-stated. Sources: kandev:usek, kandev:executors.
Public pre-1.0 releases (v0.101.0 on 2026-11-11, active main-branch commits), no access gate, community support via Discord and GitHub issues with no SLA, no status page, and backup/workflow portability for exit.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
Desktop installers in this release are unsigned development builds.
No SLA, support tiers or status history page.
8 atomic answers
Release stage [supported] Public 0.x release line (v0.101.0) with Stable and Nightly channels. Sources: kandev:releases, kandev:usek.
Access restrictions [supported] No gate: public repository, free downloads, open install channels. Sources: kandev:repo, kandev:usek.
Support [partial] Discord and GitHub issues; no committed support channel or SLA. Sources: kandev:readme, kandev:site.
Response commitments [partial] No response-time commitments published. Sources: kandev:site.
Release activity [supported] v0.101.0 shipped 2026-11-11 with ongoing main-branch commits into 2026-11-12. Sources: kandev:releases, kandev:repo.
Status history [partial] No status page or incident history was found in bounded search of site and docs. Sources: kandev:site.
Deprecation [partial] Versioned workflow YAML and backups ease migration; no deprecation policy published. Sources: kandev:wfie, kandev:features.
Export options [supported] Backups, workflow YAML and git-held code support leaving. Sources: kandev:features, kandev:wfie.
The whole product is free and open source indefinitely (self-hosted, no card, no sales approval); every scenario including two-person collaboration, BYO subscriptions, remote compute, mobile browser, issue management and review works at $0 ADE cost with provider-side caps only.
Scope
Surfaces: Kandev web application (browser, incl. phone browser), Kandev Tauri desktop app, Programmatic surface (WebSocket, REST, external MCP) · Version: v0.101.0 (commit 3c2f7e98689aab4e7bc97ece277c4f5abe04e951); first-party source pass 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-14
10 atomic answers
Ongoing free [supported] AGPL-3.0 self-hosting is free indefinitely, not a trial. Sources: kandev:license, kandev:site.
Trial [supported] No trial construct; full product from first install. Sources: kandev:site.
Credits trial [supported] No credits-based trial exists. Sources: kandev:site.
Self host cost [supported] Self-host cost is operator infrastructure only; $0 to Kandev. Sources: kandev:site, kandev:service.
Paid only [supported] Nothing is paid-only; no paid tier exists. Sources: kandev:site.
Early access [supported] No gated early access; Nightly channel is public. Sources: kandev:usek.
Free scenarios [supported] Collaboration, BYO subscriptions/keys, SSH/Sprites compute, mobile browser, issue management and review all work free of ADE charge. Sources: kandev:team, kandev:executors, kandev:mobile.
Card required [supported] No card required anywhere in the Kandev install path. Sources: kandev:site, kandev:usek.
Usage caps [partial] Kandev imposes no caps; provider rate limits and Sprites billing are third-party. Sources: kandev:integrations, kandev:executors.
Paid evaluation [supported] No payment or sales approval is needed for any evaluation. Sources: kandev:site.
Kanban/pipeline views with parallel tasks; ~25 named agent CLIs; CLI passthrough; worktree isolation; multi-repo tasks; local/Docker/SSH/Sprites runtimes; task and external MCP; plugin marketplace; open source, self-hosted, no telemetry, no tied cloud. Distributed as native Go binary per platform with embedded web UI.
Installs via Homebrew tap, Scoop, npm/npx/global npm; kandev run/start commands, --port/--headless flags; default backend port 38429 with auto-select; data under ~/.kandev; service install targets; runtime bundles include agentctl helpers.
Kind
documented
Locator
docs/cli.md and docs/public/cli.md install/commands/ports sections
Native Windows x64 desktop (NSIS) and npm/npx CLI paths; WSL2 path for Linux-only tools; Windows ARM64 has no native artifact and x64 emulation is not a release target.
Kind
documented
Locator
docs/public/windows-support.md native paths and ARM64 note
Phone reaches the same Kandev web app origin via Tailscale Serve, Cloudflare Tunnel/Access or private VPN; phone task controls, bottom-sheet confirmations and narrow-screen layouts documented; unauthenticated origin means administrator access; auth stays a separate boundary.
Kind
documented
Locator
docs/public/mobile-remote-access.md access-boundary and Tailscale/Cloudflare sections
Named parallel sessions sharing one task environment; clarification/permission questions with attachments; Changes and cumulative Review with diffs, anchored comments, stale detection; GitHub PR detail with checks/reviews/merge and GitLab MR panel; background-work view; keyboard-shortcut settings; walkthrough per task.
OS-managed service via systemd user/system units and macOS launchd with auto-start and self-update channels; Windows service mode not supported; phone access via the remote-access guide.
Kind
documented
Locator
docs/run-as-a-service.md user/system mode and Windows sections
Prerequisites (Git, agent-CLI credentials Kandev does not create, npm 7+ only for npm channel, Docker only for Docker profiles); Homebrew/Scoop/npm/npx channels with Stable/Nightly tags; fresh database seeds Default Workspace, Development workflow, Local/Worktree executors.
Lazy recovery after backend restart: NeedsResume detection, agentctl plus agent relaunch; native ACP session resume where supported else history injection; agents with neither flag boot idle without context restoration.
Kind
documented
Locator
docs/task_session_resume.md recovery-strategy and flow sections
Web app ships a manifest (name Kandev, start_url /, display standalone with window-controls-overlay override, 192/512 icons); no store listing or install prompt is documented.
WebhookProvider delivers versioned notification events to configured HTTP endpoints with 10s timeout, 4KiB body cap and private-link ranges blocked unless allow-listed; configured under notifications.* settings.
Control plane is one Go process serving web app, HTTP API, WebSocket, health and external MCP routes; agents run via executors and agentctl runtime on host/container/remote; SQLite default with PostgreSQL option; in-memory bus default with NATS option; Tauri shell starts native backend headless.
Kind
documented
Locator
docs/ARCHITECTURE.md Runtime shape and Persistence sections
Opt-in experimental runtime flag (KANDEV_FEATURES_AUTH), off in every shipped profile; email+password accounts, admin/member/guest roles, invite links, kandev_pat_ bearer tokens for scripts/external MCP; local accounts only for now, OIDC/SSO later.
Kind
documented
Locator
docs/public/authentication.md enabling/users/PAT sections and local-accounts note
Open-source agent-neutral workbench running on user infrastructure; agent list (Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Amp, Auggie, Cursor, Qwen, Kiro, Qoder and more); execution rows Local/Worktree/Docker/Sprites/SSH; community stats; no pricing, paid tier or vendor-cloud offering anywhere on the page.
Kind
documented
Locator
Homepage hero, Agents, execution and Community sections
Per-capability contract: Supported, Dependency-bound, Limited, Experimental, In progress, Internal with current boundaries; authentication/team access experimental; labels Office-only in progress; push/CI triggers in progress; Office mode in progress and disabled in production.
Workspace automations from schedule (@every/cron presets; fixed-cron timezone limitation noted), authenticated webhooks, GitHub PR-open/PR-merged (push/CI in progress); hidden or normal-task targets; concurrency limit with one active run for reusable mode; retry policy; configuration chat can create automations.
Single /ws connection carrying JSON action messages (board/column/task/session operations) with request/response/notification/error envelope and named error codes; documented as the complete programmatic surface alongside REST routes.
Office is experimental and disabled by default in production; persistent agent teams, projects, routines, review/approval stages; routes/agents/labels/costs may change between releases.
Kind
documented
Locator
docs/public/office.md status and workflow sections
In-app catalog with search/category/stars sorting, verified install pipeline, update flow, team sources; loaded plugin code runs with backend privileges so only trusted plugins should be installed; no download/usage telemetry collected.
apps/desktop is a Tauri shell: Rust starts bundled kandev --headless on an owned loopback origin and owns native windows, external links, notifications and updates; product UI remains the backend-served SPA.
Kind
documented
Locator
docs/public/architecture.md trust-boundary and apps/desktop bullets
Coordination boundaries (session, inherited subtask, new workspace, multi-repo task); spawn_session_kandev and message_task_kandev agent tools with attribution; coordinator-led work listed as shipped direction with Office-gated remainder.
Kind
documented
Locator
docs/public/coordination.md boundary table and spawn/dependency sections
v0.101.0 published 2026-11-11; notes list feature/fix PRs; macOS and Windows desktop installers in this release are unsigned development builds requiring manual OS security bypasses.
Workspace analytics at /stats (week/month/all) computed on demand from task/session/commit tables: completed counts, duration, tool calls, model usage grouped by profile snapshot, repo and Git stats, workload; single-fetch page loads, no caching or realtime updates.
Checked-in single-replica control-plane deployment example, explicitly not an HA topology; separate opt-in Kubernetes executor runs one Pod per task with namespaced RBAC.
Built-in ceiling defaults to 50 USD priced spend per workspace per UTC day for unattended runs, blocking new unattended launches at the limit; unknown/unavailable spend shown as unknown, never zero.
Experimental tenant identifier above users; normal reads org-scoped but user-admin, install-wide system operations and WebSocket fan-out have known cross-organization gaps; untrusted tenants must use separate instances.