Add Codex Context Map for AGENTS.md discovery debugging - #281
Open
Han-1413141 wants to merge 1 commit into
Open
Han-1413141 wants to merge 1 commit into
Han-1413141 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I maintain Codex Context Map, an independent MIT-licensed tool built with Codex.
This adds one entry to the AGENTS.md section, alongside the existing instruction configuration tools. Its specific use is inspecting which instruction files are discoverable from a launch directory, which same-directory candidate is shadowed, and where a configured byte budget cuts off the text.
The interactive demo uses fictional data and needs no account or API key. For a real repository,
npx codex-context-map . --html context-map.htmlgenerates a self-contained offline report. There are no runtime dependencies.The project documents its pinned upstream discovery model and limitations: it does not reconstruct a live Codex session or resolve semantic instruction conflicts. I am submitting it for that narrow diagnostic value, without claiming established adoption.
Validation: the CLI/build checks and 14 browser workflow tests passed locally. The repository also has Linux, macOS and Windows CI. The listing follows the requested one-sentence format and includes the star badge.