One engineering brain for all your AI coding agents
Qorvyn gives Claude Code, Codex and any coding agent the same cited understanding of your project. Describe a goal; specialist agents plan it, build it, review it and test it. You approve, then the change is delivered. Everything runs on your machine.
$ npx qorvyn initEverything your agents need to work like a team
Bring the agents you already use. Qorvyn adds the shared memory, the process and the safety around them.
Cited project context
An incremental index of your repository. Every agent gets the same answers with path:lines@commit citations, through the CLI, an SDK or MCP.
Describe a goal
A planner turns your goal into a workflow of steps, reusing workflows you already saved. You watch it think, then approve the plan.
Any agent, any model
Claude Code and Codex built in, plus any CLI agent (Cursor, Gemini CLI, Aider, OpenCode) or chat API. Pick the model per agent. Keys are write-only.
Guardrails, enforced
Denied capabilities, protected paths, allowed providers, time limits and approvals for every risky action. Enforced by Qorvyn, not by asking the model nicely.
Safe delivery
Agents commit to their own branches, never your working folder. Get the changes locally, merge, or open and merge pull requests on GitHub, GitLab, Azure DevOps or Bitbucket.
Team sharing, live
Share agents, workflows and knowledge through a server you host. Signed changes, live updates, conflict detection and an offline queue.
From goal to reviewed change in four steps
Qorvyn sets itself up from what your repository already has: CLAUDE.md, AGENTS.md, your existing agents and skills.
Set up
npx qorvyn initindexes the repo and creates read-only agents, workflows and knowledge for you to review.Describe a goal
The planner reads the code, designs the steps and shows the plan before anything runs.
Agents work
Steps run in parallel in isolated worktrees. You see live what each agent reads and changes.
You decide
Review the diff, approve, and deliver: into your branch, or as a pull request.
Your code never leaves your machine
The index, runs, notes and keys live in ~/.qorvyn, outside your repository. A team server receives only what someone chooses to share, signed by their device.
- Installing adds no files to your repository: only the dependency entry.
- Sensitive files (.env, keys, credentials) are never read or indexed.
- API keys are write-only, stored in your OS keychain.
- No telemetry today. Planned stats are opt-out and documented field by field.
# set up the project (local database, index, agents) npx qorvyn init # ask any question about the code, with citations npx qorvyn context search "authentication middleware" # describe a goal: plan, build, review, test npx qorvyn do "rate limit the login endpoint, with tests" # open the dashboard npx qorvyn dashboard
Core for everyone. Enterprise for organizations.
The same product and the same Q. Enterprise is a plugin for your team server, not a fork, so developers keep using Core.
CoreQorvyn Core
- Cited context, CLI, SDK and MCP server
- Agents, workflows, Describe a goal, dashboard
- Any provider and model; write-only keys
- Guardrails and safe delivery to every git host
- Self-hosted team sharing with roles and live sync
EnterpriseQorvyn Enterprise
- Everything in Core
- Organization policies enforced on every device
- SSO group roles and SCIM provisioning (Entra ID, Okta…)
- Audit export, retention and signed SIEM webhooks
- Seats and licenses that work offline
| Capability | Core | Enterprise |
|---|---|---|
| On every developer's machine | ||
| Index, cited search, CLI, SDK, MCP | ✓ | ✓ |
| Agents, workflows, planner, live progress | ✓ | ✓ |
| Providers and models, write-only keys | ✓ | ✓ |
| Guardrails and delivery (GitHub, GitLab, Azure DevOps, Bitbucket) | ✓ | ✓ |
| On the team server | ||
| Workspaces, roles, invitations, live sharing | ✓ | ✓ |
| Sign-in with Microsoft Entra ID, Google, Okta (OIDC) | ✓ | ✓ |
| Organization policies on every device | — | ✓ |
| SSO group roles, SCIM provisioning | — | ✓ |
| Audit export, retention, SIEM webhooks | — | ✓ |
| Seats, deactivation, offline licenses | — | ✓ |
| SAML, high-availability server, hosted cloud | — | Planned |
Up and running in a minute
Needs Node.js 22 or newer. No account, server or database setup. Qorvyn is in early access: ask for access to the package.
- Works with Claude Code and Codex out of the box
- Monorepos understood: apps and packages detected
- Add a team server later; nothing to migrate
npm install -D qorvyn npx qorvyn init npx qorvyn dashboard
Questions, answered
Does Qorvyn replace Claude Code or Codex?
No. Qorvyn works with them. It gives every agent the same project understanding, runs them as specialists in workflows with approvals, and keeps them inside your guardrails.
Does my code leave my machine?
Qorvyn itself never sends your code anywhere. The agents you run talk to their own providers (for example Anthropic or OpenAI) under those providers' terms, with the context Qorvyn chooses: cited snippets, never sensitive files. A team server only receives what you share.
Will it add files to my repository?
No. Only the dependency entry in package.json. Settings and data live in ~/.qorvyn. Agents work in their own worktrees and commit to their own branches.
What is the difference between Core and Enterprise?
Core is the complete product, free and open source, including self-hosted team sharing. Enterprise is a commercial plugin for the team server that adds organization policies, SSO groups, SCIM, audit export and seats. Developers keep using Core.
Do I need a server?
Only to share with teammates. You can run the team server on your own machine to try it, or in your cloud (for example Azure) for the team.
Is there telemetry?
Not today. Planned usage statistics will be anonymous, opt-out, documented field by field, and never include code, file names or prompts.
Give your agents one brain
Start with Core today. Talk to us about Enterprise for your organization.