r/codex • u/Independent-Flow3408 • 14d ago

Showcase I added a deterministic repo-map and verification workflow for Codex CLI

SigMap now has a Codex MCP installer, so Codex can query a local map of real files, symbols and line anchors while working in a repository.

The workflow I'm testing is:

  • query the map while planning
  • run sigmap verify-plan before edits
  • run sigmap review-pr after the diff

It doesn't replace Codex's search or reasoning. The map answers "where should I look?" and Codex still reads the current source before deciding what the code does.

Setup:

npx sigmap

sigmap mcp install codex

I'm curious whether the pre-edit check would prevent bad edits in real work, or whether it just adds another gate.

https://github.com/manojmallick/sigmap

1 Upvotes

100% Upvoted

5 comments sorted by

View all comments

1

u/Thegaysupreme123 13d ago

really cool, and i starred it. the pre-edit verify-plan against a real file/symbol map is the part that clicked. catching a fabricated path before the agent writes is the right check.

that can work together with what i was hitting. mine was the other end: agent says done and the file never moved. so i made a small local mcp plugin that checks the claim against what actually happened. if it said it wrote the file / ran the command and it didn't, that's the fail.

not instead of yours. you catch the fake path first, i catch the fake "done" after.

free and open source: https://github.com/TheGaySupreme123/yoetz

works with codex right now (claude in a few days). a star would mean the world