Install into a state directory you can read and remove.

Prerequisites

• A current OpenClaw installation whose Node.js runtime satisfies the OpenClaw CLI requirement: >=22.22.3 <23, >=24.15.0 <25, or >=25.9.0. AGI Super Team itself still supports Node.js 18+, but that applies only to the installer, not to the OpenClaw CLI.
• Node.js 18+ with npx available, and network access to the npm registry.
• A decision about which directory is authoritative: OPENCLAW_STATE_DIR, OPENCLAW_CONFIG_PATH, or the default state directory.
• Permission to write the OpenClaw configuration only if you intend to run --connect.

If you plan to run the optional connect step, back up openclaw.json yourself first. The installer creates its own backup, but a second copy costs nothing and makes the rollback path independent of this tool.

Install step by step

1. Resolve the target rootThe installer resolves the OpenClaw configuration directory in this order: explicit state, then the directory holding an explicitly set configuration file, then the default state. Set OPENCLAW_STATE_DIR and OPENCLAW_CONFIG_PATH together so the answer is unambiguous.
2. Preview without writingRun the command without --install. Every action prints as add, update, or unchanged with an absolute path. Nothing is written.
3. Apply the file changesRerun with --install. Managed targets that already exist are backed up before being replaced. Nothing outside the selected scope is deleted.
4. Connect the configurationAdd --connect to merge the managed agents into your OpenClaw configuration and write a pending receipt. This is the only step that edits your configuration file.

npx -y agi-super-team@latest --tool openclaw
npx -y agi-super-team@latest --tool openclaw --install
OPENCLAW_STATE_DIR="$HOME/.openclaw" \
OPENCLAW_CONFIG_PATH="$HOME/.openclaw/openclaw.json" \
  npx -y agi-super-team@latest --tool openclaw --install --connect

Add --all-subagents to install all 92 specialists; the default installs only the 14 canonical roles. --connect is rejected unless --install is also present. Repeat --tool to target several harnesses in one run.

What the package changes

Two things land under the resolved configuration directory, and a third only if you connect.

• Agent workspaces at <config-dir>/agency-agents/agi-super-team/ast-*. Each named role receives the bootstrap file set OpenClaw reads as project context: IDENTITY.md, SOUL.md, AGENTS.md, USER.md, TOOLS.md, and MEMORY.md.
• Canonical skills at <config-dir>/skills/agi-super-team/<skill>, copied byte for byte from the repository.
• Connection state at <config-dir>/agi-super-team/connection.json, plus a receipt.json written by --connect.

The connect step runs a dry run first, then merges each managed ast-* agent by id, preserving agents it does not own. It does not create channel bindings, and it does not reformat or reorder unrelated configuration keys.

Check the result

Re-run the preview. Anything reported as unchanged is already present with the same content, so a clean second run should report no new additions. Then ask OpenClaw what it loaded rather than assuming file presence equals loading.

openclaw plugins list --enabled --verbose
openclaw plugins inspect <name> --json --runtime
openclaw doctor --fix

A file existing on disk means structural wiring succeeded. The receipt keeps runtimeEvidence at pending until a real session shows the team delegating and an independent Governor reviewing a child session.

Limitations

The installer targets OpenClaw's documented file layout, not a published plugin contract. AGI Super Team is not packaged as a native OpenClaw plugin: there is no openclaw.plugin.json and no openclaw field in package.json. Skill discovery depth, the managed skill root, and the agent roster key are version dependent, and the local install under ~/.openclaw/agency-agents/ was checked on OpenClaw 2026.6.8.

One path divergence is reasoned from the installer source rather than observed at runtime. When only OPENCLAW_CONFIG_PATH is set and its directory is not the state directory, the installer writes skills to dirname(configPath)/skills while OpenClaw documents its managed skill root under the state directory. Setting OPENCLAW_STATE_DIR and OPENCLAW_CONFIG_PATH together avoids the ambiguity.

Connect refuses to run when openclaw config get returns the redaction sentinel __OPENCLAW_REDACTED__, and when the primary configuration contains $include. Both cases require manual wiring.

Rollback and uninstall

Remove the two managed directories under the resolved configuration root: agency-agents/agi-super-team/ and skills/agi-super-team/. Delete <config-dir>/agi-super-team/ to remove the connection and receipt.

If you connected, restore your configuration from the backup the installer recorded before it edited the file, and remove only the managed ast-* entries rather than rewriting the whole configuration. Do not delete the entire OpenClaw state directory: it also holds credentials, sessions, and unrelated plugins. If the legacy agents.list structure was migrated by the doctor command, that migration is OpenClaw's own change and is not undone by uninstalling this package.