Know which agent needs you.
Keep agent questions and permission requests in one inbox. Answer through the supported agent integration.
Bring Claude Code, Codex, and your other agent CLIs into one workspace. Run them on your laptop or an SSH host. Pair your phone to answer supported requests.
Open source · Apache-2.0 · v0.22.0

Run Claude, Codex, or any agent in the terminal you already use. When a supported agent needs permission, the request waits in one inbox. Away from your desk? Approve it from your phone. The agent continues in your terminal. Your agents keep working, wherever you are.
vibeke in its directory. Complete first-run setup.claude, codex, or your usual command inside the pane.Install minisign first: brew install minisign on macOS, or use your Linux package manager.
curl -fsSL https://vibeke.dev/install.sh | shcd your-projectvibekeClaude edits a test. Codex reviews a diff. When an agent needs an answer, the inbox shows its request and task.
Keep agent questions and permission requests in one inbox. Answer through the supported agent integration.
Agents keep running after a client disconnect or server restart. A host restart stops the processes.
Use a separate worktree for each task. Review its changes and check results before you accept the work.
Pair your phone with a running host. Read an agent request, then allow or deny it. Your agent keeps working on the host.
Watch phone approvalsRequests depend on the agent integration. The host must stay awake and connected. Read the guide
Run an app on an SSH host. Open its preview beside your agent in your local terminal.
Watch a remote previewBrowser panes need Chromium and a terminal that supports graphics. Read the guide
Name a pane @reviewer. Send it a request from another agent pane in the same workspace.
@reviewer please check the changes in src/auth.rs
Mentions work with Claude Code and Codex integrations. Messages wait until the receiving agent is idle.
Set up agent mentionsThe notes include the selected element and a screenshot. They wait while the agent is busy.
Use page annotationsStart in your terminal. Add the desktop app or pair your browser with the running host when you want another view.
Run agents in your terminal.
Available for macOS, Linux, and Windows. The desktop app connects to a host. Local use also requires the CLI. Windows connects to a supported remote host.
Download desktopOpen Devices on the host, then choose Pair a phone. Confirm the pairing to connect. Your host must stay awake and online.
Watch agents work in the terminal on two machines. Preview a dev server. Hand work to another computer. Answer requests from the desktop app and a phone. The video uses sample data.
Start Vibeke in your project. Complete setup, then run your usual agent command in a pane. Use the command palette for workspaces, splits, and the inbox.
# In your project directorycd your-projectvibeke # Inside a Vibeke paneclaude # or codex, pi, ompCompare Vibeke with other terminal tools and agent apps. The table covers agent control, remote access, browser tools, and review.
Copy code changes and an available agent conversation to another paired host.
Transfer work to their host, or give them view or approval access.
Open a browser pane. View the agent session and take control when necessary.
Use the quickstart to start your first agent. The reference lists commands, API methods, and configuration settings.
Open the docsThe host CLI runs on macOS 13 or later and Linux. macOS supports Apple silicon and Intel. Linux supports x86_64 and ARM64. The Windows desktop app connects to a supported remote host.
Yes. Run your usual agent commands in a pane. Agent and model charges remain with your providers. Structured requests and other features depend on the integration.
Both connect to a running Vibeke host. The desktop app does not bundle the CLI. Install the CLI for local use, or pair with a remote host. Pair your browser or phone from the host.
Holder processes keep agents active after a server restart or client disconnect. Screen recovery can be incomplete. A host restart or holder failure stops the processes.
No. Host mode uses your permissions. Use a supported sandbox, container, or VM to limit access. Worktrees separate file changes. They do not prevent access.

Start with one project and your usual agent.
Want to come back later? Save the repository with a star.