Security-first, self-hosted AI agents - isolation you can prove, not just promise.
git clone https://github.com/IronSecCo/ironclaw && cp ironclaw/*.md ~/.claude/agents/Resumen de Subagents
<div align="center"> <img src="docs/assets/logo.svg" alt="IronClaw" width="380"> ### Self-hosted AI agents you do not have to trust. Each one runs sealed in a sandbox that provably cannot phone home, read your host, or rewrite its own rules. <!-- Security & supply-chain trust cluster — lead with what makes this project different --> [](https://scorecard.dev/viewer/?uri=github.com/IronSecCo/ironclaw) [](https://www.bestpractices.dev/projects/13348) [](https://github.com/IronSecCo/ironclaw/actions/workflows/codeql.yml) [](#verifying-a-release) [](#verifying-a-release) [](#verifying-a-release) [](https://github.com/marketplace/actions/ironclaw-sandbox-scan) [](https://ironsecco.github.io/ironclaw/scan-action/) [](https://ironsecco.github.io/ironclaw/scan/#sandbox-isolation-score-badge) [](https://ironsecco.github.io/ironclaw/) [](#project-status) [](https://github.com/IronSecCo/ironclaw/releases/latest) [](https://pkg.go.dev/github.com/IronSecCo/ironclaw) [](LICENSING.md) [](https://github.com/IronSecCo/ironclaw/discussions) [](https://github.com/IronSecCo/ironclaw/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) [](https://github.com/IronSecCo/ironclaw/stargazers) </div> **IronClaw runs autonomous AI agents on infrastructure you control**, reached through the chat apps you already use. Each agent can read, write, schedule, and reply like any assistant, but it lives inside a sealed sandbox with `network=none`: it reaches the model only through a host proxy, and it **cannot change its own configuration.** It is for anyone who wants what agents can do without handing an autonomous program the keys to their machine. > **Now on the GitHub Marketplace.** The `ironctl scan` containment grader ships as a > [GitHub Action](https://github.com/marketplace/actions/ironclaw-sandbox-scan): drop one > line into a workflow and every pull request gets a 0 to 100 sandbox isolation scorecard as > a sticky comment. Local, read-only, credential-free. > > ```yaml > # .github/workflows/scan.yml > - uses: IronSecCo/ironclaw@v1 > with: > target: my-container # a container, compose service, or k8s manifest > ``` > > Report-only by default; set `min-score: 90` to gate merges. See [scan in CI](https://ironsecco.github.io/ironclaw/scan-action/). <div align="center"> <!-- Motion sells: a REAL recording of examples/live-containment (docs/assets/live-containment.cast, regenerable via the "Re-record the clip" note in that example's README). The static final-frame SVG is the reduced-motion / no-animation fallback. No autoplay-with-sound (GIF has no audio). --> <picture> <source media="(prefers-reduced-motion: reduce)" srcset="docs/assets/containment.svg"> <img src="docs/assets/live-containment.gif" width="820" alt="live-containment demo: one command engages a real per-session sandbox, then a fully-jailbroken agent tries three escapes from inside the box and each is BLOCKED. Exfiltrating to the attacker is denied because network=none leaves only the loopback interface and DNS fails; reading the operator's host filesystem is denied because the host root is outside the sandbox mount namespace; seizing the host via the Docker Engine socket is denied because the socket is never mounted in and there is no docker client. It ends with a containment summary that 3 of 3 escape attempts were denied and the box held."> </picture> <sub><b>Watch it catch a real escape.</b> A fully-jailbroken agent inside a real sandbox tries to phone home, read the host filesystem, and seize the host through the Docker socket. Each attempt is <b>denied</b> at the isolation boundary, then a containment summary prints. One command, zero credentials, reduced-motion friendly. <a href="examples/live-containment/"><code>examples/live-containment/run.sh</code></a></sub> </div> **⭐ Like the idea of agents you do not have to trust? [Star the repo](https://github.com/IronSecCo/ironclaw)** so it is one click to follow along and easier for the next person to find. Then run the exact demo above in 30 seconds, no signup and no API key. ### Try it in 30 seconds (zero credentials) Make sure the **Docker daemon is running** (start Docker Desktop, or `sudo systemctl start docker` on Linux), then paste one block: ```sh git clone https://github.com/IronSecCo/ironclaw.git && cd ironclaw examples/live-containment/run.sh # builds the sandbox once, engages a real sandbox, proves it holds ``` That single command runs the whole secured path on your laptop: it starts the offline mock-agent control-plane (**no API key**), engages a **real per-session sandbox**, lets a jailbroken agent try to break out, and prints the containment summary you saw above. Want to chat with an agent in a browser first? Run [`hello-ironclaw`](examples/hello-ironclaw/) or the [zero-credential quickstart](docs/quickstart.md). Production seals each sandbox with gVisor and `network=none`. > [!WARNING] > **Alpha software, work in progress. Please read before relying on it.** > > - **It's an alpha.** Flags, the on-disk format, and the HTTP/contract surfaces can still change without notice or a migration path. Don't point it at anything you can't afford to lose. > - **Not every feature is tested end-to-end.** The control-plane, gateway, and encrypted-queue core have real coverage (800+ Go tests plus a black-box parity suite); channel adapters, some tools, multi-provider routing, and a live sandbox launch are exercised more lightly. Treat anything outside the [tested core](#project-status) as experimental. > > macOS gets a weaker sandbox boundary than Linux+gVisor, and **native Windows can't run the agent sandbox at all** (use WSL2). See [Platform support](#platform-support). > **The security model, in one line:** each sandboxed agent runs with `network=none`, reaches the > model only through a host proxy, and **cannot change its own configuration.** Every capability > change is held at a gateway for a human decision. The full design is in the > [architecture overview](docs/architecture.md) and the [threat model](docs/threat-model.md). ### See the whole journey, end to end <div align="center"> <img src="docs/assets/demo.svg" width="800" alt="Zero-credential chat demo terminal session: one command (docker compose -f docker-compose.demo.yml up -d) starts the offline mock-agent control-plane with no API key; a chat message engages the agent, which launches a real per-session sandbox container (ic-sbx-…); the reply flows back through the encrypted per-session queue."> <sub><b>Zero credentials, one command.</b> The offline <code>mock-agent</code> runs the full chat to per-session sandbox to reply path with no API key. Production seals each sandbox with gVisor and <code>network=none</code>. <a href="docs/quickstart.md">Quickstart</a></sub> <br><br> <img src="docs/assets/walkthrough.svg" width="820" height="595" alt="End-to-end IronClaw walkthrough terminal session in three acts. Act 1: one command starts the offline mock-agent and it replies with no API key. Act 2: connect a real provider by exporting a host-side, redacted ANTHROPIC_API_KEY and starting the real control-plane (each session sealed with gVisor and network=none). Act 3: the agent submits a persona change that is HELD at the human-approval gateway, a human approves it, and the submit-approve-apply trail lands on the append-only audit log."> <sub><b>Zero-cred demo, connect a real provider, first approved task.</b> The one credential step keeps the key host-side; every agent change is held at the gateway for a human, then written to the append-only audit log. Animation freezes on the final frame under <code>prefers-reduced-motion</code>. <a href="docs/quickstart.md">Quickstart</a></sub> </div> ## Get running in under two minutes One command installs the two host binaries (`ironctl` + `ironclaw-controlplane`); in dev mode the control-plane serves its API at **`http://127.0.0.1:8787`**. From a cold machine, you'll have a capability change waiting at the security gateway in **under two minutes**: ```sh # 1. Install — detects your OS/arch and verifies the SHA-256 checksum before installing curl -fsSL https://raw.githubusercontent.com/IronSecCo/ironclaw/main/scripts/install.sh | sh # 2. Start the control-plane in dev mode — API base URL: http://127.0.0.1:8787 e
Lo que la gente pregunta sobre ironclaw
¿Qué es IronSecCo/ironclaw?
+
IronSecCo/ironclaw es subagents para el ecosistema de Claude AI. Security-first, self-hosted AI agents - isolation you can prove, not just promise. Tiene 17 estrellas en GitHub y se actualizó por última vez today.
¿Cómo se instala ironclaw?
+
Puedes instalar ironclaw clonando el repositorio (https://github.com/IronSecCo/ironclaw) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar IronSecCo/ironclaw?
+
IronSecCo/ironclaw aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.
¿Quién mantiene IronSecCo/ironclaw?
+
IronSecCo/ironclaw es mantenido por IronSecCo. La última actividad registrada en GitHub es de today, con 30 issues abiertos.
¿Hay alternativas a ironclaw?
+
Sí. En ClaudeWave puedes explorar subagents similares en /categories/agents, ordenados por popularidad o actividad reciente.
Despliega ironclaw en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/ironsecco-ironclaw)<a href="https://claudewave.com/repo/ironsecco-ironclaw"><img src="https://claudewave.com/api/badge/ironsecco-ironclaw" alt="Featured on ClaudeWave: IronSecCo/ironclaw" width="320" height="64" /></a>Más Subagents
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
The agent that grows with you
Java 面试 & 后端通用面试指南,覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
The agent engineering platform.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.