Shutdown notice
Announced 10 Apr 2026, no end date yet
bloop announced its closure and the retirement of vendor-hosted kanban issues, comments, projects and organisations. The announcement explicitly preserves local workspaces.
Dates, scope and sources
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
What would a community edition of Vibe Kanban look like?
Finding: Louis asks for community direction and maintainers. His June 7 reply calls the earlier orchestrator experiment unreleased. This is a discussion, not a committed feature delivery schedule.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
Vibe Kanban
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websitevibekanban.com Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Yes
- Phone
- Not listed
- Command line
- Yes
- Agents
- Claude Code, Codex, Cursor Agent, Gemini CLI and OpenCode
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree
- Parallel agents
- Yes
- Scheduled runs
- No
- Coordinator agent
- Yes
- Built-in issues
- No
- Pull requests
- Yes
- Review screen
- Yes
- Team
- Not listed
- Self-hosting
- Yes
- Licence
- Apache-2.0
- Price from
- Free
- How it charges
- Not listed
- Paid plans from
- Not listed
Receipts
- Checked
- · oldest answer 2026-11-07
- Findings
- 43 published · 32 cross-checked by a second agent · read them all
- Sources
- 49 public pages on 2 sites: vibekanban.com, github.com
- Screenshot
- github.com, retrieved · first party repository · shows appearance, not capability
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
Source and scope for Where you use itAgents it runs
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
Source and scope for Agents it runsAccounts and subscriptions
Local Codex uses native login or API keys and detects custom configuration directories.
Source and scope for Accounts and subscriptionsWhere agents run
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
Source and scope for Where agents runHow work is kept apart
Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
Source and scope for How work is kept apartParallel work
Docs describe independent sessions that can run simultaneously and multiple workspaces. No measured concurrency fixture was run.
Source and scope for Parallel workScheduled runs
In the pinned local continuation, work starts through explicit session/workspace requests. The local router, services and MCP expose no product-owned schedule or external-event task starter. Remote PR-review webhook code belongs to the retired hosted service.
Source and scope for Scheduled runsGit and pull requests
Local workspace docs cover branches/worktrees, PR creation, push, merge and rebase/conflict handling. No draft-PR scenario was executed.
Source and scope for Git and pull requestsLicence and source
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
Source and scope for Licence and sourceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | Yes |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | Unknown |
| CLI | Yes |
| Coding agents: Claude Code | Yes cross-checked |
| Coding agents: Codex | Yes cross-checked |
| Coding agents: Cursor Agent | Yes cross-checked |
| Coding agents: Gemini CLI | Yes cross-checked |
| Coding agents: OpenCode | Yes cross-checked |
| Coding agents: Pi | No |
| Coding agents: Grok | No |
| Coding agents: Aider | No |
| Coding agents: Antigravity | No |
| Use my subscription | Yes cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | No |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes |
| Native issue tracking | No cross-checked |
| Unattended triggers | No |
| Shared prompting | Unknown |
| Team roles | Unknown |
| SSO | Unknown |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes cross-checked |
| Product license: Apache-2.0 | Yes. Apache-2.0 cross-checked |
| Product license: MIT | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: Elastic License 2.0 | No. Apache-2.0 cross-checked |
| Product license: Custom terms | No. Apache-2.0 cross-checked |
| Product license: Proprietary | No. Apache-2.0 cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Unknown |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Unknown |
| Pricing model: Free plan | Unknown |
| Pricing model: Subscription | Unknown |
| Pricing model: Per seat | Unknown |
| Pricing model: Usage-based | Unknown |
| Pricing model: Per machine or compute | Unknown |
| Pricing model: Bring your own key | Unknown |
| Pricing model: One-time purchase | Unknown |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | No. Sunsetting cross-checked |
| Lifecycle status: Sunsetting | Yes. Sunsetting cross-checked |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. Apache-2.0 cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Unknown |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
Web client: Yes
Web client
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Browser: Local npx client opens the workspace UI in a browser.
- Cli: npx launches the UI and --mcp launches a stdio server. This does not establish a complete command-based task-management CLI.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
Vibe Kanban complete native client distribution matrix
Finding: The pinned release workflow builds native server/CLI and Tauri client targets for macOS, Windows and Linux, and publishes desktop DMG, AppImage, DEB, MSI and EXE installers. Its complete native build and installer inventory has no iOS or Android phone package. Browser clients are separate.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
Vibe Kanban complete native client distribution matrix
Finding: The pinned release workflow builds native server/CLI and Tauri client targets for macOS, Windows and Linux, and publishes desktop DMG, AppImage, DEB, MSI and EXE installers. Its complete native build and installer inventory has no iOS or Android phone package. Browser clients are separate.
CLI: Yes
CLI
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The released vibe-kanban npm command registers three subcommands: the default launches the local app (browser, or desktop with --desktop), review runs a PR review CLI, and mcp runs the local MCP server.
Coding agents: Claude Code: Yes cross-checked
Coding agents: Claude Code
Typed value: Yes.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Model providers: Documented agent variants expose model choices; the complete provider/model matrix and current entitlements are unverified.
- Session integration: Codex adapter uses its app-server for structured thread start/fork and session work. Other adapters require separate inspection.
- Mixed harness operation: Docs describe sessions with different agents sharing workspace files; no mixed-harness run was observed.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
Coding agents: Codex: Yes cross-checked
Coding agents: Codex
Typed value: Yes.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Model providers: Documented agent variants expose model choices; the complete provider/model matrix and current entitlements are unverified.
- Session integration: Codex adapter uses its app-server for structured thread start/fork and session work. Other adapters require separate inspection.
- Mixed harness operation: Docs describe sessions with different agents sharing workspace files; no mixed-harness run was observed.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
Coding agents: Cursor Agent: Yes cross-checked
Coding agents: Cursor Agent
Typed value: Yes.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Model providers: Documented agent variants expose model choices; the complete provider/model matrix and current entitlements are unverified.
- Session integration: Codex adapter uses its app-server for structured thread start/fork and session work. Other adapters require separate inspection.
- Mixed harness operation: Docs describe sessions with different agents sharing workspace files; no mixed-harness run was observed.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
Coding agents: Gemini CLI: Yes cross-checked
Coding agents: Gemini CLI
Typed value: Yes.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Model providers: Documented agent variants expose model choices; the complete provider/model matrix and current entitlements are unverified.
- Session integration: Codex adapter uses its app-server for structured thread start/fork and session work. Other adapters require separate inspection.
- Mixed harness operation: Docs describe sessions with different agents sharing workspace files; no mixed-harness run was observed.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
Coding agents: OpenCode: Yes cross-checked
Coding agents: OpenCode
Typed value: Yes.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Model providers: Documented agent variants expose model choices; the complete provider/model matrix and current entitlements are unverified.
- Session integration: Codex adapter uses its app-server for structured thread start/fork and session work. Other adapters require separate inspection.
- Mixed harness operation: Docs describe sessions with different agents sharing workspace files; no mixed-harness run was observed.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
Coding agents: Pi: No
Coding agents: Pi
Typed value: No.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
Coding agents: Grok: No
Coding agents: Grok
Typed value: No.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
Coding agents: Aider: No
Coding agents: Aider
Typed value: No.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
Coding agents: Antigravity: No
Coding agents: Antigravity
Typed value: No.
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Harnesses: Local adapters include Claude Code, Codex, Amp, Gemini CLI, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
Use my subscription: Yes cross-checked
Use my subscription
Typed value: Yes.
Local Codex uses native login or API keys and detects custom configuration directories.
- Account switching: CODEX_HOME can separate work/personal Codex configuration; no in-app account switching or multiple simultaneous entitlement test.
- Codex login docs and shutdown notice; current provider entitlements, account switching and local-model routes were not verified.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Vibe Kanban Login; Custom configuration
Finding: Local Codex setup explicitly uses provider login with ChatGPT plan or OPENAI_API_KEY. CODEX_HOME custom configuration/session path is detected. Current provider plan eligibility is not independently established.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
- Local: The local client runs coding-agent workspaces on the user computer.
- Local startup, remote SSH and Docker guide; no disconnect/other-device continuation experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
- Byo remote: Settings document running Vibe Kanban on a user server and opening files over SSH. Disconnect/continuation was not tested.
- Local startup, remote SSH and Docker guide; no disconnect/other-device continuation experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
- Local: The local client runs coding-agent workspaces on the user computer.
- Local startup, remote SSH and Docker guide; no disconnect/other-device continuation experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
- Branch: Local workspaces create a working branch and Git worktree.
- Worktree: Local workspaces create a working branch and Git worktree.
- Code separation: Worktree-based separation is documented; two conflicting changes were not executed.
- Workspace/session docs and harness sandbox settings; no code-isolation or hostile-code boundary test.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
Workspace isolation: Container: No
Workspace isolation: Container
Typed value: No.
Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
- Container: The pinned local continuation starts agent executors directly in workspace directories; no product container or VM execution backend exists. Provider sandbox flags are separate.
- Vm: The pinned local continuation starts agent executors directly in workspace directories; no product container or VM execution backend exists. Provider sandbox flags are separate.
- Workspace/session docs and harness sandbox settings; no code-isolation or hostile-code boundary test.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Vibe Kanban local execution ownership
Finding: The local service starts coding-agent executors directly in workspace directories and retains their child processes and exit monitors in the backend. Despite its name, LocalContainerService provides no Docker/container or VM backend. Server shutdown follows process signals, not browser disconnection. With the documented user-server deployment, work continues independently of the controlling laptop.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
- Container: The pinned local continuation starts agent executors directly in workspace directories; no product container or VM execution backend exists. Provider sandbox flags are separate.
- Vm: The pinned local continuation starts agent executors directly in workspace directories; no product container or VM execution backend exists. Provider sandbox flags are separate.
- Workspace/session docs and harness sandbox settings; no code-isolation or hostile-code boundary test.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Vibe Kanban local execution ownership
Finding: The local service starts coding-agent executors directly in workspace directories and retains their child processes and exit monitors in the backend. Despite its name, LocalContainerService provides no Docker/container or VM backend. Server shutdown follows process signals, not browser disconnection. With the documented user-server deployment, work continues independently of the controlling laptop.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
Docs describe independent sessions that can run simultaneously and multiple workspaces. No measured concurrency fixture was run.
- Concurrent sessions: Local documentation permits independent running sessions/workspaces; this is documented parallelism, not an observed concurrency measurement.
- Concurrent tasks: Local documentation permits independent running sessions/workspaces; this is documented parallelism, not an observed concurrency measurement.
- Status visibility: Local sidebar/chat docs describe running, idle and needs-attention states. Failure/reconnect consistency was not exercised.
- Sessions/workspaces docs; no simultaneous live agents or quota experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
Coordinator: Yes
Coordinator
Typed value: Yes.
The pinned release ships an explicit orchestrator MCP mode. With --mcp --mode orchestrator configured inside a workspace, the first session is designated as orchestrator and can create or prompt other sessions, list them and inspect execution state/final results. The earlier unreleased orchestrator UI experiment is a separate scope.
- Roles: The first workspace session is the orchestrator; its scoped tools can create/prompt other sessions but refuse prompting the orchestrator itself.
- Results return: get_execution exposes state and a final_message from the delegated execution.
- Orchestration owner: The product ships a named MCP orchestrator mode and designates the first workspace session as orchestrator.
- Activation: Launch the released MCP server with --mcp --mode orchestrator in the workspace directory.
- Invocation: create_session and run_session_prompt delegate work to other coding sessions.
- Requires configuring the shipped MCP orchestrator mode in an existing workspace; this is not an automatically started coordinator UI. Source inspection only, without an end-to-end team run.
-
Released Vibe Kanban orchestrator MCP mode
Finding: The released CLI accepts --mcp --mode orchestrator. That mode designates the first workspace session as orchestrator, scopes its tools to the workspace and offers create_session, run_session_prompt, list_sessions and get_execution with final results. It is an explicitly shipped coordinator role, separate from the earlier unreleased orchestrator UI experiment.
Native issue tracking: No cross-checked
Native issue tracking
Typed value: No.
The vendor-hosted issue board is retired. Released project pages are export-only; local workspaces and sessions are a separate surviving workflow.
- Create: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Edit: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Discuss: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Prioritize: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Label: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Assign: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Search: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Filter: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Archive: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Reopen: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Project epic views: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Idea parking: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Explicit dispatch: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Metadata: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Durable states: Retired vendor-hosted issue/project workflow: the v0.1.44 project route renders an export-only retirement screen. This restriction does not describe local workspace/session controls.
- Shutdown and released project retirement screen; local workspace/session management is separate from the retired issue board.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
packages/web-core/src/pages/kanban/ProjectSunsetPage.tsx
Finding: The accessible replacement page labels projects retired/export-only and links to data export. The restriction applies to project-scoped kanban, issue and workspace flows here, not the separate local Workspaces UI.
Unattended triggers: No
Unattended triggers
Typed value: No.
In the pinned local continuation, work starts through explicit session/workspace requests. The local router, services and MCP expose no product-owned schedule or external-event task starter. Remote PR-review webhook code belongs to the retired hosted service.
- Schedules: No local product scheduler or external-event run starter in the pinned local router, services and MCP; hosted webhook code is outside the continuing service scope.
- Events: No local product scheduler or external-event run starter in the pinned local router, services and MCP; hosted webhook code is outside the continuing service scope.
- Recurring tasks: No local product scheduler or external-event run starter in the pinned local router, services and MCP; hosted webhook code is outside the continuing service scope.
- Bounded source inspection of local server routes, services and MCP; external scripts can call the API but are user integrations.
-
Vibe Kanban local API and trigger inspection
Finding: The surviving local API starts workspace/session work from explicit requests. No local schedule or external-event work starter is registered. Webhook PR reviews exist in the separate retired remote service, not the local continuation.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
Local workspace docs cover branches/worktrees, PR creation, push, merge and rebase/conflict handling. No draft-PR scenario was executed.
- Pull requests: Workspace Git panel documents creating GitHub PRs; authentication and a remote are needed.
- Rebase: Per-repository rebase is documented in the Git panel/command bar.
- Conflicts: Docs show conflict files and continue/abort after manual resolution.
- Git and workspace docs; no repository fixture taken through a draft PR.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
Review interface: Yes cross-checked
Review interface
Typed value: Yes.
Local archive retains conversation notes/files, while diffs and previews remain separate review views.
- Diffs: Workspace changes panel documents code diffs and inline agent feedback.
- Workspace review, preview and chat docs; no retained artifact-gallery or completed-child reopening fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local diff comments are sent with a subsequent message to the agent. The panel also documents displaying submitted GitHub PR review comments, excluding pending reviews. This is documented review behavior, not an observed runtime result or proof of two-way synchronization.
Product license: Apache-2.0: Yes. Apache-2.0 cross-checked
Product license: Apache-2.0
Typed value: Yes. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: MIT: No. Apache-2.0 cross-checked
Product license: MIT
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: GPL-3.0: No. Apache-2.0 cross-checked
Product license: GPL-3.0
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: AGPL-3.0: No. Apache-2.0 cross-checked
Product license: AGPL-3.0
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: Elastic License 2.0: No. Apache-2.0 cross-checked
Product license: Elastic License 2.0
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: Custom terms: No. Apache-2.0 cross-checked
Product license: Custom terms
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Product license: Proprietary: No. Apache-2.0 cross-checked
Product license: Proprietary
Typed value: No. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
Local workspaces continue without vendor sign-in. Remote export code exists, but current export access, full-history portability and restored self-hosted projects are unverified.
- Vendor dependencies: Local workspace startup can skip vendor login. Remote export still requires sign-in and a reachable remote API.
- Account independence: Local workspaces can be used without a Vibe Kanban account; provider authentication is separate.
- Shutdown, export implementation and Docker guide; no authenticated export or import/restore attempt.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Free access: Yes cross-checked
Free access
Typed value: Yes.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Ongoing free: Apache-2.0 local source and no-sign-in workspace path continue. This excludes any promise of free model inference.
- Free scenarios: Local prompt/workspace/review flows are documented without vendor sign-in; no end-to-end free evaluation or two-person shared scenario was run.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
Lifecycle status: Active: No. Sunsetting cross-checked
Lifecycle status: Active
Typed value: No. Sunsetting.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
What would a community edition of Vibe Kanban look like?
Finding: Louis asks for community direction and maintainers. His June 7 reply calls the earlier orchestrator experiment unreleased. This is a discussion, not a committed feature delivery schedule.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
Plan not specified. Surface and scope: Commercial subscriptions and vendor-hosted remote services; v0.1.44 project pages are export-only.. bloop announced its closure and the retirement of vendor-hosted kanban issues, comments, projects and organisations. The announcement explicitly preserves local workspaces.
Lifecycle status: Sunsetting: Yes. Sunsetting cross-checked
Lifecycle status: Sunsetting
Typed value: Yes. Sunsetting.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
What would a community edition of Vibe Kanban look like?
Finding: Louis asks for community direction and maintainers. His June 7 reply calls the earlier orchestrator experiment unreleased. This is a discussion, not a committed feature delivery schedule.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
Plan not specified. Surface and scope: Commercial subscriptions and vendor-hosted remote services; v0.1.44 project pages are export-only.. bloop announced its closure and the retirement of vendor-hosted kanban issues, comments, projects and organisations. The announcement explicitly preserves local workspaces.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
- Byo remote: Settings document running Vibe Kanban on a user server and opening files over SSH. Disconnect/continuation was not tested.
- Client disconnect: The persistent backend owns executor children and exit monitors independently of browser requests; on a separate user server, browser disconnection does not stop the work.
- Local startup, remote SSH and Docker guide; no disconnect/other-device continuation experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
Vibe Kanban local execution ownership
Finding: The local service starts coding-agent executors directly in workspace directories and retains their child processes and exit monitors in the backend. Despite its name, LocalContainerService provides no Docker/container or VM backend. Server shutdown follows process signals, not browser disconnection. With the documented user-server deployment, work continues independently of the controlling laptop.
Open-source license: Yes. Apache-2.0 cross-checked
Open-source license
Typed value: Yes. Apache-2.0.
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Client license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Server license: Pinned repository root is licensed Apache-2.0, subject to component/dependency notices.
- Source visibility: Official public repository contains client and server source.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Desktop os: Release assets provide macOS, Windows and Linux desktop packages; minimum OS versions and installation were not verified.
- Mobile apps: The complete pinned native client build/distribution matrix contains desktop macOS, Windows and Linux packages only; no iOS or Android client is released.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
vibe-kanban:ACC-01: The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
vibe-kanban:ACC-01
The continuing local product provides browser workspaces, a product CLI and Tauri desktop packages. Its complete pinned native build/distribution matrix covers macOS, Windows and Linux, with no released native iOS or Android package. Phone-browser parity and cross-device continuity remain unestablished.
- Client/start docs, desktop release assets and extension docs; no install, mobile handoff or OS-minimum test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
integrations/vibe-kanban-mcp-server
Finding: npx vibe-kanban --mcp exposes local stdio tools. Workspace/session operations are distinct from the documented remote issue tools, which cannot establish current hosted availability.
-
Finding: Official docs name a VS Code extension for VS Code/Cursor/Windsurf with logs, diffs and process monitoring. Post-sunset extension compatibility was not tested.
-
Finding: The released vibe-kanban npm command registers three subcommands: the default launches the local app (browser, or desktop with --desktop), review runs a PR review CLI, and mcp runs the local MCP server.
-
Vibe Kanban complete native client distribution matrix
Finding: The pinned release workflow builds native server/CLI and Tauri client targets for macOS, Windows and Linux, and publishes desktop DMG, AppImage, DEB, MSI and EXE installers. Its complete native build and installer inventory has no iOS or Android phone package. Browser clients are separate.
vibe-kanban:ACC-02: Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested. cross-checked
vibe-kanban:ACC-02
Released source integrates multiple coding-agent adapters; actual mixed-harness execution was not tested.
- Released executor enum and Codex adapter plus agent configuration docs; no two-harness runtime fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/executors/src/executors/mod.rs
Finding: Released adapters enumerate Claude Code, Amp, Gemini, Codex, OpenCode, Cursor Agent, Qwen Code, Copilot and Droid. Agent settings/MCP support vary by adapter.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
vibe-kanban:ACC-03: Local Codex uses native login or API keys and detects custom configuration directories. cross-checked
vibe-kanban:ACC-03
Local Codex uses native login or API keys and detects custom configuration directories.
- Codex login docs and shutdown notice; current provider entitlements, account switching and local-model routes were not verified.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Vibe Kanban documents Codex authentication through a ChatGPT plan or OPENAI_API_KEY. This is an integration route, not verification of every current provider plan, allowance or restriction.
-
Vibe Kanban Login; Custom configuration
Finding: Local Codex setup explicitly uses provider login with ChatGPT plan or OPENAI_API_KEY. CODEX_HOME custom configuration/session path is detected. Current provider plan eligibility is not independently established.
vibe-kanban:ACC-04: The documented local flow is npx, agent authentication and repository selection. Install time, repository variants and remote onboarding were not tested. cross-checked
vibe-kanban:ACC-04
The documented local flow is npx, agent authentication and repository selection. Install time, repository variants and remote onboarding were not tested.
- Getting-started, workspace creation and Docker guide; no fresh install, repository-variant or VPS onboarding scenario.
- Documentation/source inspection only. No product runtime scenario was executed.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
workspaces/creating-workspaces
Finding: Documentation describes selecting repos on disk or initializing a new Git repo, choosing target branches, starting with a prompt and adding notes. Old project dropdown instructions need reconciliation with the retired project UI.
-
Finding: Official guide describes a Linux server, Docker Compose, database, domain/TLS and OAuth or a shared bootstrap admin credential, with separate optional relay setup. It does not override v0.1.44 export-only project routes or prove operational deployment.
vibe-kanban:ACC-05: Local MCP provides workspace start, session creation/follow-up and execution inspection. Remote issue tools in the same interface depend on the retired issue service. cross-checked
vibe-kanban:ACC-05
Local MCP provides workspace start, session creation/follow-up and execution inspection. Remote issue tools in the same interface depend on the retired issue service.
- Local MCP documentation and released tool implementations; no API/SDK stability contract or authenticated calls tested.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/mcp/src/task_server/tools/sessions.rs
Finding: MCP tools call local /api/sessions and execution-process endpoints to create/list sessions, submit follow-up turns and inspect executions. They check workspace scope. No calls were executed in this research.
-
crates/mcp/src/task_server/tools/task_attempts.rs
Finding: start_workspace sends a prompt and repository configuration to /api/workspaces/start. Linking an issue is optional and uses remote issue endpoints when requested. This establishes a local programmatic start path without a hosted issue.
-
integrations/vibe-kanban-mcp-server
Finding: npx vibe-kanban --mcp exposes local stdio tools. Workspace/session operations are distinct from the documented remote issue tools, which cannot establish current hosted availability.
-
Finding: The released vibe-kanban npm command registers three subcommands: the default launches the local app (browser, or desktop with --desktop), review runs a PR review CLI, and mcp runs the local MCP server.
vibe-kanban:ACC-06: Vibe Kanban manages per-harness MCP configuration; connections and permissions execute through the selected harness. cross-checked
vibe-kanban:ACC-06
Vibe Kanban manages per-harness MCP configuration; connections and permissions execute through the selected harness.
- MCP client configuration and agent variants; no installed plugins, instruction-import or external-tool boundary exercise.
- Documentation/source inspection only. No product runtime scenario was executed.
-
integrations/mcp-server-configuration
Finding: Settings edit the selected harness global MCP configuration and offer presets/custom servers. Configuration persists outside Vibe Kanban; no external tool call or permission-boundary test was performed.
vibe-kanban:ACC-07: The desktop distribution uses Tauri webviews and a web UI. This is not evidence of native platform widgets. cross-checked
vibe-kanban:ACC-07
The desktop distribution uses Tauri webviews and a web UI. This is not evidence of native platform widgets.
- Tauri configuration and desktop startup; no mobile implementation located in this pass.
- Documentation/source inspection only. No product runtime scenario was executed.
-
crates/tauri-app/tauri.conf.json
Finding: Release desktop client uses Tauri configuration version 0.1.44 and all bundle targets. The desktop UI is a webview, not evidence of platform-native widgets.
-
Finding: Desktop startup launches the web UI in a Tauri webview, including a local-server URL. This connects the shipped Tauri configuration to the desktop window.
vibe-kanban:PLAN-01: Local prompt-driven workspaces continue independently of the retired hosted issue tracker. cross-checked
vibe-kanban:PLAN-01
Local prompt-driven workspaces continue independently of the retired hosted issue tracker.
- Workspace creation, MCP and retired project routes; no external tracker import or synchronization fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
crates/mcp/src/task_server/tools/task_attempts.rs
Finding: start_workspace sends a prompt and repository configuration to /api/workspaces/start. Linking an issue is optional and uses remote issue endpoints when requested. This establishes a local programmatic start path without a hosted issue.
-
crates/mcp/src/task_server/tools/remote_issues.rs
Finding: Issue tools target /api/remote/issues and related remote routes. Their continued presence in source is not proof that the retired vendor issue service works or that issues moved into the local workspace database.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
vibe-kanban:PLAN-02: Local plan approval and workspace notes coexist with explicit archive retention. Versioned task-plan editing remains unestablished.
vibe-kanban:PLAN-02
Local plan approval and workspace notes coexist with explicit archive retention. Versioned task-plan editing remains unestablished.
- Chat planning/approval and workspace notes docs; durable acceptance criteria and revision history not exercised.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
workspaces/creating-workspaces
Finding: Documentation describes selecting repos on disk or initializing a new Git repo, choosing target branches, starting with a prompt and adding notes. Old project dropdown instructions need reconciliation with the retired project UI.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
vibe-kanban:PLAN-04: Local sessions share files and reusable prompts while keeping conversations separate. cross-checked
vibe-kanban:PLAN-04
Local sessions share files and reusable prompts while keeping conversations separate.
- Session separation, prompt tags and agent settings; managed cross-session memory/retrieval not demonstrated.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
Vibe Kanban docs/workspaces/sessions.mdx
Finding: Local sessions are separate processes with separate conversation histories but share workspace files/Git. Switching does not interrupt running agents. New sessions inherit no earlier conversation. Context gauge and complete per-session history are documented; no crash/restart fixture.
vibe-kanban:PLAN-05: Local chat accepts file mentions and images; architecture-aware retrieval and enforcement remain untested. cross-checked
vibe-kanban:PLAN-05
Local chat accepts file mentions and images; architecture-aware retrieval and enforcement remain untested.
- Chat file mentions and preview component context; architecture conflict/retrieval scenario not run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
vibe-kanban:PLAN-06: The vendor-hosted issue board is retired. Released project pages are export-only; local workspaces and sessions are a separate surviving workflow. cross-checked
vibe-kanban:PLAN-06
The vendor-hosted issue board is retired. Released project pages are export-only; local workspaces and sessions are a separate surviving workflow.
- Shutdown and released project retirement screen; local workspace/session management is separate from the retired issue board.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
packages/web-core/src/pages/kanban/ProjectSunsetPage.tsx
Finding: The accessible replacement page labels projects retired/export-only and links to data export. The restriction applies to project-scoped kanban, issue and workspace flows here, not the separate local Workspaces UI.
vibe-kanban:COORD-01: Docs describe independent sessions that can run simultaneously and multiple workspaces. No measured concurrency fixture was run. cross-checked
vibe-kanban:COORD-01
Docs describe independent sessions that can run simultaneously and multiple workspaces. No measured concurrency fixture was run.
- Sessions/workspaces docs; no simultaneous live agents or quota experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
vibe-kanban:COORD-03: The pinned release ships an explicit orchestrator MCP mode. With --mcp --mode orchestrator configured inside a workspace, the first session is designated as orchestrator and can create or prompt other sessions, list them and inspect execution state/final results. The earlier unreleased orchestrator UI experiment is a separate scope.
vibe-kanban:COORD-03
The pinned release ships an explicit orchestrator MCP mode. With --mcp --mode orchestrator configured inside a workspace, the first session is designated as orchestrator and can create or prompt other sessions, list them and inspect execution state/final results. The earlier unreleased orchestrator UI experiment is a separate scope.
- Requires configuring the shipped MCP orchestrator mode in an existing workspace; this is not an automatically started coordinator UI. Source inspection only, without an end-to-end team run.
-
What would a community edition of Vibe Kanban look like?
Finding: Louis asks for community direction and maintainers. His June 7 reply calls the earlier orchestrator experiment unreleased. This is a discussion, not a committed feature delivery schedule.
-
crates/mcp/src/task_server/tools/sessions.rs
Finding: MCP tools call local /api/sessions and execution-process endpoints to create/list sessions, submit follow-up turns and inspect executions. They check workspace scope. No calls were executed in this research.
-
Released Vibe Kanban orchestrator MCP mode
Finding: The released CLI accepts --mcp --mode orchestrator. That mode designates the first workspace session as orchestrator, scopes its tools to the workspace and offers create_session, run_session_prompt, list_sessions and get_execution with final results. It is an explicitly shipped coordinator role, separate from the earlier unreleased orchestrator UI experiment.
vibe-kanban:COORD-04: In the pinned local continuation, work starts through explicit session/workspace requests. The local router, services and MCP expose no product-owned schedule or external-event task starter. Remote PR-review webhook code belongs to the retired hosted service.
vibe-kanban:COORD-04
In the pinned local continuation, work starts through explicit session/workspace requests. The local router, services and MCP expose no product-owned schedule or external-event task starter. Remote PR-review webhook code belongs to the retired hosted service.
- Bounded source inspection of local server routes, services and MCP; external scripts can call the API but are user integrations.
-
Vibe Kanban local API and trigger inspection
Finding: The surviving local API starts workspace/session work from explicit requests. No local schedule or external-event work starter is registered. Webhook PR reviews exist in the separate retired remote service, not the local continuation.
vibe-kanban:COORD-05: Local chat provides stop, queue/retry and history controls.
vibe-kanban:COORD-05
Local chat provides stop, queue/retry and history controls.
- Chat stop/queue/approval and notification docs; no running amendment, terminal parity or stop-process test.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
Vibe Kanban docs/workspaces/sessions.mdx
Finding: Local sessions are separate processes with separate conversation histories but share workspace files/Git. Switching does not interrupt running agents. New sessions inherit no earlier conversation. Context gauge and complete per-session history are documented; no crash/restart fixture.
vibe-kanban:COORD-06: The local workspace list supplies session status context, but a 12-state fleet/epic fixture was not evaluated. cross-checked
vibe-kanban:COORD-06
The local workspace list supplies session status context, but a 12-state fleet/epic fixture was not evaluated.
- Workspace overview and screenshot; no disclosed 12-state fleet fixture or epic navigation test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
vibe-kanban:COORD-07: Local users can try a different approach by duplicating a workspace, which keeps the repository/branch configuration but starts a fresh conversation, and can choose agent profiles per run.
vibe-kanban:COORD-07
Local users can try a different approach by duplicating a workspace, which keeps the repository/branch configuration but starts a fresh conversation, and can choose agent profiles per run.
- Agent profiles and MCP source; no growing epic or coordinator/two-reviewer execution fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
vibe-kanban:RUN-01: Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
vibe-kanban:RUN-01
Local agent execution continues. BYO hosting is documented, but laptop-independent operation and current vendor remote access were not tested.
- Local startup, remote SSH and Docker guide; no disconnect/other-device continuation experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
Finding: Official guide describes a Linux server, Docker Compose, database, domain/TLS and OAuth or a shared bootstrap admin credential, with separate optional relay setup. It does not override v0.1.44 export-only project routes or prove operational deployment.
-
Vibe Kanban local execution ownership
Finding: The local service starts coding-agent executors directly in workspace directories and retains their child processes and exit monitors in the backend. Despite its name, LocalContainerService provides no Docker/container or VM backend. Server shutdown follows process signals, not browser disconnection. With the documented user-server deployment, work continues independently of the controlling laptop.
vibe-kanban:RUN-02: Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
vibe-kanban:RUN-02
Branches/worktrees separate workspace files; sessions within one workspace share files/Git. Security containment remains unestablished.
- Workspace/session docs and harness sandbox settings; no code-isolation or hostile-code boundary test.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
-
Vibe Kanban docs/workspaces/sessions.mdx
Finding: Local sessions are separate processes with separate conversation histories but share workspace files/Git. Switching does not interrupt running agents. New sessions inherit no earlier conversation. Context gauge and complete per-session history are documented; no crash/restart fixture.
-
Vibe Kanban local execution ownership
Finding: The local service starts coding-agent executors directly in workspace directories and retains their child processes and exit monitors in the backend. Despite its name, LocalContainerService provides no Docker/container or VM backend. Server shutdown follows process signals, not browser disconnection. With the documented user-server deployment, work continues independently of the controlling laptop.
vibe-kanban:RUN-03: Local archive preserves history/files and missing worktrees rebuild from last commit with uncommitted changes lost.
vibe-kanban:RUN-03
Local archive preserves history/files and missing worktrees rebuild from last commit with uncommitted changes lost.
- Session history, chat retry and release notes; no disconnect, crash, restart or compute replacement fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
crates/executors/src/executors/codex.rs
Finding: Codex executor starts an app-server client, checks authentication and starts/forks a thread for session work. It integrates structured session operations rather than only opening a terminal.
-
Finding: Sessions are independent processes that may run simultaneously and share workspace files, but new sessions do not inherit conversation history.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
vibe-kanban:RUN-04: Repository setup/dev/cleanup scripts prepare environments with user-defined lifecycle behavior. cross-checked
vibe-kanban:RUN-04
Repository setup/dev/cleanup scripts prepare environments with user-defined lifecycle behavior.
- Repository scripts and browser testing docs; no clean-host or two-service fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
settings/projects-repositories
Finding: Repository scripts prepare dependencies, launch a dev server and clean up resources. They are user-supplied commands; automatic collision handling and resource scheduling are not established.
-
Finding: Preview uses a configured dev server, detects its URL, supports viewport modes and component context selection, and offers embedded devtools. Port conflicts require the user to stop a process or change configuration.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
-
Vibe Kanban docs/settings/projects-repositories.mdx
Finding: Setup runs once at workspace start before agent, not per message. Cleanup runs when workspace closes and may stop services or remove artifacts. Dev server must print URL for preview detection. These are user-supplied scripts, not observed automated repair.
vibe-kanban:RUN-05: Approval timeouts are documented; enforced time, token and spend budgets remain unverified. cross-checked
vibe-kanban:RUN-05
Approval timeouts are documented; enforced time, token and spend budgets remain unverified.
- Chat timeout guidance and agent configuration; no controlled failure, time/token/spend enforcement experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
vibe-kanban:RUN-06: Local logs include expandable tool command/search results and execution states. cross-checked
vibe-kanban:RUN-06
Local logs include expandable tool command/search results and execution states.
- Chat, preview and session docs; no induced failure/reconnect consistency or measured performance fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Preview uses a configured dev server, detects its URL, supports viewport modes and component context selection, and offers embedded devtools. Port conflicts require the user to stop a process or change configuration.
-
Vibe Kanban docs/workspaces/chat-interface.mdx
Finding: Plan cards expand specific files/changes and accept approve/request changes. Editing/retry replaces subsequent messages on the conversation branch. Queued follow-ups wait for agent. Tool panels expose command and search results; no complete operational reliability fixture.
vibe-kanban:RUN-07: The documented context gauge is not a verified cost ledger. Per-task spend, provider reconciliation and compute billing remain unknown. cross-checked
vibe-kanban:RUN-07
The documented context gauge is not a verified cost ledger. Per-task spend, provider reconciliation and compute billing remain unknown.
- Chat context gauge and provider login docs; no per-task cost ledger or provider billing reconciliation accessed.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
vibe-kanban:RUN-08: Resource limits, check reuse and fleet backpressure remain unknown. Parallel work and a Stop control do not establish a resource scheduler. cross-checked
vibe-kanban:RUN-08
Resource limits, check reuse and fleet backpressure remain unknown. Parallel work and a Stop control do not establish a resource scheduler.
- Parallel-session and script docs; no resource scheduler, fairness or check-deduplication fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
vibe-kanban:TEAM-01: The shutdown announcement retired vendor-hosted issue discussion/comments. This row scopes that hosted service; local inline diff feedback is covered separately in SHIP-03. cross-checked
vibe-kanban:TEAM-01
The shutdown announcement retired vendor-hosted issue discussion/comments. This row scopes that hosted service; local inline diff feedback is covered separately in SHIP-03.
- Shutdown and historical Cloud docs; no two-user local co-steering experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
vibe-kanban:TEAM-02: The vendor-hosted organisation/project service was named for retirement. This finding does not establish limitations of independently self-hosted components. cross-checked
vibe-kanban:TEAM-02
The vendor-hosted organisation/project service was named for retirement. This finding does not establish limitations of independently self-hosted components.
- Shutdown, project route and self-host auth guide; no current team RBAC/SSO/revocation test.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
vibe-kanban:TEAM-03: Harness-specific plan/permission controls appear in local configuration. End-to-end command/network/secret enforcement and approver identity are untested. cross-checked
vibe-kanban:TEAM-03
Harness-specific plan/permission controls appear in local configuration. End-to-end command/network/secret enforcement and approver identity are untested.
- Chat approvals, agent profiles and Codex adapter; no permission enforcement or revocation scenario.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Agent variants configure model/effort/planning and harness-specific permission modes. Codex sandbox modes are provider controls, not a uniform Vibe Kanban security boundary.
vibe-kanban:TEAM-04: Local conversation history persists across session switches and archive, but message retry can replace later visible history.
vibe-kanban:TEAM-04
Local conversation history persists across session switches and archive, but message retry can replace later visible history.
- Session histories and export implementation; no immutable cross-user audit trail or retention policy verified.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
-
Vibe Kanban docs/workspaces/sessions.mdx
Finding: Local sessions are separate processes with separate conversation histories but share workspace files/Git. Switching does not interrupt running agents. New sessions inherit no earlier conversation. Context gauge and complete per-session history are documented; no crash/restart fixture.
vibe-kanban:TEAM-05: Local review UI provides diff modes, filtered files and submitted GitHub comments. cross-checked
vibe-kanban:TEAM-05
Local review UI provides diff modes, filtered files and submitted GitHub comments.
- Diff/chat/Git documentation and official screenshot; no reviewer effort, missed-evidence or narrow-screen scenario.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
-
Finding: Local diff comments are sent with a subsequent message to the agent. The panel also documents displaying submitted GitHub PR review comments, excluding pending reviews. This is documented review behavior, not an observed runtime result or proof of two-way synchronization.
-
Vibe Kanban docs/workspaces/changes.mdx
Finding: Local diffs support unified/side-by-side, filename search, wrap/whitespace and inline feedback. Submitted GitHub review comments can appear inline; pending unsubmitted reviews do not. Feedback reaches agent in later messages.
vibe-kanban:SHIP-01: Local archive retains conversation notes/files, while diffs and previews remain separate review views. cross-checked
vibe-kanban:SHIP-01
Local archive retains conversation notes/files, while diffs and previews remain separate review views.
- Workspace review, preview and chat docs; no retained artifact-gallery or completed-child reopening fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Local chat documents queue, stop, edit/retry, plan approval, image attachments, file mentions and visible errors. Approval requests can time out. The token gauge is context usage, not a billing total.
-
Finding: Preview uses a configured dev server, detects its URL, supports viewport modes and component context selection, and offers embedded devtools. Port conflicts require the user to stop a process or change configuration.
-
Finding: Local diff comments are sent with a subsequent message to the agent. The panel also documents displaying submitted GitHub PR review comments, excluding pending reviews. This is documented review behavior, not an observed runtime result or proof of two-way synchronization.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
vibe-kanban:SHIP-02: Repository scripts can run checks; docs advise review and CI before merge. Required/enforced checks and spec gates were not established. cross-checked
vibe-kanban:SHIP-02
Repository scripts can run checks; docs advise review and CI before merge. Required/enforced checks and spec gates were not established.
- Repository scripts and Git pre-merge guidance; no failing-check or spec-conflict gating experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
-
settings/projects-repositories
Finding: Repository scripts prepare dependencies, launch a dev server and clean up resources. They are user-supplied commands; automatic collision handling and resource scheduling are not established.
vibe-kanban:SHIP-03: Local workspace docs cover branches/worktrees, PR creation, push, merge and rebase/conflict handling. No draft-PR scenario was executed. cross-checked
vibe-kanban:SHIP-03
Local workspace docs cover branches/worktrees, PR creation, push, merge and rebase/conflict handling. No draft-PR scenario was executed.
- Git and workspace docs; no repository fixture taken through a draft PR.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local workspaces combine repositories, sessions, diffs and a preview. Workspaces use branches/worktrees; sessions are separate conversations. Documentation does not establish hostile-code containment.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
-
Finding: Local diff comments are sent with a subsequent message to the agent. The panel also documents displaying submitted GitHub PR review comments, excluding pending reviews. This is documented review behavior, not an observed runtime result or proof of two-way synchronization.
vibe-kanban:SHIP-04: Local merge is documented. Exact-revision approval, production deployment and authority enforcement remain unverified.
vibe-kanban:SHIP-04
Local merge is documented. Exact-revision approval, production deployment and authority enforcement remain unverified.
- Git merge docs and harness permissions; no exact-revision authority or deploy test.
- Documentation/source inspection only. No product runtime scenario was executed.
- First-party docs disagree on the Merge direction; the target-branch direction rests on released source, not a run.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
-
crates/server/src/routes/workspaces/git.rs
Finding: The released workspace merge route passes the repository path, workspace worktree, workspace branch and target branch to merge_changes to merge the workspace branch into its target branch; it refuses remote target branches and workspaces with an open PR, then archives unpinned workspaces. The merge_changes implementation was not read and the route was not run. The Git operations page separately describes a Merge action pulling the target into the working branch.
vibe-kanban:SHIP-05: Git PR workflow is documented, but completion-to-revision evidence, rollback and stale-approval invalidation were not tested. cross-checked
vibe-kanban:SHIP-05
Git PR workflow is documented, but completion-to-revision evidence, rollback and stale-approval invalidation were not tested.
- Git workflow and export source; no delivered revision, rollback or stale-approval experiment.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Workspace UI documents PR creation, local merge, push and per-repository rebase/conflict actions. CI and code review before merging are user guidance, not evidence of enforced gates.
vibe-kanban:SHIP-06: Single-workspace review is documented; six-output batch review, dependency queues and exact-revision approvals remain unverified. cross-checked
vibe-kanban:SHIP-06
Single-workspace review is documented; six-output batch review, dependency queues and exact-revision approvals remain unverified.
- Workspace list/diffs and Git docs; no six-output batch review or dependency-aware merge-queue fixture.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Local diff comments are sent with a subsequent message to the agent. The panel also documents displaying submitted GitHub PR review comments, excluding pending reviews. This is documented review behavior, not an observed runtime result or proof of two-way synchronization.
vibe-kanban:OWN-01: Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately. cross-checked
vibe-kanban:OWN-01
Pinned repository distribution has an Apache-2.0 license. Retired hosted functionality and surviving local source must be scoped separately.
- Pinned root Apache-2.0 license and source tree; hosted implementation parity not established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
packages/web-core/src/pages/kanban/ProjectSunsetPage.tsx
Finding: The accessible replacement page labels projects retired/export-only and links to data export. The restriction applies to project-scoped kanban, issue and workspace flows here, not the separate local Workspaces UI.
-
crates/remote/src/routes/export.rs
Finding: Authenticated export writes a ZIP containing issues, projects and users CSVs plus optional attachment manifest/files. Issue columns include status, priority, assignees and parent issue. This is not a demonstrated full-history import/restore path.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
vibe-kanban:OWN-02: Local workspaces continue without vendor sign-in. Remote export code exists, but current export access, full-history portability and restored self-hosted projects are unverified. cross-checked
vibe-kanban:OWN-02
Local workspaces continue without vendor sign-in. Remote export code exists, but current export access, full-history portability and restored self-hosted projects are unverified.
- Shutdown, export implementation and Docker guide; no authenticated export or import/restore attempt.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
packages/web-core/src/pages/export/ExportPage.tsx
Finding: Export UI requires sign-in, lists organisations/projects and POSTs /v1/export. It offers CSV and optional attachments; source existence does not establish current hosted download access.
-
crates/remote/src/routes/export.rs
Finding: Authenticated export writes a ZIP containing issues, projects and users CSVs plus optional attachment manifest/files. Issue columns include status, priority, assignees and parent issue. This is not a demonstrated full-history import/restore path.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Vibe Kanban documents Codex authentication through a ChatGPT plan or OPENAI_API_KEY. This is an integration route, not verification of every current provider plan, allowance or restriction.
-
Finding: Official guide describes a Linux server, Docker Compose, database, domain/TLS and OAuth or a shared bootstrap admin credential, with separate optional relay setup. It does not override v0.1.44 export-only project routes or prove operational deployment.
vibe-kanban:OWN-03: Local telemetry has a settings toggle and a released source default of enabled, but a successful sign-in turns analytics back on, so the opt-out does not survive a login. Workspace deletion is documented separately. cross-checked
vibe-kanban:OWN-03
Local telemetry has a settings toggle and a released source default of enabled, but a successful sign-in turns analytics back on, so the opt-out does not survive a login. Workspace deletion is documented separately.
- Current config source and settings telemetry docs; no network capture, first-run consent or provider policy audit.
- Documentation/source inspection only. No product runtime scenario was executed.
- Source at 4deb7ec re-enables analytics after a successful sign-in, confirming issue #3482; the opt-out holds only while signed out.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
crates/services/src/services/config/mod.rs
Finding: The current released config type is versions::v8::Config; a missing config loads its defaults.
-
crates/services/src/services/config/versions/v8.rs
Finding: analytics_enabled defaults to true, and migration maps an unset old value to true. This records a configuration default, not observed network traffic or first-run consent.
-
Finding: Settings document sound/browser notifications, telemetry toggle, reusable prompt tags and editor SSH links when the user hosts Vibe Kanban on a remote server.
-
Vibe Kanban docs/workspaces/managing-workspaces.mdx
Finding: Local archive keeps history/sessions/notes/worktree; deletion removes workspace data/worktree but leaves branch and commits. Missing manually deleted worktree rebuilds from last commit and loses uncommitted changes. Startup cleans orphan worktrees. Duplicate starts fresh conversation with same repo/branch configuration.
-
Vibe Kanban backend analytics gate
Finding: Backend event tracking only fires when the config flag analytics_enabled is true and an analytics client is configured; turning the flag off stops backend tracking.
-
Vibe Kanban web analytics opt-out
Finding: The local web UI opts PostHog capture in when analytics_enabled is true and calls opt_out_capturing when it is false.
-
Vibe Kanban login re-enables analytics
Finding: After a successful Vibe Kanban sign-in, the server sets analytics_enabled back to true if it was off and saves the config, so the opt-out does not survive a login.
-
Finding: General settings documentation describes a control to enable or disable telemetry collection.
vibe-kanban:OWN-06: Commercial services were sunset while the local open-source project continues. The latest listed release is v0.1.44, followed by a community direction discussion. cross-checked
vibe-kanban:OWN-06
Commercial services were sunset while the local open-source project continues. The latest listed release is v0.1.44, followed by a community direction discussion.
- Shutdown, releases, repo issues and June community discussion; no operational SLA or installation success established.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: Latest release listed at retrieval is v0.1.44, published April 24, 2026. It includes export-only project routes, Claude Code 2.1.119 and Codex 0.124.0 updates. Release assets include desktop packages; this is release evidence, not a successful installation.
-
What would a community edition of Vibe Kanban look like?
Finding: Louis asks for community direction and maintainers. His June 7 reply calls the earlier orchestrator experiment unreleased. This is a discussion, not a committed feature delivery schedule.
-
packages/web-core/src/pages/kanban/ProjectKanban.tsx
Finding: LocalProjectKanban and RemoteProjectKanbanShell both call this shared page. It returns ProjectSunsetPage instead of the board, with no alternate branch for a self-hosted API. This links the released project route to the retired UI.
-
packages/web-core/src/pages/kanban/ProjectSunsetPage.tsx
Finding: The accessible replacement page labels projects retired/export-only and links to data export. The restriction applies to project-scoped kanban, issue and workspace flows here, not the separate local Workspaces UI.
-
packages/web-core/src/pages/export/ExportPage.tsx
Finding: Export UI requires sign-in, lists organisations/projects and POSTs /v1/export. It offers CSV and optional attachments; source existence does not establish current hosted download access.
vibe-kanban:OWN-08: The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated. cross-checked
vibe-kanban:OWN-08
The local open-source project remains available without vendor sign-in. Agent subscriptions/API use and compute are separate; free team workflows were not demonstrated.
- Open-source license, no-sign-in workspace docs and shutdown; no free end-to-end or two-person evaluation run.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.
-
Finding: The pinned repository root carries Apache-2.0. This covers the repository distribution subject to component/dependency notices; it does not prove hosted parity.
-
Finding: npx launches a browser UI; sign-in can be skipped for workspaces, while board/issues/team features require it. Workspaces can start without an issue and later merge locally or create a GitHub PR. Hosted-board steps are historical after the sunset.
-
Finding: Official guide describes a Linux server, Docker Compose, database, domain/TLS and OAuth or a shared bootstrap admin credential, with separate optional relay setup. It does not override v0.1.44 export-only project routes or prove operational deployment.
vibe-kanban:OWN-09: Commercial subscriptions were terminated, so historical Vibe Kanban tariffs do not describe a current service. Provider and user-hosting cost transparency remains unverified. cross-checked
vibe-kanban:OWN-09
Commercial subscriptions were terminated, so historical Vibe Kanban tariffs do not describe a current service. Provider and user-hosting cost transparency remains unverified.
- Shutdown and Codex authentication docs; no current Vibe Kanban commercial quote or provider usage tariff comparison.
- Documentation/source inspection only. No product runtime scenario was executed.
-
Finding: bloop announced its closure and an open-source, community-maintained continuation. Subscriptions were terminated and recent invoices refunded. Remote services had a 30-day transition window, covering kanban issues, comments, projects and organisations. Local workspaces would continue. No exact service-end date is stated.