This will make it much easier to trap people into installing it without any isolation just to their primary user account or even make it run with admin privileges by default.
With the recent security related events we already see that it seems to be wide spread practice that many operators avoid the hassle of isolating their agents.
It is just an incredible cultural experience to see how quick stupidity gets accepted as a behavioural default.
The Linux version seems to use bubblewrap + seccomp for a "workspace sandbox" automatically, in addition to the auto mode and/or user approval. It's probably a mild step up from what many normal people are currently doing.
A VM would be even better, but people could presumably run this in one if we manage to convince them of higher sandboxing in general ?
For someone who has not tried these desktop apps: what is the the advantage versus cli codex with some MPCs and multiple folders each one with their context files?
The same as an OS with a UI. Discoverability, fewer actions per activity, easier navigation, faster to learn/lower skill floor, etc. Some highlights:
1. Much better multi-agent orchestration. The app supervises many agents, with different project views and built-in git worktrees, so agents can work on isolated copies of the same repo. It's easy to jump between tasks and see changes. I recall OpenAI wrote that CLI was not designed around this style of work.
2. The app combines multiple terminals, file previews, PR-review workflows, SSH connections, an integrated browser, and page annotations. For front-end stuff, Codex can run the app in Codex for mockups/prototypes, then iterate inside the app. IMHO I think this is a much faster, more intuitive flow.
3. For long-running and recurring agent workflows, I think they're much easier to manage in the app. You get automations, review queues, persistent conversation context, future schedules, and auto resume for longer running tasks. E.g. CI failure summaries, issue triage, and release briefs.
You can do some of the above, to some degree, with varying levels of success in the CLI, but I think it's miles ahead in the app.
You get GUI niceties: a nice presentation of the output like inline markdown rendering including tables and images in a nice font. Input supports drag & drop, and I can actually navigate the input field the way I am used to (pointing and clicking, using keyboard shortcuts to jump to beginning of words / sentences).
Not sure what the most modern CLIs support, but for me just the ergonomics of a GUI text field alone are superior.
I'm not ready to try this yet, since after some recent experiences[1] I've decided not to be at the cutting edge of new tools and models for a few weeks or months.
However, from the screenshots and description, I expect that you would have these advantages:
- History. Currently, if you type into the CLI (TUI) your intention and requests are captured in some transcripts, but not in conversational turns. If you want the history of what you typed into the cli/tui you would have to datamine it from transcripts. By contrast, on the screenshots you can see it is a simple conversation that's saved and easy to return to.
- Multiplatform. As per the announcement "Use Codex across ChatGPT, your editor, and the terminal", meaning that you could open the ChatGPT app on your phone and continue to interact with this. While this might not matter to you if you exclusively code while sitting in front of your computer, still, it helps you be able to stay on top of things if you are on mobile.
- Background tasks and autonomous work. It says you can schedule it to do things in the background (issue triage, alert monitoring). At the moment, it would only do this if you've asked either codex or another agent to build a harness for it that does so. (i.e. you could ask Claude to build a harness that calls Codex on some schedule or interval.)
These all seem pretty good and I look forward to starting to use it once it's been more battle-tested.
[1] notably, on the Anthropic side the Opus 5 regressions - I had to downgrade to Opus 4.8 as I found Opus 5 was unreliable. I currently use Opus 4.8 and Codex Sol 5.6.
Access to your computer is the entire point of the app. Codex computer use can script and control any application on your computer.
You can give it any task on your comouter and it can automate it.
Such as creating a photo on Photoshop, creating 3D models, editing videos, or browsing any website without scripting.
Honestly, you're missing out. The productivity gains I've had with these tools is unbelievable. I understand the risk though, so if you've got government sensitive data on your computer, or no backups, don't use the "full access" option. Babysit what it does instead.
I upgraded my workflow a few months ago from "copy-paste things in and out of ChatGPT" to "use an agent that edits my project files and runs tests on its own" and the ergonomics are just so much better and enables automating bigger tasks. I still monitor everything it does and do manual adjustments so I feel ownership of the code.
Literally everything from generic coding agent to shopping.
I run it in a MacOS vm, fwiw, for certain tasks. I usually hand it a repo and say “install all build dependencies” and it’ll click through installation GUIs where necessary. I wonder if the TOS of an application is enforceable if a bot agreed and a human never saw it.
It can UI test web apps if that’s part of your job, but it can also just use the browser for tasks. I’ve had it research flights by checking different dates automatically and compiling the results for me. I’ve heard others use it to handle building a shopping cart for instacart/grocery delivery.
Probably the hero usecase for most people would be app/web development. It can control either a browser or a device simulator and can iteratively build and test the application, by clicking real buttons.
Reminder to everyone, treat these as trojans. Run them isolated from the rest of your system.
Give it a full desktop in a VM if you want to, just not direct access to your system.
This will make it much easier to trap people into installing it without any isolation just to their primary user account or even make it run with admin privileges by default.
With the recent security related events we already see that it seems to be wide spread practice that many operators avoid the hassle of isolating their agents.
It is just an incredible cultural experience to see how quick stupidity gets accepted as a behavioural default.
The Linux version seems to use bubblewrap + seccomp for a "workspace sandbox" automatically, in addition to the auto mode and/or user approval. It's probably a mild step up from what many normal people are currently doing.
A VM would be even better, but people could presumably run this in one if we manage to convince them of higher sandboxing in general ?
From yesterday, with 26 comments: https://news.ycombinator.com/item?id=49264334
FYI; This link shows Codex based on your current OS. I get a norwegian landing page with a download link for Windows.
Same. I was quite confused. [This page](https://learn.chatgpt.com/docs/app) offers the Linux download link if anyone is interested.
Download it a few hours ago. I've been waiting a long time for linux and it is working fine in debian kvm via X11
For someone who has not tried these desktop apps: what is the the advantage versus cli codex with some MPCs and multiple folders each one with their context files?
The same as an OS with a UI. Discoverability, fewer actions per activity, easier navigation, faster to learn/lower skill floor, etc. Some highlights:
1. Much better multi-agent orchestration. The app supervises many agents, with different project views and built-in git worktrees, so agents can work on isolated copies of the same repo. It's easy to jump between tasks and see changes. I recall OpenAI wrote that CLI was not designed around this style of work.
2. The app combines multiple terminals, file previews, PR-review workflows, SSH connections, an integrated browser, and page annotations. For front-end stuff, Codex can run the app in Codex for mockups/prototypes, then iterate inside the app. IMHO I think this is a much faster, more intuitive flow.
3. For long-running and recurring agent workflows, I think they're much easier to manage in the app. You get automations, review queues, persistent conversation context, future schedules, and auto resume for longer running tasks. E.g. CI failure summaries, issue triage, and release briefs.
You can do some of the above, to some degree, with varying levels of success in the CLI, but I think it's miles ahead in the app.
You get GUI niceties: a nice presentation of the output like inline markdown rendering including tables and images in a nice font. Input supports drag & drop, and I can actually navigate the input field the way I am used to (pointing and clicking, using keyboard shortcuts to jump to beginning of words / sentences). Not sure what the most modern CLIs support, but for me just the ergonomics of a GUI text field alone are superior.
It's easier to use for most people. I don't think CLI and GUI programs target the same audience.
I'm not ready to try this yet, since after some recent experiences[1] I've decided not to be at the cutting edge of new tools and models for a few weeks or months.
However, from the screenshots and description, I expect that you would have these advantages:
- History. Currently, if you type into the CLI (TUI) your intention and requests are captured in some transcripts, but not in conversational turns. If you want the history of what you typed into the cli/tui you would have to datamine it from transcripts. By contrast, on the screenshots you can see it is a simple conversation that's saved and easy to return to.
- Multiplatform. As per the announcement "Use Codex across ChatGPT, your editor, and the terminal", meaning that you could open the ChatGPT app on your phone and continue to interact with this. While this might not matter to you if you exclusively code while sitting in front of your computer, still, it helps you be able to stay on top of things if you are on mobile.
- Background tasks and autonomous work. It says you can schedule it to do things in the background (issue triage, alert monitoring). At the moment, it would only do this if you've asked either codex or another agent to build a harness for it that does so. (i.e. you could ask Claude to build a harness that calls Codex on some schedule or interval.)
These all seem pretty good and I look forward to starting to use it once it's been more battle-tested.
[1] notably, on the Anthropic side the Opus 5 regressions - I had to downgrade to Opus 4.8 as I found Opus 5 was unreliable. I currently use Opus 4.8 and Codex Sol 5.6.
Do people really use that? It seems horrible to turn your computer into a spydevice for AI slop spammers.
If that’s an Electron app, what’s the difference with running it in the browser?
Access to your computer
That's why I won't download that tool.
Access to your computer is the entire point of the app. Codex computer use can script and control any application on your computer.
You can give it any task on your comouter and it can automate it. Such as creating a photo on Photoshop, creating 3D models, editing videos, or browsing any website without scripting.
Honestly, you're missing out. The productivity gains I've had with these tools is unbelievable. I understand the risk though, so if you've got government sensitive data on your computer, or no backups, don't use the "full access" option. Babysit what it does instead.
Isn't it expensive, though? If you let it perform gui or web tasks for you using vision, I'd think it consumes lots of tokens.
Can you give some examples? I'm evaluating where/how I could use stuff like this.
I upgraded my workflow a few months ago from "copy-paste things in and out of ChatGPT" to "use an agent that edits my project files and runs tests on its own" and the ergonomics are just so much better and enables automating bigger tasks. I still monitor everything it does and do manual adjustments so I feel ownership of the code.
Literally everything from generic coding agent to shopping.
I run it in a MacOS vm, fwiw, for certain tasks. I usually hand it a repo and say “install all build dependencies” and it’ll click through installation GUIs where necessary. I wonder if the TOS of an application is enforceable if a bot agreed and a human never saw it.
It can UI test web apps if that’s part of your job, but it can also just use the browser for tasks. I’ve had it research flights by checking different dates automatically and compiling the results for me. I’ve heard others use it to handle building a shopping cart for instacart/grocery delivery.
Probably the hero usecase for most people would be app/web development. It can control either a browser or a device simulator and can iteratively build and test the application, by clicking real buttons.
None that I can see - I already have it installed as a chrome app on my Mint desktop, and it seems identical.
Does the Chrome app have access to your local files, like when you're working on a code project?
Why do you need nodejs if you can run javascript in the browser?
people good w/ linux would not have been holding their breath for companies which keep intelligence for a premium & h0st@ge depending on policy