Repository navigation
fix: make Codex agents discoverable and share writing memory - #51
Merged
Merged
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.
Summary
Install six Codex agents as standalone
agents/*.tomlfiles with the documented discovery fields. Retire recognized legacy nested agent configs and registration sections on upgrades, with backups. Correct the fresh OpenAI provider config, which current Codex rejects when it redefines the reserved built-in provider.Connect the shared paper-miner memory to academic writing skills and preserve it across setup updates and uninstall. Clarify that Codex uses a natural-language request rather than Claude Code's slash command.
Verification
bash scripts/test_install_uninstall.sh(10 passed, including fresh and legacy agent migration)config.load=ok, TOML parseok, zero startup warningsbash -n scripts/setup.sh scripts/uninstall.shgit diff --checkRelated to #49. The issue screenshot's exact three-visible/three-missing split has no runtime log, so that particular split remains unconfirmed.