wtf is codexcont?

CodexCont is a small proxy server that sits between a coding AI agent and an API that OpenAI's Codex or a similar Responses style service exposes. Its job is to work around a specific pattern the author noticed: sometimes the model's internal reasoning gets cut off partway through, and this tool detects that pattern and quietly asks the model to keep thinking instead of returning an incomplete answer. The project explains that it is intentionally bypassing an observed truncation behavior in the OpenAI Codex service, and it states plainly that anyone using this tool is responsible for any consequences if that counts as abuse of the service's terms or leads to unexpected costs. Behind the scenes, the proxy streams the model's reasoning to the coding agent as it comes in, but holds onto the actual final answer temporarily. When it sees the signal that a response was cut short, a specific pattern in the token count the API reports, it discards that partial answer, sends the reasoning back with an instruction to continue, and starts another round with the upstream service. If the response finishes normally, it just passes the final answer through, rebuilt into a single coherent reply so the coding agent only ever sees one response, even though several requests may have happened behind the scenes. Any traffic that does not match this specific pattern is passed straight through unchanged. The tool is written in Python, needs version 3.12 or newer, and uses the small web framework Starlette along with the httpx and uvicorn libraries. To run it, a user copies an example configuration file, adjusts settings like the upstream service address and authentication mode, and starts it with a single command. It can either forward a caller's own authentication headers, inject its own configured credentials, or fall back between the two, and it includes a safeguard that refuses to leak configured credentials to a different upstream address supplied in a request. The project includes an offline test suite that does not need any extra testing framework to run, covering things like the truncation detection math, parsing of the streaming responses, and the authentication safeguards.