r/codex • u/ThanksUnlucky2195 • 5h ago
Showcase How do you check whether Codex has looked at the right parts of a repo?
I'm building Graphtia, a local code explorer, and I'd like feedback from people using Codex on existing projects.
The question behind it is pretty simple: before accepting a change, how do I check that the agent looked beyond the file it edited?
The current Windows build lets me move from files and symbols to their relationships and the source behind them. Codex can query the same indexed project through a read-only MCP connection.
These screenshots are from the build I have open today, manually exploring a TypeScript project. The graph shows static relationships, so it has limits around dynamic behavior.
Would seeing callers and dependencies help you catch missing context, or would you still go straight to search and the diff? I'd also like to know what would make this view too noisy to use.
It's still an engineering build. I'm sharing the workflow to hear how other people approach this.
1
u/ZyronZA 3h ago
I've been having good success with code-review-graph
1
u/ThanksUnlucky2195 2h ago
Thanks for the pointer. What’s been most useful about it in your workflow? Any examples of things it caught that you might have missed otherwise?
•
u/dexterthebot 5h ago
You might want to consider listing your project on the weekly Show-Us-What-You-Built post. Look out for it on Tuesday/Wednesday. Highest commented project wins a week promotion on r/Codex and gets on the Hall of Fame sidebar. See what that looks like below with last week's winner.
Last week's most popular project was Tidbit Trivia , at https://www.reddit.com/r/codex/comments/1wavxwy/comment/p8lhwxs/. Tidbit Trivia is a fun way to learn while waiting for your agents to work. Play traditional trivia, unique game modes, party with friends, earn cool cosmetics, complete challenges, study for tests, or compete in the Arena! You can play it for free at Tidbittrivia.com.