The lost question
An agent hits an ambiguity and asks — into a terminal that scrolled past an hour ago. In Zap a question is a durable object: it stays pending until answered, cancelled, or expired, and the conversation keeps moving in parallel.
org.vibevm.zap · local-first agent workspace
Your agents, on one map.
Zap is a local workspace for running coding agents in parallel: projects, conversations, questions, managed work, and Git worktrees on one navigable surface. Zap Wayfinder keeps durable state on your machine; Zap Quick Lens opens it in the browser or Electron. Codex, Claude Code, OpenCode, and Qwen Code connect with the logins you already have.
The problem
The dark between terminals
The shared checkout
Two tasks in one working tree end in stepped-on edits. Zap prepares an owned root worktree per plan and isolated child worktrees per managed task — resume returns to the same worktree, uncommitted edits intact.
Exit 0 — then what?
A clean exit says a process ended, not that the work is right. Zap records process exit, the typed report, and your acceptance as three separate records — success never skips review.
What Zap is
A planning engine with a viewer — not a wrapper
Zap ships as two packages under one discipline. The Rust engine — flow:org.vibevm.zap/zap — keeps one typed durable history: intent, obligations, uncertainty, decisions, lowering, agent packets, execution, evidence, holds, recovery. The client — tool:org.vibevm.zap/lens — is Zap Wayfinder, the local service that owns that state, and Zap Quick Lens, the viewer that renders it. The coordinator may replan inside an Owner-defined envelope, and authority and economics gates stand in front of every live effect.
Your agent CLIsCodex · Claude Code · OpenCode · Qwen Code
Zap Wayfinderdurable journal (SQLite) · questions & inboxes · worktree registry · routing catalog
Zap Quick Lensbrowser · Electron · zap-server headless
Two separate channels: agents authenticate to an exact workspace scope, and a UI login never grants agent authority. Everything binds loopback. Opening or closing a viewer neither starts nor stops agents.
Navigation
A map that refuses to guess
The workspace renders your projects as regions on one pan-and-zoom map, and the plan graph has exactly two readings. Missing members, partial relations, and prerequisite cycles are called out on the graph instead of being smoothed into a plausible-looking order — and coordinates never promise a duration the source did not state.
Capabilities
What that buys you
Questions that survive restarts
Question groups carry choices, multi-select, and free text, with drafts, cancellation, and amendment history. In the recorded acceptance flow, a live agent published a question, the browser answered it, the agent read the answer through a bounded inbox and filed a typed report — and after a Wayfinder restart, all of it was still there.
Integration with a gate
Promotion into your main line passes a candidate diff, registered checks, and human review under a single writer lease. Conflicts become a managed resolution task. There is no automatic stash, reset, or force-push.
Routing you can read
Named configurations over your existing accounts, task specializations, and an economy/quality slider. Subscription meters show the observed reading: an unknown value stays unknown, and percentages are never converted into an invented number of tokens.
Nothing starts implicitly
Registering a project spends zero inference. The coordinator starts when you press Start development. zap-server brings up the whole stack headless without a single model turn.
Trust
Rules Zap refuses to break
- A completed process is not an accepted result.
Exit, typed report, acceptance — three records.
- Unknown stays unknown.
No invented durations, orders, or token counts.
- No demo data in live views.
An unavailable planning source renders as unavailable.
- No bot author.
Commit-producing operations refuse until your Git identity is configured.
- Controls tell the truth.
The UI shows only what the selected provider adapter actually supports.
Start
From zero to a running coordinator
- $
vibe install -g org.vibevm.zap/zapOne global application through vibe. Need vibe first? Install VibeVM →
- $
zap-quicklensReuses or starts the local Wayfinder owner and opens a paired browser session. --electron for the desktop shell, zap-server for headless.
Connect an account you already have
Codex, Claude Code, OpenCode, or Qwen Code — Zap uses that application’s protected login. It does not create accounts and does not sell inference.
Add a project, press Start development
Registration is free of inference. The first model turn happens on Start — not before.
Where it is today
Zap is a local preview: one human, one machine, full journal retained. Gamelens, IDE clients, and multi-person collaboration are named future components — not features of this release. Authoritative planning operations need a configured planning source; a pending source is shown as pending, not simulated.
In the VibeVM family
The engine also installs into a VibeVM project as a flow package, adding its specifications and three skills — zap-draft, zap-state, zap-run. Installation activates nothing until you say so.
Why VibeVM →In one paragraph
Zap puts projects, agent conversations, questions, managed work, and Git worktrees on one local map. Questions survive restarts, integration passes through your review, and nothing spends a model turn until you press Start. Local preview, in the VibeVM family: vibe install -g org.vibevm.zap/zap.