Skip to main content
🤖
Codex CLI+Stompy

Design in one tool, build in another, from the same record

Switching tools should not mean explaining the project again

The Problem

Plenty of people now use more than one coding tool on the same project: one to think a design through, another to build it, a third to review.

Each one starts cold. The design that was agreed in the first is a paragraph you retype into the second.

How Stompy Helps

Stompy is a record that every one of those tools can read, because it is not inside any of them.

Connect Codex CLI over MCP with OAuth. A session can read the project's brief, recall a decision by name and search by meaning. What you decided in another tool is there to read, and what you lock here is there for the next.

You decide what is kept. Stompy does not watch a session and does not write on its own. When something is locked, the reply shows the closest existing entries, so a clash with an earlier decision is noticed at the point you save it.

The same project is reachable from a shell with the stompy command and from scripts over the REST API.

Integration Walkthrough

1

Add Stompy to Codex CLI

Add this to ~/.codex/config.toml, then sign in and verify with /mcp inside Codex.

[mcp_servers.stompy]
url = "https://mcp.stompy.ai/mcp"
oauth_resource = "https://mcp.stompy.ai/mcp"
# then
codex mcp login stompy
2

Start from the brief

project_brief compiles the project's locked contexts and ticket summary into a short overview a new session can read. It is a summary of what you chose to keep, not a transcript.

project_brief(project="my-project")
3

Keep a decision with its reason

Say what was decided and why. The topic name is the handle you will recall it by; locking the same topic again saves a new version and keeps the old one.

lock_context(
project="my-project",
topic="notification_design",
content="""Decision: notifications are written once and delivered by a worker.
Why: delivery retries must not duplicate the write.
Must not change: the notification id format.""",
priority="important"
)
4

Pick it up in the next session

Recall by name, or search by meaning when you do not remember the name.

recall_context(project="my-project", topic="notification_design")
context_search(project="my-project", query="how notifications are delivered")
5

Hand the work on as a ticket

A ticket is a request someone can pick up later, with what they need already on it.

ticket(
action="create",
project="my-project",
title="Add integration tests for notification delivery",
description="Where: tests/notifications. Why: retry path is untested. Must not change: the id format."
)

What You Get

  • Tools stop being commitments: the record is not stored inside any one of them
  • Decisions carry their reasons, so the next tool does not undo them by accident
  • Tickets hand work on with what is needed already written down
  • Only what you lock is kept; nothing is captured on your behalf

Start your own record

Join the waitlist and we will tell you when your place is ready.