G
gaia-harness/gaia
A serious harness for Claude Code
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Official descriptionA serious harness for Claude Code. Specs before code, gates on every commit, the Code Audit Team on every merge. Ships as a monorepo with a React frontend. Bring your backend.
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"gaia-harness-gaia": {
"command": "npx",
"args": ["create-gaia@latest"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"gaia-harness-gaia": {
"command": "npx",
"args": ["create-gaia@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio gaia-harness-gaia -- npx create-gaia@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 26 ★ · gaia-harness/gaia · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-26 · last seen 2026-11-14 · seen 23× · listed by 1 sources
- Score
- score 103 · 26 ★ · 1 sources · repo
- Install
npx create-gaia@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx create-gaia@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
gaia-harness/gaia；first catalogued 2026-10-26；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# GAIA
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Claude is raw power. GAIA is order and focus.
A serious harness for Claude Code. It keeps Claude-shipped code production-grade as your team scales. The React frontend is handled. You build the rest of your app on top. Every convention enforced in code. Every shortcut blocked at the source. Every merge audited before it lands.
Quick Start · What Breaks Claude · Trust · Token Economics · Tech Debt · Tech Stack · Claude Workflow · Feedback · History
## Who It's For
Engineering teams whose AI output is outpacing their review process
Engineering leads standardizing how Claude works across the org
Teams adopting AI-assisted development who want production-grade defaults from the first commit
Individuals building apps with Claude
## Quick Start
bash
npx create-gaia@latest my-app
One command. GAIA handles the rest, then /gaia-init finishes the last-mile setup (below).
> [!NOTE]
> Start projects with npx create-gaia@latest my-app rather than cloning or forking. The CLI sets up your project for you, strips the GAIA branding and release tooling, etc. A clone leaves all of that in place and pointed at the wrong repo.
Requirements: Node.js >= 22.22.0 (nvm recommended). macOS or Linux; on Windows, run inside WSL2 (the hooks and CLI need bash and POSIX file paths, and native Windows isn't exercised in CI).
Learn more about GAIA →
### Then: /gaia-init
GAIA ships clean. /gaia-init does the last-mile setup:
Configures the project. Title, package name, docs title, CODEOWNERS, localized site titles.
Installs dependencies. Bootstraps pnpm via corepack, runs pnpm install.
Configures i18n. Prompts for your language set, scaffolds the matching language files, updates the component and Storybook wiring.
Installs the React Doctor skill. React Doctor, first, so it is ready in the same session.
When it finishes, it continues straight into /setup-gaia in the same Claude session, which installs Playwright CLI and the typescript-lsp plugin, provisions the GitHub repository (for a repo admin, branch protection with the GAIA-Audit required check and squash-only merges) and asks the per-machine sandbox and statusline choices; it ends without a restart, suggesting /clear to start your first feature with a fresh context. /setup-gaia runs only the steps a clone still owes, so any developer can re-run it safely.
You end up with a clean app shell and a fully-configured Claude workflow.
### Repository layout
GAIA is a monorepo. The harness (.claude/, .gaia/, .githooks/, .github/, wiki/) lives at the repo root and the React app lives in frontend/. Launch Claude at the root for harness workflows (audits, merges, releases, /gaia- commands); a launch inside frontend/ supports frontend work through commit. Upgrading a 1.6.1 project? Open Claude Code in the 1.6.1 project and ask it to fetch, verify and follow the bundled 2.0.0 migration note, as the first line of the v2.0.0 release describes.
## What Breaks Claude on Real Projects
Most setups treat Claude as a tool you hold: bolt a CLAUDE.md onto the root and hope the model figures out the rest. GAIA treats Claude as an engineer you manage. That shift exposes three failure modes the bolt-on approach papers over.
A serious harness for Claude Code. It keeps Claude-shipped code production-grade as your team scales. The React frontend is handled. You build the rest of your app on top. Every convention enforced in code. Every shortcut blocked at the source. Every merge audited before it lands.
Quick Start · What Breaks Claude · Trust · Token Economics · Tech Debt · Tech Stack · Claude Workflow · Feedback · History
## Who It's For
Engineering teams whose AI output is outpacing their review process
Engineering leads standardizing how Claude works across the org
Teams adopting AI-assisted development who want production-grade defaults from the first commit
Individuals building apps with Claude
## Quick Start
bash
npx create-gaia@latest my-app
One command. GAIA handles the rest, then /gaia-init finishes the last-mile setup (below).
> [!NOTE]
> Start projects with npx create-gaia@latest my-app rather than cloning or forking. The CLI sets up your project for you, strips the GAIA branding and release tooling, etc. A clone leaves all of that in place and pointed at the wrong repo.
Requirements: Node.js >= 22.22.0 (nvm recommended). macOS or Linux; on Windows, run inside WSL2 (the hooks and CLI need bash and POSIX file paths, and native Windows isn't exercised in CI).
Learn more about GAIA →
### Then: /gaia-init
GAIA ships clean. /gaia-init does the last-mile setup:
Configures the project. Title, package name, docs title, CODEOWNERS, localized site titles.
Installs dependencies. Bootstraps pnpm via corepack, runs pnpm install.
Configures i18n. Prompts for your language set, scaffolds the matching language files, updates the component and Storybook wiring.
Installs the React Doctor skill. React Doctor, first, so it is ready in the same session.
When it finishes, it continues straight into /setup-gaia in the same Claude session, which installs Playwright CLI and the typescript-lsp plugin, provisions the GitHub repository (for a repo admin, branch protection with the GAIA-Audit required check and squash-only merges) and asks the per-machine sandbox and statusline choices; it ends without a restart, suggesting /clear to start your first feature with a fresh context. /setup-gaia runs only the steps a clone still owes, so any developer can re-run it safely.
You end up with a clean app shell and a fully-configured Claude workflow.
### Repository layout
GAIA is a monorepo. The harness (.claude/, .gaia/, .githooks/, .github/, wiki/) lives at the repo root and the React app lives in frontend/. Launch Claude at the root for harness workflows (audits, merges, releases, /gaia- commands); a launch inside frontend/ supports frontend work through commit. Upgrading a 1.6.1 project? Open Claude Code in the 1.6.1 project and ask it to fetch, verify and follow the bundled 2.0.0 migration note, as the first line of the v2.0.0 release describes.
## What Breaks Claude on Real Projects
Most setups treat Claude as a tool you hold: bolt a CLAUDE.md onto the root and hope the model figures out the rest. GAIA treats Claude as an engineer you manage. That shift exposes three failure modes the bolt-on approach papers over.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/gaia-harness-gaia/)
- Source
- github · https://github.com/gaia-harness/gaia
- Browse by field
- Open source
- Traction
- 26 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.