Specialist intelligence. Shared direction.

One brief.
Many minds.
Real progress.

Give your AI more than a prompt. Give it a team of specialists, a shared plan, and a clear path from idea to deliverable.

Open source. Your tools. You stay in charge.

An optical A-shaped core turns scattered tasks into coordinated specialist paths and tangible website, research and code outputs. Conceptual illustration.
SPECIALISTS, CONNECTED.YOUR NEXT MOVE.

01 / From intention to action

You bring the brief.
The team brings the craft.

A researcher finds the evidence. A designer shapes the experience. An engineer builds it. Shared instructions keep their work connected.

YOUR BRIEF / EXAMPLE
“Help me turn my idea for a customer feedback tool into a small, testable MVP.”
Product delivery team
A REVIEWABLE HANDOFF
  • 01A scoped product briefThe user, the problem, and what to build first.
  • 02A prototype with checksFocused implementation and reproducible tests.
  • 03A decision you can makeReview findings, known limits, and the next step.
  1. 01

    Frame the work.

    The CEO turns your brief into an outcome, selects a small team, and names the acceptance checks.

  2. 02

    Let specialists focus.

    Each role owns a bounded task, uses relevant skills, and brings its work back to the shared plan.

  3. 03

    Review. Then decide.

    The Governor challenges the evidence. You review the artifacts and approve any release or external action.

Illustrative workflow, not a completed project. AGI Super Team supplies role instructions and packaging; your agent framework runs the work.

03 / Make it yours

Your framework.
A new way to work.

Start from an inspected checkout. Select your framework to preview its files before you install anything.

Requires Git and Node.js 18+. Your framework may require a newer Node.js version.

Git source: 1.6.0
These commands use the repository checkout. The published npm release is 1.4.2. The current Git source changes are not yet published to npm. Release details.

Read the adapter guide
CLAUDE CODE / PREVIEW
git clone --depth 1 --branch main https://github.com/aAAaqwq/AGI-Super-Team.git
cd AGI-Super-Team

# Inspect the checkout, then preview. No files installed.
node bin/agi-super-team.mjs --tool claude-code
Preview is the default. Installation is explicit.
Ready to install after reviewing the preview?

From the same checkout, add --install --connect, then run a separate --doctor check. Replace claude-code with your chosen framework ID. Installation writes managed Agent and Skill files; connection may update framework configuration. Keep the reported backups to restore replaced files. Hermes creates blueprints only.

node bin/agi-super-team.mjs --tool claude-code --install --connect
node bin/agi-super-team.mjs --tool claude-code --doctor

Open a new client session and inspect what it discovers. Doctor checks artifacts, not model behavior.

Prefer a framework-neutral workspace? Preview Solo Founder

From the repository checkout, preview a separate workspace. Add --apply only after inspecting its destination and file plan.

./install.sh --source "$PWD" --destination /path/to/review-workspace solo-founder
Inspect Codex package

The framework connection

Same team.
Different native homes.

Adapters translate the shared role and skill files into each framework's format. File installation and runtime validation are separate steps.

FrameworkWhat you getRuntime evidence
Claude CodeNative Markdown Agents, Skills, and orchestratorValidation pending
CodexMain-session CEO, TOML Agents, and SkillsValidation pending
OpenClawAgent workspaces, Skills, and managed configuration mergeValidation pending
Hermes AgentRole Skills and Profiles / Kanban blueprintsBlueprint only

Built to be inspected

Good work comes
with its workings.

Roles have boundaries. Changes have checks. Handoffs include evidence and limitations, so you can understand what happened and choose what happens next.

  • Preview changes before writing files.
  • Review artifacts, checks, and unresolved questions.
  • Keep publishing and deployment under your approval.
Explore the verification record

GitHub repository signal

Current community signal.

Current counts come from GitHub's repository API. No third-party or reconstructed Star History is presented as official.

Current stars ... Loading current GitHub data.
Public forks ... Current repository state
Source of truth View Stargazers on GitHub Current GitHub records, no reconstructed timeline

Make room for your next idea

Big ambition.
Start with one brief.

Explore the roles. Choose a team. Make something worth reviewing.