Control your AI sessions
from anywhere.
Be the first to know when we launch. Join the waitlist.
// Claude is thinking... async function syncSession(id) { const conn = await openSocket(id) return conn.stream() }
Built for developers who code with AI
- VS Code
- Claude
- GitHub
Everything you need, remotely
A set of focused tools that keep you connected to every AI coding session — whether you're at your desk, on the couch, or on the move.
Real-time session sync
Every message from your AI assistant appears instantly on your phone. Follow the reasoning without sitting at your desk.
01Remote action approval
Your AI wants to run a command or edit a file? Approve or reject directly from your phone — you stay in control, always.
02Send prompts remotely
Type a new instruction from anywhere. VibeSync injects it directly into the active AI coding session.
03QR code pairing
Pair your phone with VS Code in seconds. Scan the QR code from the extension sidebar — no accounts to configure manually.
04Push notifications
Get notified when your AI needs your approval or finishes a task. Never miss a moment of your coding session.
05Multi-device support
Connect multiple phones to a single VS Code instance. Perfect for switching between personal and work devices.
06
Up and running in 3 steps
No servers to set up. No accounts to manage. Install, scan, sync.
- 01
Install the extension
Add VibeSync to VS Code from the Marketplace. Sign in with GitHub or Google — takes under a minute.
Extensions: MarketplaceVSVibeSyncControl AI coding from your phone★ 4.9·12k installs - 02
Pair your phone
Open the VibeSync app, tap 'Scan QR Code', and point at the code shown in the VS Code sidebar.
- 03
Stay in sync
Start an AI coding session. Everything appears on your phone in real time — messages, actions, status.
VibeSyncnowAI needs approvalRun: pnpm test — tap to reviewSession synced · 34ms latency
Your code stays yours.
VibeSync uses OAuth2 + JWT with 15-minute access tokens, refresh token rotation, and end-to-end encryption. Your sessions are never stored unencrypted. HMAC-signed OAuth state prevents CSRF attacks.
- OAuth2 via GitHub & Google
- HMAC-signed state — CSRF protected
- JWT access tokens (15 min) + rotation
- Tokens never in URLs or logs
- HTTPS/WSS enforced in production
- Audit log for every action