Beta guide

Read this page before you install. It is short on purpose: what the beta is, what to try, what Cyberine puts on your machine, and how to take all of it off again.

What the beta is

A closed beta for a few invited people. It asks you to try two things:

• The five-command first result: npm i -g @cyberine/cli, cyberine doctor, cyberine run "<task>", cyberine digest <id> and cyberine apply <id>. Getting started walks through them.
• The Claude Code plugin: cyberine plugin install, then restart Claude Code or run /reload.

Everything else in the docs works, but it is outside what the beta asks you to try. Use it if you like, and expect rougher edges there.

Platform

macOS on Apple Silicon is the only platform a person has run. Other platforms are published but are not part of the beta. The platform support table in Getting started says what was run where; this page does not repeat it.

What it uses

• Workers are the coding agents you already logged into (claude, codex, muse) and any provider API key you stored with cyberine auth login. Cyberine does not bring its own model access.
• Claude workers run your own claude -p under your own login and draw on your own plan. Cyberine never reads or stores those credentials. The one exception is a Claude account you set up yourself from a token file; see Privacy and licence.
• cyberine run sends the task to every available agent, so it spends subscription quota or provider credits. cyberine route "<task>" previews the same decision for free.
• Cyberine is free for individuals.

The one network call you did not ask for

The terminal UI and the chat (cyberine agents, cyberine tui, cyberine chat) check once a day whether a newer version exists. The check is one plain GET to the npm registry for the installed package. It sends no prompts, no usage data and no identifiers beyond the request itself. The result is cached in update-check.json under your Cyberine home, and the check never installs anything.

Turn it off completely, with no network call and no cache read or write, by setting this in your shell profile:

export CYBERINE_NO_UPDATE_CHECK=1

Privacy and licence lists every other connection Cyberine can make and what turns each on.

Upgrade

The beta ships under the npm latest tag, and the version beta users get is 0.3.0. The install command is also the upgrade command:

npm i -g @cyberine/cli
cyberine --version

cyberine --version prints the version you run. npm ls -g @cyberine/cli prints the version npm installed.

The plugin link points into the installed package, so an upgrade carries it along. Restart Claude Code or run /reload afterwards. If you ran cyberine init in a repo, run cyberine sync there once after the upgrade: it brings the generated rule files to the new version and leaves policy files you edited alone.

Remove

There is no single uninstall command. Cyberine puts files in a few places, and the steps below take each one off. Run them in this order, because steps 1 and 2 use the cyberine command and step 4 removes it.

1. Remove what Cyberine left in each repo you used it in. Which of these exist depends on what you ran:

   Path in the repo	Created by	What to do
   .local/runs/	cyberine run	Delete it. It holds the run history, including the candidate diffs.
   .local/tasks/	cyberine init, cyberine tasks	Delete it. It holds the task board and its drafts.
   .cyberine/	cyberine init, the plugin's compaction hook	Delete it. config.json, config.local.json and fleet.json come from init; handoffs/ can also appear in any git repo where the plugin was loaded and Claude Code compacted a session.
   .claude/rules/cyberine-*.md	cyberine init	Delete those files. They are the rules and policies init wrote.
   .claude/settings.local.json	cyberine init	Open it (.claude/settings.json if the repo used init --track) and delete only the hooks whose command is cyberine tasks guard (under PreToolUse) or cyberine handoff pointer (under SessionStart). The file may hold your own settings.
   <!-- cyberine:begin ... --> blocks in AGENTS.md, and AGENTS.override.md	cyberine init when AGENTS.md exists	Delete each block from its begin line through its end line. Delete AGENTS.override.md; it is generated.
   the block that starts # Cyberine: personal and runtime state	cyberine init, cyberine sync	Delete that line and the ignore lines under it, from .git/info/exclude or .gitignore, whichever holds them. A bare .local/ line or an AGENTS.override.md line may sit elsewhere in the same file.
   .claude/worktrees/cyberine-*	a run that was interrupted	cyberine reap --worktrees lists them, and cyberine reap --worktrees --apply removes the safe ones.

2. Remove what you registered, only the lines that apply to you:

   cyberine serve uninstall
   cyberine account remove <key>
   claude mcp remove cyberine
   codex plugin remove cyberine@cyberine-local
   codex plugin marketplace remove cyberine-local

   cyberine serve uninstall removes the background agent that cyberine serve install registers: the launchd job com.cyberine.loop on macOS, the systemd user unit cyberine-loop.service on Linux. cyberine account remove <key> drops an account you added with cyberine account add and the claude-<key> link it made in ~/.local/bin; its entry lives in ~/.claude-profiles/accounts.json, and the profile folder stays unless you add --purge. claude mcp remove cyberine undoes cyberine mcp install. The two codex lines undo cyberine plugin install --harness codex. The Copilot install (--harness copilot) has no Cyberine removal verb: use Copilot's own plugin commands. A beta user who only ran the five commands and the plugin step needs none of these.

3. Remove the Claude Code plugin link:

   rm -r ~/.claude/skills/cyberine

   cyberine plugin install creates this one link, to the plugin folder inside the installed package. rm -r removes the link only. If you installed with --copy, it is a real folder and rm -r removes it. If CYBERINE_SKILLS_DIR was set when you installed, the link is in that folder instead. If you also ran cyberine skill install <id>, delete the ~/.claude/skills/cyberine-<id> folders it copied. Skip this step and the link stays behind, pointing at a folder npm has deleted.

4. Remove the command:

   npm uninstall -g @cyberine/cli

   This removes the launcher (cyberine, cyberine-mcp, cyberine-handoff, cyberine-tasks-banner). The prebuilt binary for your platform is a dependency of the launcher, so npm should remove it too. Check with npm ls -g --depth=0: neither @cyberine/cli nor @cyberine/cli-darwin-arm64 should be listed. If the binary package is still listed, run npm uninstall -g @cyberine/cli-darwin-arm64.

5. Remove the Cyberine home:

   rm -r ~/.cyberine

   The folder appears on first real use, so it may not exist yet. If CYBERINE_HOME is set, the folder is the one it names. It holds your saved provider keys (.env, written by cyberine auth login), the index of past runs, chat sessions, your global fleet.json and config.json, the update-check cache and the Codex plugin folder. Deleting it deletes those keys from this machine only. A key stays valid at its provider until you revoke it there.

This is every place the source writes to that this page found. Cyberine installs no notifier app or login item, and registers a background service only if you ran cyberine serve install.

Known limits

• cyberine run and cyberine apply need a git repository with at least one commit.
• A code run leaves a winning diff, not an edited tree. Read it with cyberine digest <id>, then land it with cyberine apply <id>.
• Each candidate diff is applied and typechecked before it can win. In a repo with no typecheck script and no verify command set, the diff is only applied, and cyberine digest prints applied, verification skipped next to the winner.
• The plugin loads from a link in ~/.claude/skills. Claude Code must be restarted or reloaded after cyberine plugin install.
• cyberine run, cyberine draft, cyberine research and cyberine autopilot spend provider or subscription quota. route, digest, apply, doctor, setup --status, tasks and next do not.
• Windows is published but has never been run, and Alpine and other musl Linux images are unsupported.

Report a problem

The "Report a bug" section of the README says where to send a report and what to include. The @cyberine/cli page on npm carries the same section. Include the output of cyberine --version and cyberine doctor, your platform, what you ran and what happened, and leave out keys and tokens. Report a security issue as SECURITY.md describes.