photon-codex
I built photon-codex so I could keep working with my Mac's Codex task from Messages. I can send a request, a screenshot or a voice note from my phone, then continue the same work at my desk. It is experimental, but it is a tool I use and enjoy.
One conversation, ongoing work
The bridge connects an authorized iMessage conversation through Photon to one persistent Codex task and its workspace. A follow-up can steer work already in progress. Questions and approval requests come back into the conversation, and the task can resume after the bridge restarts.
The agent keeps its configured permissions. Moving a conversation to Messages should make the work easier to reach without silently giving it more authority.
Making it feel like Messages
I added images, documents, reactions and native voice messages in both directions. Progress can live in one editable bubble. Ordinary internal commentary stays out of the chat unless the agent explicitly chooses to send it, so the conversation can remain useful while substantial work happens behind it.
Sending is part of execution. A reply may contain several pieces, and a failure halfway through should not cause the first pieces to be sent again. Ordered delivery receipts let the bridge stop at the failure and retry only what remains.
That attention to continuity and delivery is what makes this more interesting to me than a remote command box: I can leave my desk, add a detail from my phone and return to the same thread of work.