Verity
Secure control plane for coding agents

Run your coding agents from one place.

Claude Code and Codex, plus open-source models through OpenCode — running in isolated project sandboxes and parallel worktrees, with your history on your server.

Early access details
Parallel coding-agent sessions running on iPad and iPhone

Parallel without collisions

Every session gets its own branch and clean worktree.

Claude and Codex credentials stay outside

Signing keys and infrastructure access stay brokered outside.

Your infrastructure. Isolated execution.

Agents run in project sandboxes with the assigned workspace mounted for development.

Built for real development

Agent speed. Professional safeguards.

Verity keeps the workflow you already trust — branches, CI, review, and secrets — while your agents do the work.

01

Run the fleet in parallel.

Start several agents on the same repository. Isolated worktrees keep their branches clean and their changes apart.

Worktrees Attention queue
02

Review and ship safely.

Every agent branch passes secret scanning and an isolated code review. Follow PR and CI state in the thread, then merge when the required checks are complete.

Gitleaks secret scan Isolated code review PR + CI gates
03

Use the best model. Stay ahead of limits.

Move between Claude Code and Codex — or connect open-source models through OpenCode. Verity keeps your history and paid-plan usage in view before a limit interrupts the work.

Claude + Codex Open-source via OpenCode Subscription usage Google Drive import File browser
Secure by design · Supply-chain protection

Keep Claude and Codex credentials outside agent runtimes.

Run Verity on a workstation, dedicated server, or private cloud. Isolated project containers and external credential boundaries reduce the blast radius of software supply-chain attacks. Claude and Codex provider requests cross a brokered gateway; signing and infrastructure actions are brokered outside the project runtime. OpenCode is supported separately and is not covered by this credential-isolation claim.

On brokered Claude and Codex paths, a compromised dependency may reach the sandbox — but it finds no reusable provider credential.
✓ Claude and Codex tokens stay behind the broker
✓ Commit signing key stays outside
✓ Git push and infrastructure access are brokered
✓ Secret-manager and database credentials stay server-side

Put your agent fleet under control.

Verity is rolling out to early users in waves. Public signup is not open yet.