Skip to content

Releases: alexanderradahl/mac-developer-bridge

Temporary Rush Lindell concept transfer

Pre-release

Choose a tag to compare

Temporary artifact-transfer release. It will be deleted after the files are moved into the ChatGPT sandbox.

v0.2.0 — Give ChatGPT a real terminal on your Mac

Choose a tag to compare

@alexanderradahl alexanderradahl released this 15 Aug 16:05

Mac Developer Bridge is now public and open source.

It gives a ChatGPT conversation a real execution environment on your Mac: shell commands, unrestricted filesystem access, real PTY sessions, background jobs, and read-only access to stored Codex threads.

The bridge itself makes no model call. ChatGPT stays the reasoning layer; your Mac stays the place where the work actually lives.

Included in v0.2.0

  • Arbitrary shell execution under the logged-in macOS user
  • Full file read/write/manage operations
  • Real interactive PTY sessions with bounded retention and reclaim logic
  • Detached jobs with persistent logs and process-group control
  • Read-only Codex thread discovery and history retrieval without turn/start
  • Local JSONL auditing
  • Explicit unlock latch and local kill switch
  • OpenAI Secure MCP Tunnel support for eligible workspaces
  • OAuth 2.1 + Cloudflare/HTTP transport for personal ChatGPT accounts
  • Native macOS menu-bar helper source
  • Full macOS CI test suite

Try it

git clone https://github.com/alexanderradahl/mac-developer-bridge.git
cd mac-developer-bridge
./menubar/build.sh
open /Applications/MacDevBridge.app

For setup details, read the README and DEPLOY.md. The examples/ directory has copy-paste workflows for recovering Codex sessions, fixing CI, taking over unfinished local work, and using interactive terminal programs.

Read the security model first

This project is deliberately unrestricted. It is not sandboxed and has no command or path allowlist. An MCP client using it receives the effective permissions of your macOS account. Read SECURITY.md before enabling it.

If you build something useful with it, post the workflow in GitHub Discussions so other developers can reproduce it.