Answers before you put agents to work.

Orvisor is a Windows desktop control plane for running and supervising multiple Claude Code sessions. It gives each task an isolated workspace and brings live output, approvals, review, and merge decisions into one interface.

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.

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.

No. The Windows installer includes the Orvisor interface, local service, JavaScript runtime, and SQLite module. Git and an authenticated Claude Code installation are the prerequisites you provide.

Each session can run in its own git worktree and Orvisor branch. Those isolated working directories prevent parallel sessions from writing into one shared checkout, while keeping every change available for review.

Orvisor pauses the session and presents the request for your decision. You can review the command, risk information, or question, then allow, deny, or answer it before the session continues.

Yes. Orvisor shows the diff, review findings, repository quality checks, conflicts, and commit status before you choose a merge or pull-request action. A completed session does not silently become an accepted change.

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.

The desktop interface, orchestration service, session history, settings, logs, backups, and SQLite database run on your computer. Orvisor is not a hosted control plane.

Orvisor keeps its product data locally and operates on repositories and worktrees on your machine. Claude Code continues to communicate according to your own Claude Code account and provider configuration.

Claude Code sessions can run commands as your signed-in Windows user, so the permission boundary matters. Orvisor risk-scores tool calls, pauses sensitive operations for a human decision, and keeps parallel changes isolated in worktrees.

Uninstalling the application preserves your database, settings, backups, and worktrees by default. They are removed only when you deliberately choose to delete that data.

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.

No. Orvisor does not restart for an update while a session, approval, or question is active. A downloaded update can be applied after your work is clear or on a later normal launch.

Current early-access builds may use a test-signing identity while production code signing is being completed. Windows cannot establish public publisher trust from that identity, so review the warning before continuing.

Not currently. The first desktop release supports x64 editions of Windows 10 and Windows 11. Other desktop platforms are outside the current version-one scope.