Fix memories namespace for Responses API tools#24898
Conversation
jif-oai
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5358fc4bc7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: adf839418f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Why
Dedicated memories tools are exposed through a Responses API namespace tool. The namespace itself has to be a valid tool identifier, so
memories/can fail validation before the model ever gets a chance to call the memory tools.What changed
MEMORY_TOOLS_NAMESPACEfrommemories/tomemories.memory_tool_namespace_matches_responses_api_identifierso the namespace stays non-empty and limited to Responses-safe identifier characters.Verification
codex-rs/ext/memories/src/tests.rs.