Know where the tokens went.
Fresh input, cache reads, cache writes, and output stay separate. Track live cost, by-day and by-model statistics, rolling ceilings, and per-session token caps.
live estimate · 94% cached inputComplete product tour
Orvisor does not replace Claude Code. It provides the operational system around many sessions: isolation, attention, evidence, memory, and a deliberate path to merge.
01 · Parallel by construction
Orvisor gives concurrent Claude Code sessions separate git worktrees and branches, then brings their live state into one board. Resume work, jump between sessions, or turn one large task into a dependency-ordered queue.
02 · Human attention, routed
Risky tool calls become contextual approval requests. Agent questions become durable interactions that release a run slot and resume the preserved conversation after you answer—even after an Orvisor restart.
03 · Review before acceptance
Inspect a GitHub-style diff, mark files viewed, read AI findings in context, and run the repository's own checks. Orvisor reads gate definitions from the base repository so an agent cannot quietly rewrite the test it needs to pass.
04 · Autonomy with a contract
Auto-merge requires real evidence and a conflict-free merge. The optional fix-it loop classifies failures, respects attempt and changed-line budgets, blocks sensitive files, verifies the result, and rolls back work that does not improve the gate state.
05 · Memory that earns trust
Project memory records summaries, decisions, conventions, facts, and gotchas with code evidence. Changed files quarantine affected notes. Agents can verify or correct them, teams can share repository-scoped knowledge, and proven rules can graduate into CLAUDE.md.
06 · GitHub without workflow drift
Choose among multiple GitHub identities, push over HTTPS or SSH remotes, open and update pull requests, monitor CI and status, retain PR history, handle divergent branches explicitly, and clean up only the remote branch Orvisor owns.
The systems around the system
Operational details are not secondary in Orvisor. They determine whether parallel agent work remains affordable, recoverable, and understandable over time.
Fresh input, cache reads, cache writes, and output stay separate. Track live cost, by-day and by-model statistics, rolling ceilings, and per-session token caps.
live estimate · 94% cached inputCompare two to five isolated attempts by checks, review findings, diff shape, cost, and duration. Mechanical rank and an optional AI judge stay advisory; you select the winner.
green leader · human mergeSessions use the real Claude Code CLI and existing login. Slash-command discovery mirrors the commands enabled for each repository and passes recognized commands through correctly.
project · user · plugin commandsFirst-run prerequisite checks, native tray and notifications, close-to-tray, launch at login, crash recovery, redacted diagnostics, automatic updates, and preserved local data.
loopback service · SQLite stateStart locally
Orvisor uses your existing Claude Code installation and login. No Node.js installation is required for the Windows desktop app.