{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie2w2btjtizb6toquarp4kyc3nz5udf6xn5ftambqqr73vzkgq5mu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlbvzx74oqv2"
  },
  "path": "/t/feature-idea-codex-mobile-control-inside-chatgpt/1380412#post_2",
  "publishedAt": "2026-05-07T18:41:15.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@petritbahtiri24"
  ],
  "textContent": "Hey @petritbahtiri24, this is a solid idea, especially the “desktop start, mobile supervise” flow. A lot of devs already treat Codex like an async teammate, so the gap becomes obvious the moment you step away from the laptop.\n\nThe MVP breakdown also feels realistic. Read-only status + approval notifications alone would already remove a lot of friction without turning mobile into a full IDE.\n\nThe safety section is especially helpful here too. Things like explicit approval for destructive actions, audit logs, and admin controls make the proposal feel practical instead of just “remote terminal on a phone.”\n\nForwarding this to the team so it’s properly logged and tracked internally. The push notification + approve/reject workflow seems like the strongest near-term win based on how people are already using Codex today.\n\nReally good write-up overall. Easy to understand and easy to picture in real workflows.\n\n-Mark G.",
  "title": "Feature idea: Codex Mobile Control inside ChatGPT"
}