Traffic runtime for coding agents
macOS + Linux preview · v0.1.1
See and control how Claude Code and Codex CLI connect to AI services.
Capture → decide → send, with one Turn of shared context.
PRODUCT TOUR
These screens use deterministic preview data: the complete product interface, without exposing a live credential or conversation.
Keep the conversation, frozen routing decision, model request, and outcome in one readable timeline.
Open retained HTTP boundaries only when needed, with redacted diagnostics and exact test samples close at hand.
Bind client protocols and origins to the intended upstream service, account, and policy revision.
Start from readable built-ins, edit in a bounded sandbox, and test before creating a saved copy.
Review calls and protocol-declared tokens by runtime user without pretending partial evidence is billing data.
Install
Supported path: macOS 14+ App · Linux x86-64/ARM64 Server + Web
macOS 14+ · Apple silicon and Intel
Install one App with the local Runtime included. Start Claude or Codex with the vibermate command, or open the browser address shown under Settings → Team access on the same Mac.
brew install --cask vibe-agi/tap/vibermateLinux x86-64 and ARM64
Extract the matching release archive, start the Runtime, then open the printed address with its owner key. Create one Runtime User per person or device under Settings → Team access.
./vibermated server --listen 0.0.0.0:9666 --transport self_signed_tlsThe boundary it owns
01 / 02ViberMate owns the boundary between a coding agent and its AI provider. The macOS App and Linux Web Runtime expose the same capture, routing, account, message-rule, and evidence model to one or many Runtime Users.
What it makes possible
Traffic runtime for coding agentsLaunch Claude Code or Codex from Terminal and inspect the same run in the macOS App or Web workbench.
Choose an Endpoint, account, model mapping, or a bounded JavaScript selector.
Control redaction and retention while keeping provider credentials outside evidence.