vibeke
↑ ↓ navigate · ↵ openesc to close
A terminal workspace for coding agents

Run your agents.
Keep control.

Run Claude Code, Codex, and other agent CLIs in one workspace. Reconnect to the same processes after you disconnect. Answer agent requests from the inbox.

Install Vibeke Read the docs

macOS + Linux / Rust / Apache-2.0

~/ One session. Three ways to connect.

Read the conversation. Review the changes.

Screenshots with sample data.
Electron app
Vibeke desktop app with a workspace list, agent conversation, and changed files.
Agent integrations
✳ Claude Code Codexπ pi / ompIntegration details
01 / While the agents run

Find the agent
that needs an answer.

Claude edits a test. Codex reviews a diff. When an agent needs an answer, the inbox shows its request and task.

[01]

Answer agent requests.

Read permission requests and questions in the inbox. Send your answer through the agent integration.

Claude hooks · Codex RPC · pi extension
How interactions work
[02]

Restart the server.

A holder process owns each terminal. If the server stops, the holder keeps the agent process active. The new server reconnects.

one holder process per pane
What survives a restart
[03]

Use separate worktrees.

Use a separate branch for each task. Review the task diff and check results before you accept the work.

separate branches · reviewable diffs
Tasks and review
02 / From your shell

Start locally.
Attach over SSH.

Start a workspace.

Run Vibeke. Create a workspace for your repository. Start an agent. Close the terminal to disconnect. Run Vibeke again to reconnect.

Follow the guide
~/workspace — local
# Attach the terminal workspacevibeke # From another shell, in your projectvibeke workspace create .vibeke agent start builder --harness claude
Host mode uses your permissions. Use a supported sandbox, container, or VM to limit access.
03 / Comparison

How it compares.

Compare the features

Compare Vibeke with other terminal tools and agent apps. The table covers agent control, remote access, browser tools, and review.

Transfer work between hosts.

Copy code changes and an available agent conversation to another paired host.

Share work with a teammate.

Transfer work to their host, or give them view or approval access.

Control the browser.

Open a browser pane. View the agent session and take control when necessary.

Compare 29 features
04 / Documentation

Start with
one workspace.

Use the quickstart to start your first agent. The reference lists commands, API methods, and configuration settings from the code.

Open the docs

Start your first workspace

Install Vibeke. Start an agent. Reconnect to the session.

How the runtime works

Agent processes, requests, and tasks.

CLI reference

Commands and configuration, from the code.

Before you install

Common questions.

Does Vibeke replace my agent?+

No. Vibeke provides the workspace. Use your existing agents and model accounts. Claude Code, Codex, and pi/omp support structured integrations. Features depend on the agent.

What survives a restart?+

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.

Does every task run in a sandbox?+

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.

Can I try it alongside Herdr?+

Yes. Import supported configuration and layouts into Vibeke. Herdr processes remain in Herdr. Use the dry-run command in the migration guide first.

Try it in one project.

Start an agent. Disconnect. Reconnect to the same session.

Install Vibeke