Vibe Toolbox
windows-first · trial 14d · local-first

AI coding
sessions that stay
organized.

A native desktop workspace for durable Codex, Claude Code, and local-model sessions. Isolate work in git worktrees, inspect every diff, run tests and browser checks, and recover the context normal terminals lose.

Codex + Claude Code
Git worktrees + review
Local SQLite session store
Tests · Playwright · MCP
vibetoolbox · vibe-checkout · main⌘K · open command palette
Agent Workbench4 active
New session

UX · billing redesign

claude-code

Running
feature/checkout-v2
7 files+184 / −56

Backend · entitlement cache

codex/openai

Needs input
fix/cache-ttl
3 files+42 / −12

Database · migration 0042

codex/openai

Clean
db/users-not-null
1 files+18 / −0

Review · PR #142

claude-code

Reviewing
review/pr-142
12 files+401 / −188

The problem

AI coding breaks down when work leaves the workspace.

Fragile sessions

Terminal tabs close. CLI state vanishes. Resume IDs disappear. Recreating context costs the whole afternoon.

Scattered tools

Chat lives here. Diff lives there. Tests, browser, notes, terminal — all in different windows you tab between.

Risky changes

Agents produce diffs faster than humans can read. Without prompt, diff, and tests in one place, review breaks down.

Team collisions

Multiple developers and agents touch the same repo. Worktrees and branches drift without anyone noticing.

The flow

From prompt to reviewed change, in one project workspace.

Every step is part of the product surface — not a separate tool you have to context-switch into.

  1. project01

    Add or clone

    Track local projects, repository metadata, commands, runtime defaults, and worktree policy.

  2. runtime02

    Start session

    Choose Codex/OpenAI, Codex/Ollama, Codex/LM Studio, custom OpenAI-compatible, or Claude Code.

  3. worktree03

    Pick the lane

    Default to a safe worktree session. Explicit opt-in for main repo. Base branch and commit always visible.

  4. panels04

    Work in panels

    Chat, terminal, diff, editor, test runner, browser, Playwright, MCP, hooks, and audit — all session-scoped.

  5. review05

    Review evidence

    Prompt markers, execution diffs, git status, comments, test output, and validation events stay connected.

  6. ship06

    Checkpoint / PR

    Create local checkpoint commits, prepare PRs through gh, or route findings into the next fix session.

  7. durable07

    Recover context

    Reconnect to the daemon and replay persisted session history when the UI or runtime fails.

The product

Chat is one panel. The workspace is the product.

Six surfaces, one cockpit. Each piece earns its real estate by sitting next to the agent turn that needs it.

Durable Agent Workbench

All non-terminated sessions stay visible per project, with status, follow-up input, mode changes, stop controls, popouts, and replay.

  • No hard 16-session cap
  • Codex + Claude Code parsers
  • Panel-scoped messages
  • Detached popouts

Git worktrees + review

Start AI work in a scoped lane, then inspect exactly what changed before it becomes a PR.

  • Main-repo or worktree scope
  • Working / branch / commit diffs
  • Prompt markers + execution diffs
  • Checkpoint commits + PR status

Tests · Browser · Playwright

Validate where the agent worked. Test commands, browser preview, and Playwright runs in the same session surface.

  • Test discovery + history
  • Browser + Playwright panels
  • Project command runner
  • Audit log per workflow

Local-first runtime control

Launch installed agent CLIs locally. Secrets stay in env vars, credential managers, SSH agents, or keychain references.

  • OpenAI · Ollama · LM Studio · custom
  • Approval, sandbox, web search
  • MCP selection + capability proof
  • SSH/tmux remote persistence

Team visibility

See who is viewing a project, invite collaborators through GitHub, and open read-only live session popouts.

  • Project presence heartbeat
  • Read-only live popouts
  • GitHub invitations
  • Direct trusted peer transport

Recovery + audit

When the app reconnects, replay persisted history, surface crashed sessions, and keep audit evidence attached.

  • SQLite per-project store
  • Daemon reconnect path
  • Crash + resume metadata
  • Sanitized diagnostics export

also included

Terminal · editor · logs · dashboard · setup · todo · PR status · rules · MCP · hooks · audit · roadmap · dependencies · lifecycle · database inspection.

Local-first by design

Your repo stays local. The cloud handles accounts, not your source.

Vibe Toolbox runs agent CLIs locally, stores project and session state in a local SQLite database, and only talks to the cloud for what the cloud should actually do.

On your machine

  • desktop app + daemon
  • local SQLite store
  • agent CLIs (Codex, Claude)
  • local repos + worktrees
  • prompts · diffs · terminal output

Vibe Toolbox Cloud

  • account + GitHub identity
  • signed entitlement (Stripe)
  • release access
  • hosted team relay (planned)
  • opt-in diagnostics
default boundary: source code, prompts, diffs, terminal output, and model responses never leave the device.

What stays on your machine

  • Project files and worktrees
  • Prompts and model output
  • Execution diffs and checkpoint commits
  • Terminal, test, browser, and Playwright output
  • Audit events, todos, rules, and MCP capability data

What the cloud touches

  • Email + GitHub identity for sign-in
  • Stripe subscription + signed entitlement
  • Up to 3 device activations + offline grace
  • Hosted relay (only when paid Team ships)
  • Diagnostics — only when you export them
windows-first · signed updater

Team visibility

See teammate AI work before you collide with their branch.

GitHub-backed identity, invitations, project presence, shared active-session listings, and read-only live popouts. Hosted relay coming with paid Team.

ready

Read-only live popouts

Watch a teammate's session transcript without taking control. Prompt input, stop, and mode changes stay hidden.

ready

GitHub invitations

Invite collaborators through the same GitHub flow that grants repo access. No manual peer-token exchange.

planned

Hosted relay

Coordinated sessions across the internet. Available with paid Team once hosted relay and seats are production-ready.

Team plan launch — `$49/seat/month` (planned)

Early-access design partners: $39/seat/month.

Join the waitlist

Pricing

Solo costs less than a single PR review service.

Stripe-backed subscription with a 14-day trial. Up to 3 activated devices and 7-day offline grace.

Trial

Prove the workflow on your own machine before paying.

Free14 days
  • Solo feature access during trial
  • Local projects and AI sessions
  • Codex + Claude Code runtimes
  • Worktrees, diff, tests, browser, MCP
  • Up to 3 activated devices
Start trial
most popular

Solo

live

For solo vibe coders who want a real workspace around AI coding sessions.

$29.99per month
  • Durable Codex + Claude Code sessions
  • Codex/OpenAI · Ollama · LM Studio · custom
  • Main-repo + worktree sessions
  • Native chat · terminal · diff · editor
  • Tests · browser · Playwright · MCP · hooks · audit
  • Prompt markers + execution diffs + checkpoints
  • SSH/tmux remote persistence
  • Signed updater + diagnostics export
Subscribe to Solo

Team

For small teams coordinating AI sessions across the same repositories.

$49per seat / mo · planned
  • Everything in Solo
  • Team workspace + seat model
  • Hosted collaboration relay
  • GitHub identity + repo permissions
  • Project presence across instances
  • Read-only live session views
  • Team-safe worktree defaults
  • Collaboration audit + notifications
Join waitlist

FAQ

Common questions before you trial.

Is Vibe Toolbox an IDE?+

No. It is a native AI development workspace. File, terminal, git, diff, test, browser, and review surfaces are included, but it is designed to coordinate AI coding sessions around existing projects — not replace every editor workflow.

Which AI runtimes are supported?+

Codex and Claude Code. Codex runtime options include OpenAI/default, Ollama, LM Studio, and custom OpenAI-compatible endpoints, with approval policy, sandbox mode, web search, and config overrides. External runtimes require your installed and authenticated CLIs.

Does Vibe Toolbox upload my code?+

By default, no. Source code, prompts, diffs, terminal output, and model responses stay on your machine. The cloud is used only for account identity, subscription entitlements, release access, planned hosted team collaboration, and explicit support diagnostics.

Why does it run a daemon?+

The daemon owns long-running sessions, supervision, SQLite persistence, recovery, git/worktree operations, panels, SSH/tmux orchestration, and structured agent output parsing. That lets the UI reconnect and replay useful history instead of losing everything when a window closes.

What is in Solo?+

Local projects, durable AI sessions, Codex/Claude/local runtime setup, worktrees, git review, native panels, signed updates, diagnostics export, and personal workflow features. Solo is $29.99/month.

Is Team available?+

Team is on the way. The codebase already has local presence, GitHub-backed invitations, read-only live popouts, and direct trusted peer transport for LAN/VPN validation. Paid Team launches after the hosted relay, seats, permission checks, and production validation are complete.

What platforms are supported?+

Windows x64 first, through a signed Tauri desktop app with local Windows updater publishing. macOS and Linux are not promised yet — release scope expands after Windows is stable.

/ ship

Give your AI coding
sessions a real workspace.

Start a 14-day trial of Vibe Toolbox Solo, or join the Team waitlist for hosted collaboration.

Start Trial Join Team Waitlist

windows x64 · signed updater · 3 devices · 7-day offline grace