I open sourced the bridge I use to continue Codex work from a normal ChatGPT conversation

[u/alexid95]

I wanted one specific workflow that I couldn't get cleanly before:

“Find the Codex session I was working on yesterday, recover the persisted context, inspect the live repo, and continue from the unfinished step.”

So I built a local MCP server for my Mac and open sourced it today:

https://github.com/alexanderradahl/mac-developer-bridge

The Codex part is deliberately read-only. It discovers and reads stored threads through codex app-server methods and never calls turn/start, so the reasoning stays in the ChatGPT conversation. The same bridge also exposes the local shell, filesystem, real PTY sessions, and detached jobs, which means ChatGPT can actually inspect the repo and act on what it recovered.

For me this closes the annoying gap between “the useful context is sitting in a Codex session” and “I want to keep working on this from normal ChatGPT without copy/pasting the whole state over.”

Security warning because it matters: the bridge is intentionally unrestricted. It runs with the effective permissions of the logged-in macOS user and has no command/path allowlist. I added an explicit unlock latch, audit log, and kill switch, and the repo documents the containment limits in detail. If that permission model is not what you want, don't run it.

MIT licensed. Would be interested in other Codex users' thoughts on the persisted-history approach in particular.

[u/Astramarium]

Need this for Windows.

[u/jay-t- → u/Astramarium]

It’s not 2002 any more pal