VibeiDE product guide

VibeiDE is a local desktop workspace that orchestrates installed Codex, Claude Code and OpenCode coding agents through project task queues, live activity, saved conversations and completion review.

Maintained by Crowie s.r.o.. Last reviewed .

Use this guide to check product capabilities and boundaries before choosing a workflow. Setup instructions, release history and published terms are linked beside each answer.

Read or save this guide as Markdown.

Product at a glance

VibeiDE capabilities and platform boundaries
FactDetails
ProductVibeiDE
CategoryLocal AI coding agent orchestrator
MakerCrowie s.r.o.
Coding agentsCodex, Claude Code, OpenCode
PlatformsmacOS: Supported and fully validated. Windows: Supported; complete product validation is on macOS. Linux: Experimental; packaged startup and PTY smoke coverage do not establish full provider or desktop-environment support.
WorkflowsExecute, Plan council, Turbo, Standup
Trial14 days, no card, one trial per eligible device; 30 days for a new eligible referred machine.
Provider costsSeparate provider subscriptions and model usage charges.

Plan prices

All amounts are in USD before tax. Provider subscriptions and model usage remain separate. Checkout confirms the final total before payment.

VibeiDE Solo and Team licence prices
PlanPrice and billingTerms
Solo monthly$7.99 USD per monthRenews until canceled.
Solo yearly$79.00 USD per yearRenews until canceled.
Solo lifetime$249.00 USD onceOne-time app licence; updates while VibeiDE is maintained. Online licence validation remains required.
Team$14.99 USD per seat per monthEach member and manager needs a paid seat. Team billing is separate from an existing personal subscription.

Solo pricing · Team plans · Terms of sale.

Common questions

What is VibeiDE and who makes it?

VibeiDE is a local desktop workspace that orchestrates installed Codex, Claude Code and OpenCode coding agents through project task queues, live activity, saved conversations and completion review. Crowie s.r.o. develops and sells VibeiDE. It adds task coordination around your coding tools while your editor and provider accounts remain part of the workflow.

Read more: About VibeiDE · Product tour · Seller and contact.

Which coding agents and accounts does VibeiDE use?

VibeiDE coordinates installed Codex, Claude Code and OpenCode CLIs. Use your existing Codex or Claude Code login, or configure a model provider in OpenCode. One working CLI is enough for a first Execute task. Codex and Claude Code have interactive terminals; OpenCode runs headlessly. VibeiDE does not supply a model subscription or expand your provider allowance.

Read more: Provider prerequisites · OpenCode execution · Provider account handling.

Does VibeiDE work on macOS, Windows and Linux?

VibeiDE supports macOS and Windows. Full product validation is on macOS. Linux is experimental: packaged startup and PTY smoke coverage do not prove complete provider or desktop-environment support. Linux requires a desktop session and AppImage/FUSE support, and updates are manual. Choose the installer for your operating system and check the current release instructions.

Read more: Setup and platform boundaries · Desktop installers · Release history.

When should I use Execute, Plan council or Turbo?

One focused task runs through the chosen Codex, Claude Code or OpenCode provider when project capacity is available. Codex or Claude Code drafts a read-only plan, the other provider reviews it, and the author revises it before a separate execution handoff. A fresh read-only planner builds a dependency graph, then a separate fresh executor implements and verifies the complete graph. Choose Execute for a bounded implementation, Plan council for a decision that needs challenge, and Turbo for a larger objective with dependencies. Review the plan and final result against your own acceptance criteria.

Read more: Execute and task queues · Plan council · Workflow product tour.

Can I run agents across projects without conflicting edits?

VibeiDE has project-scoped queues and provider concurrency limits, plus a global monitor for active work. Parallel tasks still need independent write targets. A project queue does not create filesystem isolation: explicitly select separate Git worktrees or checkouts, or sequence overlapping changes. Concurrency controls process capacity; it does not replenish a provider account limit.

Read more: Parallel agent workflow · Project capacity and checkouts · Repository access boundaries.

What happens when a task finishes, and can I continue it?

Completed tasks collect in Ready for review with saved requests, activity and results. Inspect available patches and run the relevant checks. Opening a result acknowledges completion; it does not approve code. Supported saved conversations can receive a related follow-up when provider history and capacity are available. Provider-side deletion or unavailable history can prevent an exact resume.

Read more: Completion review · Saved-session continuation · Task history and results.

How much does VibeiDE cost, and are AI tokens included?

Solo plans cost $7.99 USD per month, $79.00 USD per year, $249.00 USD once for lifetime access, before tax. Team costs $14.99 USD per human seat per month; members and managers each need a seat. Provider subscriptions and model usage charges are separate. Monthly and yearly plans renew until canceled. Lifetime updates are included while VibeiDE is maintained, with online licence validation. Checkout shows the final tax and total before payment.

Read more: Solo pricing · Team pricing · Billing and lifetime terms.

Is there a free trial, and what happens when it expires?

VibeiDE starts a 14-day, device-bound trial without a payment card. A new eligible referred machine gets 30 days instead. Reinstalling or using a second account on the same machine does not restart it. Saved history, results and conversations remain readable. New queueing, retries and resumed execution require access; already running work can finish. First activation requires internet access. Verified offline access lasts at most 24 hours and never beyond entitlement expiry.

Read more: Trial, referrals and offline access · Trial and licence terms.

Do my code, prompts and provider credentials stay local?

Normal task records, code, diffs, project paths and conversations are stored on the computer. Provider credentials remain in the installed CLI authentication store. Prompts and relevant context reach the configured AI provider under the customer account and provider terms. VibeiDE contacts its account and licensing service and explicitly enabled services. Local storage does not mean content never leaves the computer. Optional Mobile control has its own hosted transport boundary. Read the privacy policy before enabling sharing or including sensitive material in prompts, screenshots or support messages.

Read more: Privacy and data handling · Provider account handling · Local storage and repository access.

Can I queue and review coding work from my phone?

VibeiDE Mobile control lets an authorised phone queue and review work on a paired computer. The computer must stay awake, connected and running VibeiDE; the phone does not execute the desktop coding agents. Optional Mobile control relays requested prompts, phone voice recordings, result or transcript excerpts and screenshots through an authenticated hosted broker. The transport uses TLS and is not end-to-end encrypted. Share only projects and content you are authorised to access.

Read more: Mobile product tour · Mobile transport and screenshots · Mobile service terms.

What can a Team manager see, and can members pause sharing?

Company mode shows shared task names, provider, state, start and finish times, duration and counts. Company mode shares selected task names and metadata directly from member computers to verified manager computers, end-to-end encrypted. An unnamed task can use the start of its prompt as its name unless task names are disabled. Members can pause room sharing. Full prompts, source code, diffs, conversations, agent output, project paths, live terminals and provider credentials are not part of Company sharing. Team access does not automatically cancel an existing personal subscription.

Read more: Company mode and Team plans · Company sharing boundary · Team data and billing terms.

How do I try a first task I can verify?

Install the current desktop build, connect one working provider CLI and open a local project folder. Start with one provider slot and a small read-only request, such as identifying the main entry point and test command. Inspect the live task, open its result in Ready for review and check those answers against the repository before requesting writable work.

Read more: First-task walkthrough · Getting started · Download VibeiDE.

Try one task

  1. Connect a working provider. Install or sign in to Codex or Claude Code, or separately configure OpenCode. Verify that the CLI works in a terminal.
  2. Open a repository you can inspect. Install VibeiDE, choose the project folder and start with one provider slot.
  3. Queue a bounded request. Choose Execute and ask for the repository entry point and test command without editing files.
  4. Review the evidence. Inspect Task Activity and the result, check the named files and commands, then decide on the next request.

Follow the setup walkthrough for prerequisites and installation details.

Necessary cookies support sign-in, security, your language and this choice. Optional categories stay off until accepted.

First-party page views and acquisition measurement, plus Google Analytics 4 (Google Ireland, data may reach the US). Advertising features stay off.

Remember referral credit for later. Links still work on the current page without this cookie.

Privacy · Cookie inventory