Vibe Inject

Types your Vibe answers straight into the live Claude Code session in your terminal — no clone, no copy‑paste.

Vibe lets a running Claude Code session ask you a question (vibe_ask) and notify you on your phone or Mac. You answer remotely — tap A/B/C, type, or dictate. This extension is the last hop: it finds the terminal that belongs to that session and types your answer into the live process, exactly as if you'd typed it yourself. The session reads it as its next prompt and keeps going — as if you never left.

It uses VS Code's supported terminal.sendText() primitive (raw TIOCSTI is blocked on modern macOS), so there's no clone, no lock, and no fragile resume machinery.

What it does

• Answer injection — delivers your Vibe answer (decision or free text) into the matching live session.
• Alert replies — types replies to session alerts back into the terminal.
• New sessions — when you start a session from the Vibe app, it opens a terminal in the chosen folder, launches claude, and types the first prompt.

The session ↔ terminal match is done via tty (Vibe's hooks write ~/.claude-ask/terminals/<session>.json); the extension never reads your code or workspace contents.

Requirements

• macOS (the tty‑based terminal match is macOS‑only).
• VS Code — or a fork that can install this extension: Cursor, Windsurf, VSCodium (via Open VSX).
• A Vibe account + the on‑machine setup (MCP tool + hooks). See davedinapoli.de/vibe.

Connecting it to Vibe

The extension needs your Vibe project URL, publishable key and personal token. It looks for them in this order (first source that has a value wins, per key):

1. Environment variables — VIBE_API_TOKEN, VIBE_SUPABASE_URL, VIBE_PUBLISHABLE_KEY, VIBE_FORCE_EDGE, VIBE_EDGE_URL.
2. ~/.vibe/config.json — the recommended way. Same key names as below:

   {
     "vibeSupabaseUrl": "https://<your-project>.supabase.co",
     "vibePublishableKey": "<publishable-key>",
     "vibeApiToken": "vibe_sk_…",
     "vibeForceEdge": true
   }
   

3. VS Code settings — vibe.apiToken, vibe.supabaseUrl, vibe.publishableKey, vibe.forceEdge, vibe.edgeUrl (Settings → search "Vibe").

You'll find your token (vibe_sk_…), URL and key in the Vibe app. The values you need are issued per account — nothing here is shared or hard‑coded.

Usage

It runs automatically (onStartupFinished) and polls quietly in the background. Two commands are available from the Command Palette:

• Vibe: Injection an/aus — pause/resume injection.
• Vibe: Log anzeigen — open the activity log (Output → "Vibe Inject").

Privacy

The extension polls your Vibe backend for answers addressed to sessions on this machine and types them into the matching terminal. It reads only the Vibe config and the session‑mapping files it created; it does not read, upload, or transmit your workspace files or source code.

License

MIT © Dave Di Napoli — see the bundled LICENSE file.