Open-source project
Zoo-Code-Org/Zoo-Code avatar
Zoo-Code-Org/Zoo-Code

Zoo Code: the product renamed, the package still called roo-code

Zoo Code gives you a whole dev team of AI agents in your code editor.

2,119 stars349 forksTypeScriptApache-2.0

At a glance

What is it?
Zoo-Code-Org/Zoo-Code is the VS Code extension the Roo Code team continued after Roo wound down active development. Three layers of the rename are finished, one is not, and the build file is where you can see it: the package is still `roo-code`, the environment variables still carry a `ROO_CODE_` prefix, and the mode definitions still live in `.roomodes`.
Who is it for?
This suits an existing Roo Code user who wants the newer model support, the Semble search and the Destructive Command Guard without changing editors, and the migration guide exists for exactly that. It is a poor choice if you need to know which code you are running, because the version that ships is not traceable from the package name.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Zoo-Code-Org/Zoo-Code2,119 ★ · +640
Star history
Repository2026-07-312026-11-15
Zoo-Code-Org/Zoo-Code1.5k2.1k

640 Stars in the last 107 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The package, the env prefix and the mode file all still say Roo

Zoo Code is a continuation, and the file says so plainly: the project continues after the Roo team wound down active Roo Code work to focus on Roomote, with a core team made up of developers who contributed to Roo previously. The rename is complete at the layer a reader sees and incomplete everywhere else. `package.json` still carries the name `roo-code`. The environment sample still heads one block Roo Code Cloud / Local Development and still defines `ROO_CODE_API_URL` and `ROO_CODE_PROVIDER_URL`. The workspace still holds `.roo/`, `.rooignore` and `.roomodes`, the last being where mode definitions live. The sample environment file also commits a live Clerk tenant hostname for local cloud development, and its PostHog key line is a placeholder reading `key-goes-here`. The Roo to Zoo migration guide is published separately, and support for the transition is routed through Discord and Reddit rather than the issue tracker.

engines pins one exact Node patch, and three other files pin versions too

The build configuration states `"node": "22.23.1"` and `"packageManager": "[email protected]"`. The node entry is a bare version rather than a range, so it names one patch release of Node 22 rather than a compatible series, which is a much narrower requirement than the usual `>=22` form and will refuse a host running a different 22.x patch. The package manager is pinned the same way. Two more version declarations sit in the root, `.nvmrc` and `.tool-versions`, so the same constraint is expressed up to four times in the tree in four formats, none of them derived from the one in `package.json` by anything visible. The mismatch has a practical shape: a contributor whose editor reads `.nvmrc` and a CI runner that reads `engines` can disagree about the same repository without either being wrong.

The same turbo flag string is repeated on ten scripts

Almost every top level script is a turbo passthrough with an identical tail, `--log-order grouped --output-logs new-only`, applied to `lint`, `check-types`, `test`, `test:coverage`, `format`, `build`, `bundle`, `vsix` and the front of `clean`. The same string ten times is a change waiting to happen: fixing the log format means editing ten lines, and there is no shared variable to hold it. Two scripts are more specific. `clean` also removes `dist`, `out`, `bin`, `.vite-port` and `.turbo` with rimraf, and `install:vsix` begins with `pnpm install --frozen-lockfile` followed by that same clean. There is also redundancy at the top: `preinstall`, `install` and `install:all` are three names for the same body, `node scripts/bootstrap.mjs`, so the hook fires from more than one direction.

Task lifecycle invariants are checked by scripts, not by tests

The repository enforces its concurrency and delegation rules with a family of standalone checks rather than a test suite, and one script chains most of them. `lifecycle:model-check` runs checks for task lifecycle, task store concurrency, the provider handoff scheduler and completion persistence, then shells out to two more protocol checks and a parser scoping check, for eight steps in a single command. Siblings cover the task fanout protocol, the task cleanup protocol, the native tool call parser scoping through a node script, and MCP OAuth integration. Two test scripts target single files with the node test runner: `test:code-qa-ci` on the code QA workflow and `test:mutation-ci` on a Stryker diff script. Alongside them sit `stryker.config.mjs` for mutation testing, `knip.json` for dead export detection, `codecov.yml` for coverage reporting and `.coderabbit.yaml` for review automation. The upshot is that the task and provider layer has its own verification vocabulary, separate from the turbo test task the rest of the packages use.

v3.86.0 stops models inventing line numbers and tasks replaying themselves

The newest release notes are unusually specific about failure modes, which makes them the best part of the file. On models: GPT-6.1 Sol becomes selectable, the output budget for Claude Opus 5.5 is corrected, and DeepSeek V4.1 Flash is available on OpenCode Go. On tasks: the first abort reason is preserved instead of being overwritten, stream abort state is reset per request so one interrupted stream cannot poison the next, and an interrupted task no longer replays subtasks that were already rejected. On tools: streamed tool arguments are kept intact rather than truncated by a partial chunk, MCP tool policy is enforced rather than advisory, and the release explicitly prevents invented line numbers, which is a reference to diff edits that pointed at positions the model had made up. The tag for this release is dated 2026-10-03, eight days after the last recorded push on 2026-09-25, and the previous tags sit at v3.84.0 and v3.82.2.

Semble drops the indexing step, and the guard drops the approval prompt

Two additions change how much setup an autonomous run needs. Semble codebase intelligence is described as on demand semantic code search with automatic setup and no separate indexing workflow, which means the cost normally paid for keeping a code index fresh is removed rather than moved. The Destructive Command Guard, abbreviated DCG, automatically blocks dangerous commands while trusted work continues without repeated approval prompts, and it is what the file credits for longer autonomous runs. Between them sit the Orchestrator changes: safer delegation, parallel task coordination, reliable parent and child task recovery, and better isolation between subtasks and provider profiles, the last of which matters when one agent call can reach a different credential set than the one it was planned under. Workspace control is also expanded, with rules management, per mode MCP restrictions, multi root path controls, model reasoning options and review actions for completion changes.

Eighteen READMEs, and five empty links at the top of the English one

Localisation is done as parallel README files rather than as translated UI strings, and the English file carries a collapsed list of them: Català, Deutsch, Español, Français, हिंदी, Bahasa Indonesia, Italiano, 日本語, 한국어, Nederlands, Polski, Português (BR), Русский, Türkçe, Tiếng Việt, 简体中文 and 繁體中文, which is seventeen translations beside the original. Each lives under `locales/` with its own directory, so seventeen files can drift from the English one at any time and nothing in the build is described as checking them. The top of the English README has the opposite problem: a centred block of five anchor elements pointing at the marketplace listing, X, Discord, Reddit and the issue tracker, none of which contains any link text, so on a rendered Markdown page they produce nothing at all. The one line that does carry text is the one below them, offering Discord for real time help and Reddit for asynchronous answers.

One of the three ways to run it uninstalls your copy first

Local setup is a clone and an install, then one of three run paths, and the third has a side effect worth knowing:

sh
git clone https://github.com/Zoo-Code-Org/Zoo-Code.git
pnpm install

Development mode is F5 in VS Code, which opens a second window with the extension loaded, where webview changes appear immediately and core extension changes hot reload automatically. Automated installation runs `pnpm install:vsix [-y] [--editor=<command>]`, which asks which editor command to use among `code`, `cursor` and `code-insiders`, defaulting to `code`, then uninstalls any existing version of the extension, builds the latest VSIX, installs it and prompts a restart. `-y` skips the confirmations and `--editor=<command>` sets the target, with `cursor` and `code-insiders` given as examples. Manual installation builds with `pnpm vsix` and installs the package yourself. So the same command that refreshes your build is also the command that removes what you had, and a script that calls it unattended needs `-y` and an explicit editor.

Editorial conclusion

This suits an existing Roo Code user who wants the newer model support, the Semble search and the Destructive Command Guard without changing editors, and the migration guide exists for exactly that. It is a poor choice if you need to know which code you are running, because the version that ships is not traceable from the package name. Three things to check before you install. Read the package identity rather than the product name: `package.json` still says `roo-code`, so anything that pins, mirrors or audits by package name will see the old identity, and the environment variables are `ROO_CODE_API_URL` and `ROO_CODE_PROVIDER_URL`. Respect the engine pin, since `node` is set to one exact patch release and pnpm is pinned to a specific version, with `.nvmrc` and `.tool-versions` adding two more places that can disagree. And if you rely on unattended runs, read what the Destructive Command Guard blocks, because it is the feature that decides how much autonomy you can hand over.

Frequently asked questions

How do I build a VSIX of Zoo Code?

Run pnpm install:vsix, which asks which editor command to use among code, cursor and code-insiders and defaults to code. It uninstalls any existing version, builds the VSIX, installs it and prompts a restart. Use -y to skip prompts or --editor=cursor to pick the target.

How do I run the Zoo Code extension in VS Code while developing it?

Clone the repository, run pnpm install, then press F5 in VS Code, or use Run and Start Debugging. That opens a new VS Code window with the extension running, webview changes appear immediately and core extension changes hot reload automatically.

What did Zoo Code add after the Roo Code team stopped active work?

Semble on demand semantic code search with no separate indexing workflow, stronger Orchestrator delegation and task recovery, the Destructive Command Guard for longer autonomous runs, new providers including Zoo Gateway and OpenCode Go, per mode MCP restrictions, and seventeen translated READMEs.

Which modes does Zoo Code provide?

Code Mode for everyday coding, edits and file operations, Architect Mode for systems, specs and migrations, Ask Mode for answers and documentation, Debug Mode for tracing issues and adding logs, plus Custom Modes you build for a team or workflow.

What does the Destructive Command Guard block in Zoo Code?

It automatically blocks dangerous commands while trusted work continues without repeated approval prompts, which is what makes longer autonomous runs practical. The release notes for v3.86.0 also add enforcement of MCP tool policy and a fix preventing invented line numbers in edits.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zoo-code-org-zoo-code.svg)](https://hysenlabs.com/projects/zoo-code-org-zoo-code)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zoo-code-org-zoo-code.svg)](https://hysenlabs.com/projects/zoo-code-org-zoo-code)

Was this useful?