| I haven't made any changes yet and I think the changes that I do make, they will want. I want to create a `/knowledge` slash command that can quickly tell me what the Agent currently knows so I can determine if I need to perform "lobotomy surgery" to make it not know something or add what it needs. I created a new brain that helped me find the answer for what you described: > Codex does not just need a /v1/responses endpoint. It needs an OpenAI Responses-compatible agent surface. Many providers implement enough Responses API for text streaming, but not enough for Codex’s tool-call loop and event mapping. I can understand why they might have done this for performance and/or lock-in and/or AI thinking reasons. I don't think I will create a translation layer, as that would be a sync nightmare, so based on what I found and what you said, it doesn't look like you can use other providers unless you introduce a proxy layer to translate things. I should also note, even if you have the translation layer, you might end up breaking harness capabilities. I am going to update https://github.com/gitsense/smart-codex to include the `codex-rust-navigation` brain that you can use to chat with AI about. And you will probably want to use it since `gpt-5.5` estimated that 25 - 50 files did not have to be read: > Roughly 300-500 files avoided, with a defensible lower bound around 25-50 files. This brain is designed specifically for rust files so you will need to use code-intent if you want to ask more documention/config questions. |