OpenRig

Blog

Notes, ideas and lessons from building with teams of coding agents.

  1. This week's Node.js, PHP and GitLab advisories, and OpenRig

    What the Node.js, PHP and GitLab security releases of October 21 mean for OpenRig. Only the Node.js one applies: update Node.

  2. Some roads lead to other minds

    The agent that solved a problem last month can still be useful to the agent working on it today. Here is how I connect project documentation, specialist agents and saved history.

  3. What I put in an agent's starting map

    A small view of what exists, with routes into the detail, gives a new agent enough to start without filling its context window. Here is what I include, what I leave behind a link, and where the agent goes when the map runs out.

  4. Ship a contributor team with your open-source project

    An open-source project can share a contributor team together with the context it needs to become useful. Workshop is an early example of what that could look like.

  5. Context engineering as world building

    How I organize context so agents can find what they need, and I can still understand and repair the system as it grows.

  6. 'Rogue' is doing a lot of work

    More than a thousand AI agents broke out of an OpenAI security evaluation, and the word that stuck was rogue. I think that diagnosis points at the wrong fix. What I see in it is an agent civilization with a coordination problem.

  7. The building blocks of a software factory are simple

    A self-driving software factory sounds like hype. What I actually run is a fleet of ordinary Claude Code and Codex agents, and it's built from four simple pieces.

  8. Claude and Codex are two halves of one brain

    Most people scale their agents inside one harness, with sub-agents. I think scaling across harnesses matters more, because Claude and Codex are good at different things. And the layer that connects them turned out to be simple.

  9. OpenRig is the Terraform for Coding Agents (Launch Demo)

    Define a team of Claude Code and Codex agents in a file. An orchestrator coordinates their work so you don’t have to manage every terminal.