Update codex review

Author: zackproser

src/content/blog/openai-codex-review/page.mdx

@@ -1,5 +1,6 @@
 import { Button } from '@/components/Button'
 import Image from 'next/image'
+import Link from 'next/link'
 
 import codexHero from '@/images/codex-hero.webp'
 import codexChat from '@/images/codex-main-chat-interface.webp'
@@ -45,7 +46,13 @@ Codex is currently a chat-first experience. You gain access by being invited or
 
 <Image src={codexChat} alt="Codex is a chat-first experience now" />
 
-Once you've got access, you start by enabling multi-factor authentication, which is required to use Codex. Next, you authorize the Codex GitHub app for each organization you want it to work with. Codex then clones your repositories into its own sandboxes so it can run commands and create branches on your behalf. If you maintain dozens of public and private repositories, this setup is fantastic because you can jump between projects and queue up tasks for each of them without leaving the interface. If you only keep a single repo or two, the overhead may feel heavier than just asking an LLM for help or working in an AI-powered editor like Cursor.
+Once you've got access, you start by enabling multi-factor authentication, which is required to use Codex. Next, you authorize the Codex GitHub app for each organization you want it to work with. 
+
+Codex then clones your repositories into its own sandboxes so it can run commands and create branches on your behalf. 
+
+If you maintain dozens of public and private repositories, this setup is fantastic because you can jump between projects and queue up tasks for each of them without leaving the interface. 
+
+If you only keep a single repo or two, the overhead may feel heavier than just asking an LLM for help or working in an AI-powered editor like Cursor.
 
 ## Things I like about Codex 
 
@@ -68,7 +75,7 @@ By the time I start work, I tend to have a laundry list of items I want to compl
 
 ### I think this will eventually support my dream untethered workflow
 
-As I wrote about in [/blog/walking-and-talking-with-ai](Walking and talking with AI in the woods), ideally I'd like to start my morning in an office, launch a bunch of tasks, 
+As I wrote about in <Link href="/blog/walking-and-talking-with-ai">Walking and talking with AI in the woods</Link>, ideally I'd like to start my morning in an office, launch a bunch of tasks,
 get some planning out of the way, and then step out for a long walk in nature.
 
 <Image src={phone} alt="Codex is even usable on mobile" />
@@ -118,7 +125,7 @@ than 12 programming languages.
 
 Right now, it feels like I can spin up multiple tasks in parallel with a 40-60% chance that I'll be content enough with the result to hit the Open PR button instead of requesting changes.
 
-So far Codex has been perfect for firing off a bunch of maintenance-level updates: dependency bumps, minor copy tweaks and other small chores. I've tried asking it to tackle larger refactors and the experience quickly becomes cumbersome. The current workflow wants to open a fresh pull request for every iteration, which means pushing follow-up commits to an existing branch is awkward at best.
+So far Codex has been perfect for firing off a bunch of maintenance-level updates: minor copy tweaks, stylistic changes, and other small chores. I've tried asking it to tackle larger refactors and the experience quickly becomes cumbersome. The current workflow wants to open a fresh pull request for every iteration, which means pushing follow-up commits to an existing branch is awkward at best.
 
 ### Multi-turn updates on a branch 
 
@@ -148,7 +155,7 @@ Not yet, but I can see how it will once:
 - Codex enables more integrations with additional OpenAI platform capabilities such as generating images. 
 - Codex (potentially) becomes more of the high-level orchestration and signaling layer that humans primarily work out of
 
-At the moment, Codex is useful for flushing the low priority yet numerous and tedious maintenance tasks and small updates. 
+At the moment, Codex is useful for flushing the low priority yet numerous and tedious maintenance tasks and small updates at the beginning of the day.
 
 For significant refactoring or feature-building, I'm still better served doing that myself in an IDE with optional LLM support.