Codex installation

Install the focused Codex package, not the whole archive.

The Codex distribution is a separate curated package. Adding it does not copy the generic starter-kit workspaces, and syncing its optional agent roles is a second, preview-first action.

Last reviewed: 2026-07-21 ยท Surface: Codex plugin marketplace

Prerequisites

  • A current Codex installation with plugin marketplace commands available.
  • GitHub access to aAAaqwq/AGI-Super-Team.
  • Permission to add a user-level plugin and, only if desired, write agent TOML files under your Codex home.

For a controlled review, clone the repository first and inspect .agents/plugins/marketplace.json, .codex/INDEX.md, and plugins/agi-super-team-codex/.codex-plugin/plugin.json.

Install step by step

  1. Inspect the packageConfirm the repository revision, plugin source path, packaged skills, and requested permissions before adding the marketplace.
  2. Add the marketplaceRegister the repository and its .agents/plugins/marketplace.json entry with Codex.
  3. Add the pluginInstall the named package, then start a new task so Codex can discover the newly available skills.
  4. Preview agent syncInvoke $agi-super-team-sync without applying. Review creates, updates, backups, and destination paths.
codex plugin marketplace add aAAaqwq/AGI-Super-Team --ref v1.7.1
codex plugin add agi-super-team-codex@agi-super-team

The marketplace reference selects the release tag matching the npm and plugin version. A Git tag is not a cryptographic content pin: verify and record the tag's resolved commit before installation, and stop if it differs from the published release commit. Repository commands may evolve with the client; check codex plugin --help before scripting them.

What the package changes

The plugin exposes a small set of Codex-oriented workflows for bounded agent swarms, explicit project memory, iterative retrieval, context engineering, and optional agent synchronization. It does not install the repository's generic workspace kits, copy the full skills library, modify ~/.codex/config.toml, or create a background memory service.

Sync remains optional

The sync workflow should show its plan before writing. Differing installed agent files are backed up; unrelated files are not deletion targets.

Check the result

Start a new Codex task and confirm that the plugin's named skills appear. If you enabled agent sync, run it in preview mode again: unchanged destinations should no longer be proposed as fresh writes. Keep the repository revision and the plugin version in your evaluation notes.

codex plugin --help
git -C /path/to/AGI-Super-Team rev-parse HEAD
git -C /path/to/AGI-Super-Team diff --check

Limitations

The package is intentionally narrower than the generic repository. It does not establish that a business workflow, external integration, or generic starter kit produces the same outcome in Codex as in another harness. Plugin command names and cache behavior depend on the installed Codex release. Published outcome verification remains pending until a clean public fixture is tied to the served commit.

Rollback and uninstall

Use Codex's plugin management command for your installed version to remove agi-super-team-codex@agi-super-team, then remove the marketplace only if no other package uses it. If agent sync created or updated TOML files, consult the reported backup directory and restore only the files you intentionally replaced. Do not delete your entire Codex home.