Orchestrator / PRODUCT DOSSIER

Vibe Kanban

A planning and review board built around coding-agent workspaces.

Local & browser · Open source · Apache-2.0Revision 2026-09-13.4 · unreviewedNeeds recheck · recheck 2026-10-130 attestations · checked 2026-09-13

What we do not know yet · 2 open gaps

  • Project announces sunsetting and community maintenance; evaluate maintenance risk.
  • Recheck the supported release and setup before attempting reproduction.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Applicability, 3 recheck triggers & verification plan

Applicability

Unpinned public documentation as of 2026-09-13

Documentation review only

Excludes: Runtime behavior; Performance comparisons; Security guarantees

Recheck when

  • Documentation changes
  • New product release
  • License change

Needs recheck · due

Verification plan

  1. Pin a product release or repository commit and record the host environment.
  2. Create a disposable repository with a passing baseline test.
  3. Run a bounded change with two agents where supported; record permissions and logs.
  4. Record a failed attempt, actual outcome, and artifacts without secrets.
  5. Have another person reproduce the result before labeling it reproduced.

Provenance & review

Testedknowhow initial research

Commissioned by a Nimbalyst maintainer; not an independent comparison.

Revision 2026-09-13.4 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 9 / 46 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Orchestration

Parallel agentsYes
Explore Parallel agents →

Runs local coding agents in parallel.

Git worktreesYes
Explore Git worktrees →

Automates Git worktree creation and setup scripts.

Agent choiceYes
Explore Agent choice →

Supports Claude Code, Codex, OpenCode and other agents.

Task managementYes
Explore Task management →

Organizes work into issues and sub-issues.

Review & delivery

Change reviewYes
Explore Change review →

Supports code review with comments on agent changes.

Work surface

Code editingYes
Explore Code editing →

Supports click-to-edit app components during QA.

Browser interactionYes
Explore Browser interaction →

Includes a browser for testing app changes.

Visual selection contextYes
Explore Visual selection context →

Click-to-edit targets components during browser QA.

Scope: Documented QA workflow; sunset notice applies.

Execution & access

Team collaborationYes
Explore Team collaboration →

Documents collaborative team issue tracking.

Unknown · 37 capabilities without evidence

Interface images & local attachments

Sources · 3

vendor-documentation · locator & rights

Homepage: sunset notice and parallel-agent workflow. Repository identifies Apache-2.0.

Link and authored summary only; upstream content retains its own rights.

[2]Vibe Kanban repository ↗0 / 9 claims
repository · locator & rights

Repository overview and license; no product execution.

Upstream license applies.

[3]Vibe Kanban · expanded overview ↗4 / 9 claims
vendor-documentation · locator & rights

Review code; QA changes; end-to-end team workflow.

Authored summary and link only; upstream rights retained.