Plan the outcome.
Choose a repository, model, permission mode, dependency, or decompose a larger job into an editable sequence.
ALPHAWindows early access is available→
The supervision layer for Claude Code
Parallel agents.One accountable workflow.
Run Claude Code sessions in isolated worktrees, bring only important decisions to your attention, and ship after the evidence is green.
Windows 10/11 · 64-bit · Automatic updates
✓ Runs locally✓ Uses your Claude login✓ Git-native isolation
Claude Code stays the agent. Orvisor makes the workflow observable and accountable.
ISOLATESUPERVISEVERIFYSHIP
Not another coding agent
Claude Code writes the code. Orvisor runs the operation.
Orvisor keeps the CLI, account, configuration, commands, skills, hooks, and plugins you already use. It adds the missing control plane around multiple concurrent sessions.
Claude CodeReason · edit · run tools
+OrvisorIsolate · queue · approve · review · ship
One path from intent to evidence
Delegate the work. Keep the judgment.
Supervise the exceptions.
Live output is always available. Orvisor pulls you in for questions, risky actions, failed checks, conflicts, and budget limits—not every token.
Review, then ship.
Read the diff, inspect findings and checks, then merge locally or open a GitHub PR from the same decision surface.
Designed around engineering reality
Agent speed needs operating discipline.
Orvisor coordinates the isolation, attention, evidence, sequencing, and memory around Claude Code so parallel work remains understandable when the novelty wears off.
01Isolated execution
Parallel work without shared-state chaos.
Run multiple Claude Code sessions at once. Each task gets an isolated git worktree, branch, live output, and resumable history.
02Attention routing
See the exception, not every token.
Orvisor scores tool risk and pauses sensitive operations for an explicit allow or deny—without leaving a terminal prompt hanging.
03Evidence-driven review
Ship the change you actually inspected.
Review diffs, AI findings, quality-gate output, conflicts, and commit readiness in one decision surface before you merge or open a PR.
04Dependency-aware queue
Turn a plan into the right execution order.
Queue tasks behind running work or completed merges. New worktrees branch at start time, so dependent tasks inherit the right base.
05Operational visibility
Know what is running and what it costs.
Track fresh, cached, and output tokens; live cost estimates; per-session caps; run duration; and model-level usage without guesswork.
06Verified project memory
Let the next session inherit what survived review.
Capture decisions, gotchas, and code-grounded insights. Stale knowledge is quarantined until current code verifies it again.
Control is a product feature
Fast by default. Deliberate at the boundary.
Orvisor keeps orchestration on your machine, separates concurrent work with git, and makes high-impact actions visible before they happen.
- 01Explicit permission boundaries
Risk-scored tool calls pause for a human decision.
- 02Local by default
The desktop service binds to your machine and stores product state locally.
- 03Checks come from the base repo
Agent-edited gate definitions are flagged instead of trusted.
- 04Active work survives lifecycle events
Updates, restarts, crashes, and uninstall flows are designed around preservation.
Project memory with receipts
The next session should not start from zero.
Orvisor turns completed work into searchable decisions, conventions, and gotchas. It verifies that knowledge against the code before another agent receives it.
- Grounded in code
Insights cite repository files and carry git content fingerprints.
- Stale means quarantined
Changed evidence moves a note into verify-first context instead of presenting it as fact.
- Shared on purpose
Opt-in JSONL sharing keeps repo knowledge portable without exporting machine-local data.
Promote a proven convention into CLAUDE.md when it should become a durable repository rule.
The depth behind the dashboard
Built for the full agent lifecycle.
The board is the overview. Underneath it is a set of operational controls for starting, supervising, verifying, and shipping agent work without losing the git workflow you trust.
Orchestrate
- Isolated git worktrees
A branch and working directory for every parallel session.
- Dependency-aware queue
Start now, when a slot opens, or after another session merges.
- Task decomposition
Turn one large outcome into editable, sequenced subtasks.
- Session quick-switch
Move across the active fleet without returning to the board.
Supervise
- Risk-scored approvals
Sensitive tool calls pause with context and explicit allow or deny.
- Durable agent questions
Questions free the run slot and resume the same conversation after your answer.
- Token and cost limits
Live accounting, honest cache splits, and per-session runaway protection.
- Native notifications
Approvals, questions, completion, and failures reach the Windows desktop.
Verify
- GitHub-style change review
File navigation, viewed progress, inline patches, and bounded large diffs.
- Repository-owned gates
Run the project's real checks without trusting agent-edited definitions.
- AI pre-review
Compare the final diff with the original task and pin findings to files.
- Conflict radar
See overlapping work early and let a session sync, resolve, and re-test.
Ship & improve
- Auto-merge when green
Opt in only when real checks provide evidence and the merge is conflict-free.
- Bounded fix-it loop
Retry failed checks under budgets, deny lists, diff caps, and rollback rules.
- Best-of-N attempts
Race independent solutions, compare evidence, and choose the winner yourself.
- Complete GitHub PR lifecycle
Open, monitor, update, and clean up pull requests from the same session.
Want the complete product tour?
Explore all features See how these systems work together across real agent workflows.
Windows early access
Give every agent a workspace. Give yourself a control plane.
Keep your existing Claude Code account and configuration. Install Orvisor once; future alpha updates arrive through the built-in update channel.
- Platform
- Windows 10/11 · x64
- Requires
- Git 2.38+ · Claude Code
- Channel
- Alpha · Auto-updating
Early-access builds are currently test-signed. Windows may show an unknown-publisher warning until production code signing is enabled.
Before you install
Questions, answered plainly.
01Does Orvisor replace Claude Code?+
No. Orvisor works with the Claude Code CLI you already use. Your Claude account, authentication, configuration, commands, skills, agents, and plugins remain part of Claude Code; Orvisor coordinates the sessions around it.
02What do I need before installing?+
You need a 64-bit Windows 10 or Windows 11 computer, Git for Windows 2.38 or newer, and Claude Code installed, available on PATH, and signed in. First-run onboarding checks these prerequisites and explains how to resolve anything missing.
03Where does Orvisor run?+
The desktop interface, orchestration service, session history, settings, logs, backups, and SQLite database run on your computer. Orvisor is not a hosted control plane.
04Can Orvisor open GitHub pull requests?+
Yes. Optional GitHub mode can push the session branch, open a pull request, monitor checks and status, retain PR history, and support follow-up commits. You configure the GitHub identity used for each repository.
05How do updates work?+
Installed builds check their configured release channel in the background. When an update is available, Orvisor downloads it and asks you to restart when it is safe to apply.
Looking for installation, privacy, workflow, or update details?
Browse all questions