Practical field guides

Choose the smallest useful team—and keep the evidence.

These guides separate what the repository contains from what has been proven in a specific harness. Start with installation safety, then choose a workflow that matches the outcome and risk.

Last reviewed: 2026-07-21 · Editorial scope: eleven maintained guides

Prerequisites

You need a local Git client, a current Node.js runtime for the manifest-backed installer, and a workspace where you can review proposed files before applying them. Harness-specific pages list any additional client requirements. Use a disposable destination for the first run.

Current evidence boundary

The repository is still completing its public fixture gate. A manifest or package being present does not establish parity across Codex, Claude Code, Cursor, or Gemini.

Installation and compatibility

  1. Install for CodexReview the curated native package, add its marketplace, and preview the optional agent sync.
  2. Install for Claude CodeInspect the repository marketplace, add it explicitly, and verify what the client actually loads.
  3. Install for OpenClawPreview the workspace and skill files, resolve the state directory, and merge the managed agents only if you connect.
  4. Install for HermesChoose the home that receives the role skills and profile blueprints, and see what the installer does not create.
  5. DeepSeek Harness statusNot installable yet. Read what is missing, what was verified by hand, and what remains unproven.
  6. Compare harness pathsUnderstand the difference between native packaging, repository context, metadata, and a published outcome fixture.

Outcome-oriented workflows

  1. Solo FounderTurn one bounded brief into a build, review, and release evidence trail.
  2. Choose an AI teamMatch task complexity and risk to the fewest roles that can challenge each other usefully.
  3. Content CreatorSeparate research, drafting, and measurement while keeping publishing human-controlled.
  4. Quant ResearchUse licensed historical data, paper evaluation, explicit costs, and an independent risk review.

A realistic first pass

git clone --depth 1 --branch main https://github.com/aAAaqwq/AGI-Super-Team.git
cd AGI-Super-Team
./install.sh --source "$PWD" --destination /path/to/review-workspace solo-founder
npm test
npm run validate

The first installer command is a preview. Read the destination list and recommended external dependencies before deciding whether to rerun it with --apply.

Limitations

These pages do not benchmark model quality, guarantee business outcomes, or certify every harness version. The guides reflect repository state on the review date and can become stale when a client changes its plugin format or permission model. Inspect the pinned revision and client documentation before installation.

Rollback and uninstall

Record the preview output before applying. The generic installer protects existing files, so rollback means removing only the new workspace-<agent> directories listed in that output. Native harness packages have their own uninstall controls; use the relevant installation guide and preserve any backup created by the sync tool.