You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Imagesrc={codexHero}alt="I got hands-on with OpenAI's Codex research preview. Here's what I thought..." />
30
32
33
+
<figcaption>The interface I want and the performance I'll have to wait for...</figcaption>
34
+
31
35
## Table of contents
32
36
33
37
On May 16th, 2025, I gained access to OpenAI's Codex research preview. I connected Codex to my GitHub organization and spent
@@ -62,6 +66,17 @@ This is one of the things I like most about Codex and that I'm most excited for
62
66
63
67
By the time I start work, I tend to have a laundry list of items I want to complete, so initiating a ton of them in parallel via natural language feels like a reasonable interface.
64
68
69
+
### I think this will eventually support my dream untethered workflow
70
+
71
+
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,
72
+
get some planning out of the way, and then step out for a long walk in nature.
73
+
74
+
<Imagesrc={phone}alt="Codex is even usable on mobile" />
75
+
76
+
I think, ultimately, once some of the sharp edges are polished, Codex will support me and others in performing our work effectively away from our desks.
77
+
78
+
<Imagesrc={phoneTwo}alt="Codex and similar tools will ultimately support workers who want to be effective away from their desks" />
79
+
65
80
### Follow ups via chat
66
81
67
82
Once your initial task has had some time to bake, you can click into it to view its progress, see the logs and make follow-up requests via a very familiar chat interface.
@@ -111,6 +126,8 @@ It's not clear when or if changes will be pushed on an existing branch, and righ
111
126
112
127
### Lack of network connectivity in execution sandboxes
113
128
129
+
To be clear, I understand this is an intentional design choice. It mitigates remote code execution vulnerabilities amongst others.
130
+
114
131
This currently blocks the use of Codex for a lot of the tasks that working developers are going to want to use it for, namely
115
132
resolving annoying dependency issues by installing a more recent version of a package and regenerating the relevant lockfiles in the process.
0 commit comments