50 of 51 criteria have a sourced finding; 41 were also cross-checked by a second agent. Every comparison that includes vibe-tree links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Electron desktop app (macOS arm64/x64, Windows x64, Linux x64), a React PWA served by the standalone server (usable from phone browsers), a `vibetree` CLI and the server API. No native iOS/Android app or editor extension. A Windows launch crash is reported (issue 136).
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server), vibetree command-line client (@vibetree/cli), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
desktop_os: Installers ship for macOS (dmg/zip arm64 and x64), Windows x64 (NSIS) and Linux x64 (AppImage, deb); a user reports the Windows v0.2.0 installer crashes at launch (open issue 136, unconfirmed) and ma…
mobile_apps: No native iOS/Android app in the release asset list or source; the phone client is the PWA.
editor_extensions: No editor extension; the desktop app can open a worktree in VS Code or Cursor.
task_actions: Create worktrees, start and type into agent terminals, review diffs and send a note as the next prompt, remove worktrees; approvals happen by typing into the agent terminal; no dedicated approve butt…
notifications: Desktop native notifications on completion/question; web client plays a sound ding and shows agent-state badges; no push notifications to phones.
9 atomic answers
Desktop os [partial] Installers ship for macOS (dmg/zip arm64 and x64), Windows x64 (NSIS) and Linux x64 (AppImage, deb); a user reports the Windows v0.2.0 installer crashes at launch (open issue 136, unconfirmed) and macOS/Windows builds are not signed/notarized. Sources: vibe-tree:builder, vibe-tree:release, vibe-tree:site, vibe-tree:issue136.
Mobile apps [unsupported] No native iOS/Android app in the release asset list or source; the phone client is the PWA. Sources: vibe-tree:release, vibe-tree:srch-clients.
Browser [supported] Standalone server serves a React web app on port 3002 (or 3000 via Docker). Sources: vibe-tree:readme, vibe-tree:docker.
Mobile browser [supported] Installable PWA with QR pairing for phones; web app supports worktree terminals, diffs and fleet status. Sources: vibe-tree:readme, vibe-tree:site, vibe-tree:authsvc.
Cli [supported] `vibetree worktrees|status|run` talks to a running server. Sources: vibe-tree:cli.
Editor extensions [unsupported] No editor extension; the desktop app can open a worktree in VS Code or Cursor. Sources: vibe-tree:ide, vibe-tree:srch-clients.
Task actions [partial] Create worktrees, start and type into agent terminals, review diffs and send a note as the next prompt, remove worktrees; approvals happen by typing into the agent terminal; no dedicated approve button. Sources: vibe-tree:readme, vibe-tree:ws, vibe-tree:release.
Notifications [partial] Desktop native notifications on completion/question; web client plays a sound ding and shows agent-state badges; no push notifications to phones. Sources: vibe-tree:notif, vibe-tree:site, vibe-tree:release.
Cross device continuity [supported] Terminal sessions live on the server and survive reloads and disconnects; any paired device reaches the same sessions. Sources: vibe-tree:arch, vibe-tree:release.
Harness-agnostic terminal launcher: any CLI agent (Claude Code, Codex CLI, Gemini CLI, Aider, opencode named by the project) runs in a PTY per worktree. No model providers or API are embedded; activity detection is tuned to Claude Code prompts.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), vibetree command-line client (@vibetree/cli) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
model_providers: No model provider integration; models are whatever the agent CLI uses.
session_integration: Launches the agent command in a PTY and watches terminal output; no harness API control.
5 atomic answers
Harnesses [supported] README and site name Claude Code, OpenAI Codex CLI, Gemini CLI, Aider and opencode as working in the terminal, plus any other terminal program. Sources: vibe-tree:readme, vibe-tree:site.
Model providers [unsupported] No model provider integration; models are whatever the agent CLI uses. Sources: vibe-tree:srch-mcp.
Custom adapters [supported] A per-project `agentCommand` in `.vibetree/config.json` (or `--agent`) launches any command. Sources: vibe-tree:projcfg, vibe-tree:cli.
Session integration [partial] Launches the agent command in a PTY and watches terminal output; no harness API control. Sources: vibe-tree:tracker, vibe-tree:activity.
Mixed harness operation [supported] Each worktree and terminal runs its own command, so different agent CLIs can run side by side; no product-level harness orchestration. Sources: vibe-tree:readme, vibe-tree:projcfg.
Uses whatever login or key the launched agent CLI has; the project states users bring their own agent subscriptions. No vendor credits, account or key handling in VibeTree.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
api_accounts: Agent CLIs can use API keys from the shell environment; VibeTree has no key handling.
vendor_credits: No vendor credits exist; VibeTree is free.
local_models: Possible only through an agent CLI that supports local models; none is integrated.
account_switching: No account switcher; accounts belong to each agent CLI.
provider_restrictions: Provider terms on automated terminal use of subscriptions are not documented by VibeTree and depend on each vendor.
7 atomic answers
Agent subscriptions [supported] Site: "You bring your own agent subscriptions"; agents run as native terminal programs with their own login. Sources: vibe-tree:site, vibe-tree:readme.
Api accounts [partial] Agent CLIs can use API keys from the shell environment; VibeTree has no key handling. Sources: vibe-tree:srch-mcp.
Local models [partial] Possible only through an agent CLI that supports local models; none is integrated. Sources: vibe-tree:srch-mcp.
Account switching [unsupported] No account switcher; accounts belong to each agent CLI. Sources: vibe-tree:srch-mcp.
Vendor account requirement [supported] No VibeTree account required. Sources: vibe-tree:site.
Provider restrictions [unknown] Provider terms on automated terminal use of subscriptions are not documented by VibeTree and depend on each vendor. Sources: vibe-tree:site.
Install the desktop app (or run the server), open a Git repo, create a worktree and launch an agent command in its terminal. Requires an existing Git repository; no remote or account needed. Docker VM deployment is documented.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
no_git: Projects must be Git repositories (project validation; worktree creation uses `git worktree add`).
hosted_git: Works with any repository checkout, but no GitHub/GitLab integration exists.
prerequisite_guidance: README lists install options and the agent CLI the user must install separately; onboarding checks required tools only as an open issue.
managed_cloud_setup: No managed cloud; the site states there is no cloud component.
byo_vps_onboarding: DOCKER.md documents `npm run deploy` for a VM/EC2 deployment but there is no installer or onboarding flow.
7 atomic answers
First task setup [supported] Download app, open project, create worktree, click the agent preset or type the agent command; onboarding dialog guides desktop first run. Sources: vibe-tree:readme, vibe-tree:release.
No git [unsupported] Projects must be Git repositories (project validation; worktree creation uses `git worktree add`). Sources: vibe-tree:git.
Local git without remote [supported] Worktree add/remove and diff are local Git commands; no remote needed. Sources: vibe-tree:git.
Hosted git [partial] Works with any repository checkout, but no GitHub/GitLab integration exists. Sources: vibe-tree:srch-pr.
Prerequisite guidance [partial] README lists install options and the agent CLI the user must install separately; onboarding checks required tools only as an open issue. Sources: vibe-tree:readme, vibe-tree:site.
Managed cloud setup [unsupported] No managed cloud; the site states there is no cloud component. Sources: vibe-tree:site.
Byo vps onboarding [partial] DOCKER.md documents `npm run deploy` for a VM/EC2 deployment but there is no installer or onboarding flow. Sources: vibe-tree:docker.
The `vibetree` CLI and the server REST/WebSocket API (the same API the web app uses) can create and remove worktrees, list sessions and agent states, start shells and type into them; there is no SDK, MCP server or webhooks.
Scope
Surfaces: vibetree command-line client (@vibetree/cli), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
sdk: `@vibetree/core` WebSocketAdapter is shared by clients but no documented SDK.
VibeTree has no MCP, plugin or tool layer of its own; agent CLIs bring their own MCP and plugin support. It offers lifecycle hooks, an agent preset and an IDE launcher.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
mcp_client: No MCP client in VibeTree; bounded search found none.
plugins: No plugin system.
custom_tools: Executable `.vibetree/hooks/post-create` and `pre-remove` scripts run per worktree.
instructions_import: VibeTree imports no instruction files; agent CLIs read their own.
authentication: No integration authentication.
permission_scope: Hooks run with the user's privileges under a git-hooks trust model with a 120 second timeout.
7 atomic answers
Mcp client [unsupported] No MCP client in VibeTree; bounded search found none. Sources: vibe-tree:srch-mcp.
Desktop is Electron (Vite React renderer, embedded Express/WebSocket server on loopback); web client is a React PWA (Vite, vite-plugin-pwa); no mobile app.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
4 atomic answers
Desktop implementation [supported] Electron app packaged by electron-builder with an embedded server and xterm.js terminals. Sources: vibe-tree:arch, vibe-tree:builder.
Intake is typing a branch name (worktree) and a prompt to an agent terminal, or `vibetree run <branch> "prompt"`. No issue import, tracker or Git-event triggers.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), vibetree command-line client (@vibetree/cli) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
external_import: No tracker import.
chat_git_triggers: No chat or Git-event triggers.
authoritative_tracker: No tracker; the worktree/branch is the unit.
stable_ids: Branch names and deterministic session IDs per worktree path and terminal ID, not issue IDs.
sync: No tracker sync.
supported_edits: No issue edits.
external_roundtrips: No external tracker relationship.
9 atomic answers
Local creation [supported] A worktree plus terminal is created from the UI or `vibetree worktrees add`. Sources: vibe-tree:git, vibe-tree:cli.
Prompt intake [supported] `vibetree run <branch> "prompt"` starts a session, launches the preset agent and types the prompt. Sources: vibe-tree:cli.
No plans: tasks are prompts typed into agent terminals; the project agent preset and hooks are the only persisted setup.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
plans: No plan object.
acceptance_criteria: No acceptance criteria field.
editors: No plan editor.
revisions: No plan revisions.
implementation_links: A worktree and branch map to one conversation and reviewable diff.
amendment: Users can keep typing to the running agent; no plan amendment feature.
restart_persistence: Terminal sessions and scrollback persist while the server runs; disk persistence of session buffers is a roadmap item.
Implementation links [partial] A worktree and branch map to one conversation and reviewable diff. Sources: vibe-tree:readme.
Amendment [partial] Users can keep typing to the running agent; no plan amendment feature. Sources: vibe-tree:ws.
Restart persistence [partial] Terminal sessions and scrollback persist while the server runs; disk persistence of session buffers is a roadmap item. Sources: vibe-tree:arch, vibe-tree:readme.
Flat list of worktrees per project; no epics, hierarchy, blockers or readiness.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
epics: No epics.
hierarchy: Worktrees are a flat list.
blockers: No blockers.
readiness: Agent state (idle/working/needs-input/done) is shown, not dependency readiness.
Agents read their own repo instruction files; VibeTree stores only a per-project agent command and hook scripts in `.vibetree/` and keeps terminal scrollback. No memory or shared-context feature.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
instructions: VibeTree manages no instruction files; `.vibetree/config.json` holds only agentCommand.
skills: No skills.
project_docs: No project docs feature.
memory: No memory store; terminal scrollback buffers only.
scope: Project config is committed in the repo so a team can share defaults.
provenance: No provenance tracking.
correction: No memory to correct.
deletion: No memory to delete.
10 atomic answers
Instructions [unsupported] VibeTree manages no instruction files; `.vibetree/config.json` holds only agentCommand. Sources: vibe-tree:projcfg, vibe-tree:rev-srch-memory.
No code search, indexing, retrieval or multimodal input; the product runs terminals and shows Git diffs.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
No issue or idea backlog; the work list is the Git worktree list per project with a live agent-state badge.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
create: Worktrees (branch + terminal) are created, not issues.
edit: No editing of tasks.
discuss: No discussion.
prioritize: No priority.
label: No labels.
assign: No assignment.
search: No search of worktrees found.
filter: No filters.
17 atomic answers
Create [partial] Worktrees (branch + terminal) are created, not issues. Sources: vibe-tree:git.
Agents are plain terminal programs without VibeTree tools; the REST/WebSocket API lets scripts create worktrees and type into sessions, but there are no issue IDs or fields.
Scope
Surfaces: Standalone server (Express + WebSocket, Docker option), vibetree command-line client (@vibetree/cli) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
shared_ids: Session IDs and branch names are shared between UI, CLI and API.
read: `vibetree status` and /api/agent/states read session states and worktrees.
create: `worktrees add` and `run` create worktrees and sessions.
update: No task fields to update.
claim: No claims.
assign: No assignment.
state_changes: States are derived, not set.
dependencies: No dependencies.
14 atomic answers
Shared ids [partial] Session IDs and branch names are shared between UI, CLI and API. Sources: vibe-tree:arch, vibe-tree:cli.
Read [partial] `vibetree status` and /api/agent/states read session states and worktrees. Sources: vibe-tree:cli, vibe-tree:rest.
Create [partial] `worktrees add` and `run` create worktrees and sessions. Sources: vibe-tree:cli.
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
One PTY session per worktree and terminal run concurrently; a fleet badge shows working, needs input, done and idle; no stated concurrency limit.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
quotas: No quota in code; idle sessions are reaped after SESSION_IDLE_TIMEOUT_MS (24h default) on the standalone server.
observed_concurrency: No concurrency measurements are published; the catalog does not measure it.
5 atomic answers
Concurrent sessions [supported] Independent PTY sessions per worktree and terminal run concurrently on the server. Sources: vibe-tree:arch.
Concurrent tasks [supported] Several worktrees run agents in parallel. Sources: vibe-tree:readme.
Quotas [partial] No quota in code; idle sessions are reaped after SESSION_IDLE_TIMEOUT_MS (24h default) on the standalone server. Sources: vibe-tree:cfg.
Observed concurrency [unknown] No concurrency measurements are published; the catalog does not measure it. Sources: vibe-tree:readme.
Status visibility [supported] Dots/badges show working, needs input, done and idle per worktree. Sources: vibe-tree:tracker, vibe-tree:site.
No assignment, claims or queues; the user chooses which worktree and terminal to use. Sessions are deterministic per worktree path and terminal ID so a reconnect reuses the same shell rather than duplicating it.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
human_assignment: No assignment.
agent_assignment: No agent assignment.
claims: No claims.
queues: No queue of work.
routing: No routing.
duplicate_prevention: Deterministic session IDs prevent duplicate shells for the same worktree/terminal; no duplicate-work prevention across worktrees.
Duplicate prevention [partial] Deterministic session IDs prevent duplicate shells for the same worktree/terminal; no duplicate-work prevention across worktrees. Sources: vibe-tree:arch.
No product-owned delegation: agents are independent terminal programs. Their own subagent features are not surfaced.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
roles: No coordinator or worker roles.
model_harness_effort: No model or effort control.
messages: No inter-agent messages.
results_return: No result return.
cross_harness: No cross-harness teams.
orchestration_owner: No orchestration; the user drives terminals.
activation: Not applicable: no delegation feature to activate.
A desktop-only command scheduler queues a command or prompt for a terminal after a delay, once or repeating; no cron, event triggers or completion conditions; it stops when the app closes.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
schedules: Delay-based scheduler (delayMs) in the desktop app only.
events: No event triggers or webhooks.
recurring_tasks: A `repeat` option repeats the queued command at the delay.
completion_conditions: No completion conditions.
overlaps: An e2e test covers terminal scheduler overlap; handling is per terminal.
retries: No retries.
client_independence: Scheduler state lives in the desktop renderer and does not run server-side.
Stop by terminating a session; resume by reattaching; steer by typing in the terminal; desktop notification and web sound when an agent needs input; question detection uses heuristics for Claude Code-style prompts.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
pause: No pause control beyond the agent's own.
pending_decisions: Question patterns mark a worktree needs-input; there is no decision inbox.
escalation: No escalation.
visible_errors: Terminal output and toasts only; no structured failure states.
retained_history: Scrollback is bounded (~100KB) and lost when the server stops; disk persistence is a roadmap item.
10 atomic answers
Pause [unsupported] No pause control beyond the agent's own. Sources: vibe-tree:ws.
Stop [supported] `shell:terminate` and the UI end a session; the worktree remains. Sources: vibe-tree:ws.
Resume [supported] Reattaching a client resumes the same session with buffered scrollback. Sources: vibe-tree:arch.
Steer [supported] Type into the terminal from any attached client. Sources: vibe-tree:ws.
Notifications [supported] Desktop native notifications and web sound on completion/question. Sources: vibe-tree:notif, vibe-tree:site.
Pending decisions [partial] Question patterns mark a worktree needs-input; there is no decision inbox. Sources: vibe-tree:activity, vibe-tree:tracker.
Visible errors [partial] Terminal output and toasts only; no structured failure states. Sources: vibe-tree:tracker.
Chat terminal parity [supported] Terminal is the only interaction surface, so CLI-only prompts are visible. Sources: vibe-tree:arch.
Retained history [partial] Scrollback is bounded (~100KB) and lost when the server stops; disk persistence is a roadmap item. Sources: vibe-tree:arch, vibe-tree:readme.
A worktree sidebar with live state badges (idle, working, needs input, done) and unstaged-change counts, plus a welcome table of worktree states; no epics, dependencies or history timeline.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
fleet_fixture: Fleet view lists worktrees with status dots for several worktrees in one project; project tabs separate repos.
parent_child: No parent/child relations.
dependencies: No dependencies.
history: No history timeline.
workload: Counts of working and needs-input agents appear in the title bar.
navigation_errors: No failed/blocked states.
8 atomic answers
Fleet fixture [partial] Fleet view lists worktrees with status dots for several worktrees in one project; project tabs separate repos. Sources: vibe-tree:site, vibe-tree:tracker.
No presets beyond the project agent command; any terminal workflow can be used. Orchestration is manual.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), vibetree command-line client (@vibetree/cli) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
growing_epic: No epic growth.
presets: A per-project agent preset launches an agent command with one click.
natural_language: No natural-language configuration.
agent_configuration: Agent command per project or `--agent`; model/effort are the agent CLI's.
live_roles: No roles.
retained_relationships: No relationships recorded.
discoverability: Onboarding dialog, welcome screen and keyboard shortcuts help first use.
auth_friction: Desktop needs none; standalone server needs pairing or password to be safe.
10 atomic answers
Quick task [supported] Create a worktree and type a prompt or run `vibetree run`. Sources: vibe-tree:cli.
Agent work executes where the VibeTree server runs: the user's machine (desktop) or a user-managed host running the standalone server/Docker. No vendor cloud; sessions keep running on the server after clients disconnect.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
managed_cloud: The site states there is no cloud component.
hybrid: Desktop and web clients can attach to the same self-managed server.
provisioning: User provisions the VM; `npm run deploy` builds and starts the container.
expiry: Standalone server reaps sessions idle for 24h by default (SESSION_IDLE_TIMEOUT_MS); desktop keeps sessions until quit.
12 atomic answers
Local [supported] The desktop app embeds the server and runs terminals locally. Sources: vibe-tree:arch, vibe-tree:site.
Byo remote [supported] DOCKER.md deploys the server and web UI on a VM/EC2; terminals run on that host. Sources: vibe-tree:docker.
Self hosted [supported] Standalone server (apps/server) is the self-hosted service. Sources: vibe-tree:arch, vibe-tree:readme.
Managed cloud [unsupported] The site states there is no cloud component. Sources: vibe-tree:site.
Hybrid [partial] Desktop and web clients can attach to the same self-managed server. Sources: vibe-tree:arch.
Provisioning [partial] User provisions the VM; `npm run deploy` builds and starts the container. Sources: vibe-tree:docker.
Payer [supported] User pays their host and agent providers; VibeTree is free. Sources: vibe-tree:site.
Resources [supported] Host resources are the user's; no limits in VibeTree. Sources: vibe-tree:docker.
Region [supported] Chosen by the user's host; no vendor region. Sources: vibe-tree:docker.
Expiry [partial] Standalone server reaps sessions idle for 24h by default (SESSION_IDLE_TIMEOUT_MS); desktop keeps sessions until quit. Sources: vibe-tree:arch, vibe-tree:cfg.
Client disconnect [supported] A client disconnect only detaches; the PTY keeps running and output is buffered (~100KB). Sources: vibe-tree:arch.
Other device continuation [supported] Any paired phone or browser can reattach to the same session. Sources: vibe-tree:arch, vibe-tree:readme.
One Git worktree and branch per task; a PTY per session. No per-agent container, VM or OS sandbox; the whole server can run in Docker. A worktree is not a security boundary.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
container: DOCKER.md runs the whole server and terminals in one container; no per-worktree container.
vm: No VM isolation.
os_sandbox: No OS sandbox.
filesystem: Worktrees separate files by directory only; processes run with the user's filesystem access.
process: Agents run as ordinary user processes in a PTY.
network: No network controls.
secrets: `post-create` hooks can copy .env into a worktree; no secret boundary.
security_boundary: No hostile-code containment claimed.
12 atomic answers
Checkout [supported] The main checkout and worktree checkouts are separate directories. Sources: vibe-tree:git.
Branch [supported] Each worktree creates a branch (`worktree add -b`). Sources: vibe-tree:git.
Container [partial] DOCKER.md runs the whole server and terminals in one container; no per-worktree container. Sources: vibe-tree:docker, vibe-tree:srch-isolation.
Sessions persist across client disconnects with bounded in-memory scrollback; they do not survive a server restart (disk persistence is a roadmap item); a crashed agent leaves the shell.
Scope
Surfaces: Standalone server (Express + WebSocket, Docker option), VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
worker_crash: A crashed agent process returns to the shell prompt; there is no automatic restart.
service_restart: Session buffers do not survive server restarts; disk-persisted buffers are a roadmap item.
expiry: Standalone sessions idle for 24h by default are reaped.
task_resume: No task-level resumption beyond the live session.
state_reconstruction: Agent state is re-derived from new terminal traffic; replayed scrollback is not treated as activity.
context_loss: Agent conversation context is the agent CLI's; lost scrollback beyond the buffer.
manual_repair: Users restart agents manually.
multi_day_continuity: Sessions live up to the idle timeout on a server; desktop sessions end at quit.
12 atomic answers
Client disconnect [supported] Disconnect detaches listeners only; the session keeps running and reattach restores scrollback. Sources: vibe-tree:arch.
Worker crash [partial] A crashed agent process returns to the shell prompt; there is no automatic restart. Sources: vibe-tree:arch.
Service restart [unsupported] Session buffers do not survive server restarts; disk-persisted buffers are a roadmap item. Sources: vibe-tree:readme.
Expiry [partial] Standalone sessions idle for 24h by default are reaped. Sources: vibe-tree:cfg, vibe-tree:arch.
Process reconnect [supported] Reconnect resumes the same PTY via deterministic session IDs. Sources: vibe-tree:arch.
Task resume [unsupported] No task-level resumption beyond the live session. Sources: vibe-tree:arch.
State reconstruction [partial] Agent state is re-derived from new terminal traffic; replayed scrollback is not treated as activity. Sources: vibe-tree:tracker.
Context loss [partial] Agent conversation context is the agent CLI's; lost scrollback beyond the buffer. Sources: vibe-tree:arch.
Lifecycle hooks (`post-create`, `pre-remove`) let users install dependencies, copy .env files and stop services per worktree; VibeTree detects dev-server URLs for a preview pane. No dependency caching, port allocation or snapshots.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
dependencies: Hooks can run installs; nothing is automatic.
caches: No cache sharing.
snapshots: No snapshots.
services: `pre-remove` hooks can stop services; none are managed.
ports: Dev server URLs are detected and shown; no port allocation.
secrets: Hooks receive VIBETREE_PROJECT_PATH so they can copy .env files.
duplicate_installs: Each worktree installs separately via its hook.
collisions: No collision handling.
10 atomic answers
Dependencies [partial] Hooks can run installs; nothing is automatic. Sources: vibe-tree:readme.
Live agent state (idle, working, needs input, done) derived from terminal traffic, per-worktree git status counts, and bounded scrollback; no logs, traces, usage statistics or failure reasons.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
logs: Terminal scrollback buffer only.
traces: No traces.
failure_reasons: No failure reasons.
usage_export: No usage export.
task_stats: No task statistics; a desktop stats dialog shows diagnostics only.
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Single-operator tool: one shared password or per-device pairing; several clients can attach to the same terminal session, but there are no identities, comments, presence or attribution.
Scope
Surfaces: Standalone server (Express + WebSocket, Docker option), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
visibility: Any authenticated client sees the same terminals; one credential, no per-user view.
discussion: No discussion.
comments: No comments (diff notes go to the agent, not people).
presence: No presence.
coprompting: Multiple clients attached to a session can all type into it; no ordering, attribution or per-user permission.
ordering: No input ordering.
conflicts: No conflict handling.
attribution: No attribution.
11 atomic answers
Visibility [partial] Any authenticated client sees the same terminals; one credential, no per-user view. Sources: vibe-tree:arch, vibe-tree:authsvc.
Coprompting [partial] Multiple clients attached to a session can all type into it; no ordering, attribution or per-user permission. Sources: vibe-tree:ws, vibe-tree:arch.
Ordering [unsupported] No input ordering. Sources: vibe-tree:ws.
Conflicts [unsupported] No conflict handling. Sources: vibe-tree:ws.
No roles, SSO or membership; access is a single password, a loopback token (desktop) or revocable paired devices.
Scope
Surfaces: Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
organization_roles: No roles.
project_roles: No roles.
task_roles: No roles.
membership: No membership.
sso: No SSO.
provisioning: No provisioning.
unauthorized_access: Optional password and device JWT; authentication is off by default on the standalone server, which binds 0.0.0.0 and warns at startup.
revocation: Paired devices can be revoked over /api/devices/:deviceId; JWT secret has a dev default unless set.
Unauthorized access [partial] Optional password and device JWT; authentication is off by default on the standalone server, which binds 0.0.0.0 and warns at startup. Sources: vibe-tree:cfg, vibe-tree:arch.
Revocation [partial] Paired devices can be revoked over /api/devices/:deviceId; JWT secret has a dev default unless set. Sources: vibe-tree:rest, vibe-tree:cfg.
Plan scope [supported] No plans; features are the same for everyone. Sources: vibe-tree:site.
No product approvals: permission prompts are the agent CLI's and appear in the terminal; VibeTree detects them for notifications. Default standalone mode is unauthenticated unless configured.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
command: The agent CLI asks; VibeTree flags needs-input via question patterns.
tool: No tool approvals.
network: No network controls.
secret: No secret approvals.
delivery: No delivery approvals.
approver_identity: No approver identity.
lifetime: No scoped approvals.
allow: Allow/deny happens in the agent terminal.
14 atomic answers
Command [partial] The agent CLI asks; VibeTree flags needs-input via question patterns. Sources: vibe-tree:activity.
Revoke [partial] Terminate the session. Sources: vibe-tree:ws.
Tunnels [unsupported] No tunnels; QR pairing uses the server URL. Sources: vibe-tree:authsvc.
Defaults [partial] Desktop embeds on loopback with a per-launch token; standalone has authentication off by default. Sources: vibe-tree:cfg, vibe-tree:arch.
No activity or decision history beyond terminal scrollback and Git history.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
actions: No action log.
approvals: No approval log.
edits: Git history and diffs hold edits.
discussion: No discussion.
decisions: No decision log.
cross_user_persistence: No users.
cross_session_persistence: Scrollback persists only while the server runs.
A changes dock shows staged and unstaged diffs per worktree with maximize mode; a selected file can be sent as a note to the agent; keyboard shortcuts exist; phone web layout; no review queue or approvals.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
pending_reviews: Worktree list shows change counts; no pending-review queue.
change_understanding: Staged and unstaged diffs per file.
evidence_navigation: Click a file in the changes dock; no test/CI evidence.
comments: A note can be sent to the agent as its next prompt; no human-to-human comments.
request_changes: Sending a note to the agent works as a request for changes.
shipping_guidance: No next-shipping-action guidance.
effort: No reviewer effort measurements.
missed_evidence: No missed-evidence detection.
13 atomic answers
Pending reviews [partial] Worktree list shows change counts; no pending-review queue. Sources: vibe-tree:site.
The same server session can be reattached from another device with the same credential, giving full takeover of terminal and worktree state; there is no identity transfer or handoff record.
Scope
Surfaces: Standalone server (Express + WebSocket, Docker option), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
ongoing_takeover: Another authenticated client can attach to and type into the running session.
session_history: Bounded scrollback only.
decisions: No decision record.
artifacts: Files live in the worktree.
permissions: Same credential; no permission model.
ownership: No ownership.
attribution: No attribution.
context_loss: Lost beyond the buffer; a server restart ends sessions.
12 atomic answers
Ongoing takeover [partial] Another authenticated client can attach to and type into the running session. Sources: vibe-tree:arch, vibe-tree:ws.
Same task [supported] Same worktree and terminal session. Sources: vibe-tree:arch.
Session history [partial] Bounded scrollback only. Sources: vibe-tree:arch.
Retained outputs are the Git worktree files, staged/unstaged diffs on demand and bounded terminal scrollback; a browser preview pane shows running dev servers while they run. No gallery, screenshots, recordings or reviewer outputs.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), VibeTree web app (React PWA served by the standalone server) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
documents: Files in the worktree only.
screenshots: No screenshot capture.
recordings: No recordings.
previews: Dev server URLs are detected and shown in a preview pane while running.
test_outputs: Only visible in terminal scrollback.
reviewer_outputs: No reviewer agents.
gallery: No gallery.
task_links: Artifacts are scoped to the worktree.
13 atomic answers
Diffs [supported] Staged and unstaged diffs per worktree via git:diff messages. Sources: vibe-tree:ws, vibe-tree:release.
Documents [partial] Files in the worktree only. Sources: vibe-tree:git.
No product-run verification: users run tests inside terminals; hooks can run scripts on create/remove only.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Product-managed Git: create/remove worktrees with new branches, list worktrees, status, staged and unstaged diffs; branch deleted on removal. Committing, pushing and PRs happen in the agent terminal; no rebase or conflict workflow.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), vibetree command-line client (@vibetree/cli) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
commits: No commit feature; the agent or user commits in the terminal.
pull_requests: No PR creation or management.
comments: No PR comments.
ci_response: No CI response.
rebase: No rebase.
conflicts: No conflict handling.
product_state: Worktree list and git status counts are product state; no commit/PR state.
9 atomic answers
Branches [supported] Branch created per worktree and deleted on removal. Sources: vibe-tree:git.
No approval, merge, release or deploy authority in the product.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
approve: No approval flow.
merge: No merge code.
release: No release tooling.
deploy: No deployment tooling (the project's own Docker deployment is not a user feature).
No completion evidence or rollback features; deleting a worktree and its branch discards an experiment.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
commit_links: No commit links.
pr_links: No PR links.
build_links: No build links.
deployment_links: No deployment links.
delivery_status: No delivery status.
retained_evidence: No retained evidence.
rollback: Removing the worktree and its branch discards failed experiments.
revert: No revert feature.
9 atomic answers
Commit links [unsupported] No commit links. Sources: vibe-tree:srch-pr.
No batch review or shipping queue; reviewers open each worktree's changes dock in turn.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
MIT license for the monorepo (desktop app, server, web, CLI, core packages) at v0.2.0; no closed or hosted components.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Fully self-hosted: desktop app or standalone server/Docker on user hardware, no vendor account or service, data lives in Git worktrees on the host. No export/import features; history is Git.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
export: Work is plain Git branches; no export feature.
import: Existing repositories open directly.
history_portability: Git history portable; scrollback and agent state are not exported.
8 atomic answers
Self hosting [supported] Standalone server and Docker deployment on user-controlled hosts. Sources: vibe-tree:docker, vibe-tree:readme.
The site states no cloud component and no telemetry; bounded search found no telemetry, analytics or updater code. Code and terminal data stay on the user's machine or their own server; agent providers receive code per their policies. A privacy-documentation issue is open.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
credentials: Standalone server password and JWT secret are configured via environment; JWT secret has an insecure default unless set.
retention: In-memory scrollback until server stop; idle reaping after 24h.
training: Agent providers' policies apply; VibeTree has no training use because it receives no data.
telemetry_controls: No telemetry exists, so no control; none needed.
15 atomic answers
Code data [supported] Stays on the user's machine or server; no VibeTree service receives it. Sources: vibe-tree:site, vibe-tree:srch-tele.
Credentials [partial] Standalone server password and JWT secret are configured via environment; JWT secret has an insecure default unless set. Sources: vibe-tree:cfg.
Logs [supported] Local scrollback only. Sources: vibe-tree:arch.
Artifacts [supported] Local worktrees. Sources: vibe-tree:git.
Retention [partial] In-memory scrollback until server stop; idle reaping after 24h. Sources: vibe-tree:arch, vibe-tree:cfg.
Free and open source (MIT) with no paid plan or hosted service; agent subscriptions are bought separately.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
credits: No credits.
trial: No trial needed.
overages: None.
12 atomic answers
Currency [supported] Not applicable: no price. Sources: vibe-tree:site.
Interval [supported] Not applicable: free. Sources: vibe-tree:site.
Scenario cost is $0 for VibeTree for one, two or five developers; agent subscriptions, model costs and optional VM hosting are separate and unmodeled here.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
two_people: $0 for VibeTree; there is no collaboration feature to price.
task_assumptions: No fixed workload published; the catalog invents none.
tokens: Token spend is provider-specific.
compute_hours: User's own host or laptop.
variable_cost: Agent usage varies.
unknown_cost: Agent provider and VM costs are unknown to VibeTree.
11 atomic answers
One person [supported] $0 for VibeTree. Sources: vibe-tree:site.
Two people [partial] $0 for VibeTree; there is no collaboration feature to price. Sources: vibe-tree:site.
Five people [supported] $0 for VibeTree. Sources: vibe-tree:site.
Task assumptions [unknown] No fixed workload published; the catalog invents none. Sources: vibe-tree:site.
Concurrency [supported] No concurrency pricing. Sources: vibe-tree:site.
Tokens [unknown] Token spend is provider-specific. Sources: vibe-tree:site.
Compute hours [unknown] User's own host or laptop. Sources: vibe-tree:docker.
Single-maintainer open-source project at v0.2.0 (2026-07-24); support via GitHub issues; no response commitments; latest commit 2026-07-25 and several unresolved issues including a Windows launch failure.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
release_stage: Pre-1.0 (0.2.0) with unsigned macOS/Windows builds.
support: GitHub issues only.
response_commitments: No commitments published.
release_activity: Releases 0.0.1 (2025-07-29) and 0.2.0 (2026-07-24); default branch last pushed 2026-07-25.
Everything is free: MIT open source, free download, no trial or card; two-person collaboration, issue management and managed remote compute do not exist, but a BYO-host Docker deployment and BYO agent subscriptions work for free.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback), Standalone server (Express + WebSocket, Docker option) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
trial: No trial needed.
credits_trial: No credits.
paid_only: No paid-only tier.
early_access: No gated access.
free_scenarios: Free: local parallel agents, BYO subscriptions, BYO remote host, phone web, diff review; not available: collaboration, issues.
10 atomic answers
Ongoing free [supported] Free and open source. Sources: vibe-tree:site.
Trial [unsupported] No trial needed. Sources: vibe-tree:site.
Credits trial [unsupported] No credits. Sources: vibe-tree:site.
Fully transparent: free, no paid plans, no markups; third-party agent costs are separate.
Scope
Surfaces: VibeTree Electron desktop app (embeds the server on loopback) · Version: v0.2.0 (commit 4ada164, released 2026-07-24) · Plan: Open source (MIT) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
9 atomic answers
Units [supported] No billing units. Sources: vibe-tree:site.
Included limits [supported] No limits. Sources: vibe-tree:site.
One server core embedded by Electron and run standalone; deterministic per-worktree PTY session IDs; sessions survive client disconnect and are reaped after idle timeout (default 24h); auth modes.
Free and open source, bring your own agent subscriptions, no cloud component and no telemetry; macOS (dmg), Windows (exe) and Linux (AppImage/deb) downloads; fleet status, changes dock, persistent sessions, CLI, phone PWA, hooks, presets.
Release notes list one backend everywhere, fleet status with a ding, browser preview, changes dock with send-note-to-agent, PWA, agent presets, vibetree CLI and worktree hooks; assets are macOS arm64/x64 dmg and zip, Windows Setup.exe, Linux AppImage and deb.
shell:start/write/resize/status/get-buffer/terminate/get-agent-states and git:worktree:list/status/diff/diff:staged/worktree:add/remove messages; sessions persist when a connection closes.
`vibetree worktrees list|add|remove`, `status`, `run <branch> ["prompt"]` with --server/--token/--project/--agent/--delay; uses the same REST and WebSocket APIs as the web app.
A user reports the Windows Setup.exe fails at launch with "Cannot find module body-parser" because app.asar ships no transitive dependencies; open, not confirmed by a maintainer in the thread read.
Reviewer bounded search at pinned commit: 3 file hit(s), reviewed: apps/desktop/src/main/stats-dialog.html, apps/desktop/src/renderer/components/ui/use-toast.ts, packages/core/src/utils/system-diagnostics.ts. None is a memory or instruction-file feature: the hits are a toast reducer state variable (use-toast.ts) and process-memory figures in the desktop diagnostics dialog and system-diagnostics.ts.
Desktop renderer dialog that queues a command to send to a terminal after a delay, once or repeating; state cached in the renderer and listed per worktree.
Reviewer bounded search at pinned commit: 4 file hit(s), reviewed: apps/web/src/components/Toaster.tsx, apps/web/src/components/WorktreePanel.tsx, apps/web/src/hooks/useWorktreeStatuses.ts, packages/core/src/utils/agent-activity.ts. None is a verification feature: the hits are eslint-disable comments and a control-character regex in the web components and agent-activity.ts.
Reviewer bounded search at pinned commit: 4 file hit(s), reviewed: apps/desktop/src/main/embedded-server.ts, apps/desktop/src/main/stats-dialog.html, apps/web/src/App.tsx, packages/core/src/utils/system-diagnostics.ts. None is a review summary or queue: the hits are the fleet-summary badge of agent states (web App.tsx), diagnostics and an embedded-server status summary.