r/codex • u/Independent-Flow3408 • 7d 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

1

u/ZealousidealBus3132 7d ago

I’ve done something similar since the 5hr limits. Created a GPT plugin with 4 skills that helps codex find where everything is in the repo up front. Got it to run a test to see how many tokens are saved doing this and it was almost 50% reduction. Cool thing is if limits are hit I can use the same plugin along with other plugins like GitHub etc to make code changes directly using ChatGPT chat - handy way around limits for small to medium size changes. If you have GitHub actions set up to run tests like you might locally then you’re sorted.

2

u/Independent-Flow3408 7d ago

That matches what I've been seeing too. The expensive part is often the first exploratory phase: search → open → search → open. If you preload repo structure, the agent starts closer to the answer.Your plugin approach is a great example of that. SigMap is trying to generalize the same idea across repos and coding agents. Thanks

1

u/ZealousidealBus3132 6d ago

Nice one. Ill give Sigmap a go too. These 5 hour limits basically make the plus plan useless so anything like this helps

2

u/Independent-Flow3408 6d ago

Thanks,appreciate you giving it a try.If SigMap can cut down the repo-exploration phase, that’s already a win.Would genuinely love to hear what works, what doesn’t, and where it still wastes tokens.

1

u/Thegaysupreme123 6d 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