Fork Orca into packages/ide as first-party code, and rename its config and CLI identifiers to CoDev

[yousef20920]

Makes the IDE first-party code in this monorepo, then renames the identifiers a
person actually types or sees on disk.

The diff is enormous (~11.3k files) but almost all of it is one mechanical move:
the IDE source landing in packages/ide. Review the last three commits; skim
the first.

Why

The IDE was vendored. Every build cloned stablyai/orca at a pinned tag and
re-applied a 13k-line codev-web.patch over it. That made CoDev's own IDE work
invisible in the tree, unreviewable in diffs, and reconcilable only as patch
hunks — and it left "Orca" as the name on config files, the CLI, and the pairing
scheme.

The commits

f16a5720	Fork Orca into packages/ide as first-party code
ca5de8d8	Rename the config directory and project config
3296835b	Rename the plugin manifest, pairing scheme, and CLI
43837979	Record what was renamed and what deliberately was not

1. The fork

Mechanical and byte-exact: the patched upstream tree at the pinned commit
02cea8a became packages/ide verbatim, so no CoDev edit was rewritten or
redone. Rebuilding the web client from the new location reproduces the
committed bundle with identical content hashes and zero diff under
apps/web/public/orca — proof this changed no behavior.

Both artifacts now build from that one directory, which keeps them on the same
version by construction: pnpm orca:web (browser client) and
build-orca-serve.sh (the backend — the Containerfile now COPYs the source as
build context instead of cloning it).

packages/ide stays a self-contained project rather than joining the workspace:
it declares its own pnpm-workspace.yaml (packages: []), lockfile,
patchedDependencies, and an Electron native-rebuild postinstall — exactly the
carve-out upstream already made for itself. The root workspace excludes it and
.prettierignore skips it, so the recursive build/lint/typecheck/test
scripts and Prettier don't sweep ~11k IDE sources into every CI run; it formats
with its own oxfmt and lints with its own oxlint.

Trimmed at fork time, since no build consumes them and electron-builder already
excluded three of them from the packaged app: mobile/ (a separate workspace),
docs/, examples/, Casks/, .github/.

Accepted trade-off: upstream Orca fixes are no longer a version bump. Taking
one now means reading their diff and porting it by hand into a diverged tree.

2–3. The rename

Was	Now	Old name still works?
~/.orca	~/.codev	an existing ~/.orca keeps being used
<repo>/.orca/	<repo>/.codev/	read, and cleared on delete
orca.yaml	codev.yaml	read
orca-plugin.json	codev-plugin.json	read
orca://pair	codev://pair	parsed — IDE, renderer, and apps/web
orca / orca-ide	codev	kept as bin aliases; still probed and detected

Every reader accepts both names, so nothing has to migrate and no deploy has
to be coordinated. Only what is written and displayed uses the CoDev name.
src/shared/codev-identifiers.ts holds both sets.

Neither name was centralized before — 15 call sites each hand-built
join(home, '.orca', …) or join(repoPath, 'orca.yaml'), and ten remote hook
installers each had their own copy of the path — so this also collapses them
onto shared helpers.

~/.orca is not moved when it already exists: agent hooks record absolute
script paths in Claude/Codex config, so relocating the directory would break
hooks installed before this change. Fresh installs get ~/.codev.

What reviewers should look at

Three things are deliberately not renamed, each with a test pinning it:

1. source: 'orca.yaml' in orca-runtime.ts is a host→client wire
   discriminant. Per AGENTS.md remote-wire-compatibility, mixed client/host
   versions are the normal state and an older paired client would not understand
   a new token. Invisible to users; the filename displayed beside it is renamed.
2. Remote launches keep the pre-rename shim name. The relay deploys the CLI
   as plain orca, so getTuiAgentLaunchCommand now routes remote launches
   through a separate remoteLaunchCmdByPlatform. Local launches use codev on
   all three platforms.
3. Package and app identity — productName, the Electron name, the
   com.stablyai.orca bundle id, and the deb/rpm package and artifact names.
   These are tied to code signing, TCC grants, update channels, and the userData
   directory, so renaming them would orphan user data rather than rename a
   command. Linux executableName is the command a person types, so that one
   did change — orca-ide existed only to dodge Ubuntu's GNOME Orca package, a
   conflict codev doesn't have.

detectCmdAliases gained the new names rather than swapping them, so a session
started by an older build is still detected.

Verification

• IDE suite at exact parity with the pre-fork baseline: 24 failing files / 65
  failing tests before and after, identical failure set, 47,213 passing. Those
  24 are pre-existing — they need a built Electron runtime.
• typecheck (node + cli + web), repo format:check, lint, and pnpm install --frozen-lockfile (lockfile unchanged) all pass.
• Web client rebuilds from packages/ide to a byte-identical bundle.
• The infra suite gained a test asserting neither build script nor the
  Containerfile can reintroduce an upstream clone.

One unrelated fix rode along. apps/web/components/sign-in-layout.test.ts
was already failing on main: it still expected initialMode={mode === "sign-up" inline, but the waitlist-invite work (e8c993dc) moved that behind
startInSignUp, which is true for ?mode=sign-up or a valid invite grant.
The page has been correct the whole time; only the test was stale. This PR
didn't cause it and doesn't depend on it, but verify can't go green without
it, so the assertion now checks both the derivation and the prop. The full
recursive suite passes: apps/web 458, packages/contracts 31,
apps/hocuspocus-server 8.

Not verified here: Linux deb/rpm packaging output, which needs an
electron-builder run this environment cannot do. The packaging config's own
contract test passes.

Still to do

Display copy, not identifiers. infra/aws/orca-build/brand-web.mjs still
rewrites Orca → CoDev in the built bundle after the fact, and the
non-English locale bundles (es/ja/ko/zh, ~600 occurrences each) are
untouched. Folding that into the source is now ordinary editing.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
codev	Ready	Preview	Aug 30, 2026 9:02pm

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.