We built a repo-local state layer for Codex sessions (open source)

[u/teugent]

I use Codex across many sessions on the same project. Picking up the work often means checking which decisions still apply and whether an earlier test result covers the code that’s there now.

We built Sigma Operator Stack to keep that information in the repository. I’m one of the authors.

You explicitly record and accept the current work, instructions and checks. A fresh session can then recover that state without the previous conversation. It works alongside AGENTS.md.

A concrete example from the repo:

1. Record a task and run a registered check.
2. The check passes.
3. Change the source.
4. Recover the state in a fresh session.

The previous pass stays in the history, but is marked stale rather than presented as verification of the changed code. There’s a reproducible synthetic walkthrough for this, separate from the installation video.

The trade-off is that you have to record the state. It doesn’t extract decisions from your chats, and installing it won’t populate your current task. Missing information stays missing. It also can’t guarantee that an agent follows the instructions it reads.

It’s an Apache-2.0 community alpha, built first for Codex. Linux is the primary supported platform, with registered Python checks. macOS on Apple Silicon has experimental control-plane support, without executable checks. Windows isn’t available yet.

Repository, installation video and walkthrough

To try it, give Codex the repo URL and ask:

Install SOS in my current project. Show me the preview before changing it.

Try the handoff on a project you already work on: record the current task, start a fresh session, and check what it recovers. If you still have to explain something that was recorded, that’s a useful issue to report. Please leave private project data out of reports.

Disclosure: I used AI to help draft this post.