{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidxlttz4zx5qz23mn3j6abhjdh7d6bwswbtoavwwhxc6dawb5yuqq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmfa6cuf5pq2"
  },
  "path": "/t/codex-mobile-outlook-remote-continuity-for-codex-desktop-built-through-itself/1381441#post_1",
  "publishedAt": "2026-05-21T20:01:23.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hi everyone,\n\nI wanted to share a small project I have been building with Codex Desktop: **Codex Mobile Outlook**.\n\nThe idea is very simple, and maybe a bit naive: I wanted to keep working with an open Codex Desktop conversation even when I was no longer sitting in front of my Windows PC.\n\nRight now, as far as I know, Codex Desktop does not provide a built-in way to remotely command the active desktop session from a phone, send a screenshot or a document into the same chat, and then receive the answer back in a mobile-friendly place. So I created a **Codex skill** that acts as a remote-control and synchronization layer for Codex running on my Windows PC.\n\nI have prepared a white paper with the full workflow, screenshots and architecture. Since I cannot publish external links to the PDF here, if anyone is interested in reading it, please let me know by email and I will be happy to share it.\n\nThe first version was based on a OneDrive inbox. From the phone, I could drop a text file, Word document, screenshot or image, mark the instruction as complete with `READY`, and the skill would route it into the selected Codex Desktop project/chat. Codex would then publish the answer back to the inbox and clean the folder. That first prototype is still kept as a backup because it is simple and surprisingly useful when another channel fails.\n\nThe newer version uses Outlook as the main mobile interface. Under a `CODEX` folder, each Codex project becomes a folder and each Codex chat becomes a persistent mail item. The mail item is formatted like a lightweight WhatsApp-style conversation, with colored message bubbles, timestamps, unread status when Codex has replied, and an empty reply bubble at the end where I can write the next prompt from the phone and finish it with `READY`.\n\nThe result is not just remote prompting. It also creates a searchable Outlook archive of Codex projects and conversations, while keeping the desktop chat, the Outlook mirror and the OneDrive backup synchronized.\n\nOne thing I especially like is that this project was largely developed through itself. The first OneDrive version made it possible to keep working remotely while I was building and debugging the Outlook version. In practice, Codex Mobile Outlook became both the tool and the development environment for its own evolution.\n\nThe white paper presents the workflow, the motivation, the architecture, the OneDrive-to-Outlook evolution, screenshots of the Outlook chat mirror, the control console and a compact implementation inventory.\n\nI am sharing it because I think this kind of continuity could become an important part of desktop agents: being able to keep working with the same agent across PC and mobile, through tools people already use every day, with visible state, searchable history and a safe fallback channel.\n\nI would love to receive feedback from the Codex/OpenAI community. And if someone at OpenAI sees value in this direction, I would be very happy to explore how this kind of remote continuity, Outlook integration or mobile-first Codex control could evolve into a more polished product feature.\n\nAuthor/contact: Eduardo Albaizar - eduardoalbaizar@gmail.com",
  "title": "Codex Mobile Outlook: remote continuity for Codex Desktop, built through itself"
}