211–220 of 334 posts
Does this mean it's a matter of time until I can deploy codex on my raspberry pi now?
Why is this written in electron?
This is how I get ChatGPT on Windows to not absolutely suck. Can just install it in WSL now and it's got buttery smooth performance vs. the Windows version I blame AV hooks
I find it almost funny how hostile the response is when a company actually goes through the effort of supporting Linux. Apparently shipping the Linux version is only step one, you also need to pick the right framework, use the right packaging, consume the right amount of RAM, and preferably rewrite it natively.
Earlier quoted context omitted.
Exactly my thoughts! I was expecting a Rust app written from scratch available at least in Qt and GTK flavors , and maybe with a third and a fourth option. Don't they have agent swarms with infinite tokens?
They replaced a pretty decent native Swift Mac app (with only some chronic state management bugs), weighing ~100MB ish, with the Codex app that most people don't need, made in Electron, which takes minimum 5GB+ including filesystem cruft. Today I ran into a memory leak that froze the app and made the Renderer process take 5GB, then 10GB of RAM. That was after I asked it to only touch 3 text files in its working direc…
Earlier quoted context omitted.
I guess it's easier to solve Erdos problems and improve the lower bound of the Riemann hypothesis, than it is to solve Linux desktop app distribution.
Microsoft used to ship a Linux binary for Teams, but they stopped doing that. Guess the tech was lost.
Earlier quoted context omitted.
It'd be nice for sending prompts from phone, although it is a whole lot of bloat for just that feature. Par for the course for the AI era, in order to do a thing first you must import the universe.
That was already supported from your phone by using SSH, using the app server feature of the Codex CLI. The Codex desktop app is more for computer use, browser control, and the UI paradigm of GUI, which is overall just richer and better than a TUI, albeit more heavyweight.
One of the issues with this new trend of vibecoding a million features, is that the (vibecoded) docs are labrynths of new features, and features that are deprecated or redundant with 2 month younger features.
Earlier 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.
That is not how it works: the "but it works for me" is a logical fallacy.
Haven't you followed a bit all the posts about models, for example, escaping their environments?
The "but it works for me" is a random data point: an anecdote.
That there are people / companies where models ran wild and destroyed files / messed up projects is a fact.
When there are documented cases of stuff gone wrong, people must find ways to protect their data.
We literally see posts frontpage, daily, about AI sandboxing and we regularly see posts about AI escapes or AI SNAFUs.
And you come and post "show me your prompt, for it works on my machine"...
Earlier quoted context omitted.
Yeah, but if you use Qt like I did, you're shipping libstdc++, some other crap and Qt.
Yeah, I was kind of surprised recently that there's no solid native way to build desktop apps on Linux! I was thinking I'd build something actually native with AI but then the options were QT or or gtk...
I find it almost funny how hostile the response is when a company actually goes through the effort of supporting Linux. Apparently shipping the Linux version is only step one, you also need to pick the right framework, use the right packaging, consume the right amount of RAM, and preferably rewrite it natively.