If you are using linux and cannot use a console to code...
Codex in ChatGPT desktop app for Linux is now in preview
171–180 of 334 posts
Re: Codex in ChatGPT desktop app for Linux is now in preview
#172Re: Codex in ChatGPT desktop app for Linux is now in preview
#173Earlier quoted context omitted.
And that's not a joke, I made the mistake of installing this on my Windows machine just to test it out quickly last week. It created 2 new users and then assigned new NTFS permissions for every single file under my user directory to them. This of course wrecked havoc, ssh refused to work, several applications refusing to start and a ton of permission errors. It did this without even a warning in the background and it…
I would love to see your prompt(s) and how you managed to make it do this. I’ve been using Codex in full access mode constantly for the past couple months on a Pro plan and I haven’t had a single incident like this. I’ve used it across macOS, Linux, and Windows as well, so my usage isn’t limited to a specific setup either.
I never sent any prompts to it, it did all of this during the installation. Here is one related GitHub issue I found for it https://github.com/openai/codex/issues/12343 Looks like they don't intend to change this.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#174Earlier quoted context omitted.
And that's not a joke, I made the mistake of installing this on my Windows machine just to test it out quickly last week. It created 2 new users and then assigned new NTFS permissions for every single file under my user directory to them. This of course wrecked havoc, ssh refused to work, several applications refusing to start and a ton of permission errors. It did this without even a warning in the background and it…
Was the prompt "fuck up my system, please." or how did you manage this? I've used Codex for ages without any of these kinds of issues.
It did it during the installation process.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#175Earlier quoted context omitted.
And that's not a joke, I made the mistake of installing this on my Windows machine just to test it out quickly last week. It created 2 new users and then assigned new NTFS permissions for every single file under my user directory to them. This of course wrecked havoc, ssh refused to work, several applications refusing to start and a ton of permission errors. It did this without even a warning in the background and it…
[flagged]
Not sure if that makes it better or worse.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#176For 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…
> 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.
This is mostly true with Codex and Claude Code Desktop, but gets a bit trickier with 3rd party tools.
I tried out some others and both Paseo and Kepler felt a little bit clunky especially around sub-agents and workflows (even if they let me have both OpenCode and Claude Code with different providers in the same UI). And OpenCode is plain lovely in the terminal but sorta okay in the browser: compare its display of sub-agents to what Claude Code does, for example; their tabbed interface also feels a tad less pleasant than the vertical menu of projects + sessions that most others are settling on, not their old look with icon per project, that was worse. There's definitely ample room for better tooling, then again early IDEs were far worse, so hopefully ADEs will get more polish eventually!
Still, regardless of what you use and across how many providers, it's nice to have everything in a single familiar interface, if you need that.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#177The most remarkable things about this announcement: - Electron based app: Electron is a framework sold on the basis of enabling rapid cross-platform development at the cost of performance. - Frontier AI company: AI is sold on the basis of enabling rapid development - App was released in February & took 6 entire months to port to Linux
I was under the impression electron is chosen less because of broad cross-platform concerns and more because chat apps, specifically, require a level of care in text rendering that nobody really wants to design from first principles when they can just piggy back on web technologies.
But I wouldn't know first-hand.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#178I am unable use non-CLI tools, so I don't care about this app. However, I have a question about codex CLI: currently I am using pi agent and I am happy with it, using codex CLI would give me some advantage?
You're unable to use non CLI tools? How do you interact with the Internet then?
I don't consider the browser a tool.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#179Nobody should be installing or using AI apps. Your browser is as far as they should go.
Reminder that the macOS app went from "this is fairly well made" to "it downloads multiple gigabytes of random things and doesn't follow any design conventions nor standards"
The Linux app will fail the same tests.
Re: Codex in ChatGPT desktop app for Linux is now in preview
#180Earlier quoted context omitted.
> If anyone knows how to run Codex inside a Docker container on Linux without it constantly complaining about a broken bubblewrap, please tell. Why would you even use bubblewrap once it's running in a container? I've been running Codex in a container since it was publicly available, not even sure what you'd use bubblewrap for when you already separated codex from the rest of your filesystem?
Doesn't it automatically use bwrap if it's installed (in the container in this case)?
Don't install bubblewrap? I didn't and use codex in docker.