Our server knows nothing. By design.

Two promises. Your tasks stay on your computer, and remote control is sealed between your own devices.

Reviewed

Tasks data

Your tasks live on your computer.

Nothing about your work needs our server. Prompts leave your computer only to reach your own AI provider.

Your computer

Local database

  • Tasks
  • Prompts
  • History
  • Conversations

Logins stay in each CLI

  • Claude Code
  • Codex
  • OpenCode

Your AI provider

Under your own account, limits and terms.

VibeiDE server

Not in this path. It never receives your tasks.

Where your data lives

Your work never needs our server to exist. Mobile control and Company mode only add an encrypted path between your own devices.

  • Your computerTasks, prompts, history and conversations, in a local database.
  • Each CLIClaude Code and Codex logins stay in their own auth stores.
  • Your AI providerPrompts go from your computer straight to the provider, under your own account.

Website logins in the Vault

Agents can sign in to your test sites without ever reading the password.

  • Encrypted hereApple Keychain on macOS. DPAPI or your system keyring plus a Vault passphrase on Windows and Linux.
  • Agents seeThe login name, ID and your notes. Never the password.
  • Off by defaultNew logins start with agent access off. You choose which ones agents can use.

Remote control

Your phone, sealed end to end.

Check and steer tasks from your phone or another computer. Everything between them is encrypted on your devices.

Your computer

Holds the keys

Task #128, running

Fix the login redirect on staging

Codex, 4 files changed

Tasks and history in a local database.

VibeiDE relay

No keys

Passes the sealed message on. Cannot read it or change it.

Your phone or other computer

Holds the keys

Task #128, running

Fix the login redirect on staging

Codex, 4 files changed

Paired by you, one device at a time.

The same task update, as each of the three sees it.

  • Paired by a code

    Check that the code matches on both screens. Keys are made on your devices and never leave them.

  • A relay without keys

    Our server passes sealed messages on. It cannot read them.

  • Tamper-proof

    A changed message is rejected by your device.

Pairing a device

When pairing a phone or another computer, check that the code matches on both screens before you approve. The secret keys are created on your devices and never leave them. If the codes differ, cancel pairing.

What our server sees

It connects two of your devices and passes encrypted messages between them. Without the keys it cannot read them, and a changed message is rejected.

Our server sees

  • Your account and plan
  • Which of your devices are online
  • When a sealed message passes through

Our server never sees

  • Task names, prompts and replies
  • Code, diffs and terminal output
  • Your Claude Code and Codex logins
  • Saved Vault logins

Company mode

Teams share live progress the same way: sealed on one computer, opened on another.

  • Encrypted before storage

    Company mode is encrypted on your devices before anything is stored.

  • Managers see activity

    Task names and activity. Never code, prompts or output.

  • Keys on each computer

    Every member’s keys are created on their own devices and never leave them.

Found a security issue?

Email the details and steps to reproduce.

info@vibeide.dev

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 personalization stays off.

With Analytics enabled, retain Google, Microsoft and Reddit ad click identifiers and share download, signup, activation and purchase conversions with the relevant ad provider. No personalized advertising.

Privacy · Cookie inventory