{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifttb63ijwse55fte255dhrnauy2bqwgsudgg74vo3py23fu3g6bm",
    "uri": "at://did:plc:3hmagzdut76xycuvulaezm3j/app.bsky.feed.post/3mgrku3ve2rp2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihpmmzo3zav5plza3xqhvjgp3brjve4hc2zaywgto26tzb6skmwg4"
    },
    "mimeType": "image/png",
    "size": 235917
  },
  "path": "/2026/03/10/running-xcode-from-codex.html",
  "publishedAt": "2026-03-10T17:23:10.000Z",
  "site": "https://www.manton.org",
  "tags": [
    "FastScripts"
  ],
  "textContent": "I’ve been doing a lot of work in Codex for the upcoming Inkwell for Mac release. I’m weeks ahead of where I thought I’d be. One small tweak I’ve made to my workflow is to wire up ⌘-R to run the project while I’m in Codex.\n\nCodex has its own run action button, which in theory could run `xcodebuild` or `osascript` command-line tools, but that didn’t work for me. So I reached for FastScripts instead. I wrote this tiny AppleScript:\n\n\n    tell application \"Xcode\"\n    \tactivate\n    \trun workspace document 1\n    end tell\n\n\nHere’s a screenshot of the config in FastScripts:\n\nNow when I’m in Codex and it has finished a change, I review the transcript, then hit ⌘-R to run my Mac app and test the new thing. If I don’t like it, I’ll ask Codex for changes and run again. Then I can review the code diff and tweak or commit as needed. The keyboard shortcut makes this cycle just a little smoother.",
  "title": "Running Xcode from Codex"
}