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.