What they did
u/Unixwzrd, who wrote a Safari extension called LogGPT for exporting ChatGPT chats, wanted the context of a very long ChatGPT Work conversation available inside a Codex development project. They gave Codex permission to control their Mac and asked it to work out how to transfer the context, without naming any method. Codex first tried the built-in ChatGPT and Codex integration, then opened Safari on the original conversation and used the LogGPT download button. When scripting Safari through JavaScript failed, it switched to macOS Accessibility to find and press the button.
How it went
The built-in route only exposed six of the 1,651 message records to the receiving chat. The export produced a ZIP with all 1,651 records, 97 artifacts, the conversation as structured JSON and an artifact manifest. Codex checked the SHA-256 hashes and the ZIP integrity, then used the material to rebuild the project context. The poster says Codex picked LogGPT from its memory of earlier development work on the extension; they never told it to use Safari or the extension.
Worth knowing
The tool that saved the day was the poster's own extension, and several commenters read the post as an advert for it; nobody disputed the numbers, but nobody confirmed them either. Native transfer between ChatGPT and Codex looked badly truncated here, so check how much context actually arrived. Giving an agent full computer control means it may reach for Accessibility APIs when scripting fails.
GitHub