Top
Best
New

Posted by whimblepop 4 hours ago

Codex CLI installs a persistent, self-updating background daemon by default(github.com)
390 points | 213 commentspage 3
elAhmo 2 hours ago|
So, similar as Google and Microsoft have been doing with all their tools?
ilitirit 3 hours ago||
I use it at work. On Windows it also launches a new console window every it executes (?) a command. You should definitely disabled this using --no-daemon.

I don't know how and why they ruined this CLI with needless "features". It was perfectly usable two weeks ago.

sigotirandolas 1 hour ago|
A bit off-topic, but on the rare occasions I help some acquaintance with Windows I always feel a bit upset that random split second console windows still pop up when installing everyday software, even that from Microsoft.

I remember them from way back on Windows 98 and no one seems to care to hide them (?).

ranger_danger 3 hours ago||
In some circles this is called a backdoor.
Alifatisk 3 hours ago||
Is anyone using the vscode extension of Codex? Its insane how brittle it is.

Just a couple of days ago, it was completely broken for about a week before it got somewhat fixed again. When I say fixed, I mean basic functionality is working again but bugs and regressions are still left. There are multiple issues tracking the same problems. The community have even started to patch the extension themselves as a workaround until its adressed.

You know whats even crazier? There are like a new release every other day with lots of commits and changes, yet it still in a bad shape. I have turned off autoupdate for Codex extension for this reason. The only extension I’ve had to.

I mean, it doesn’t take that much work to have some tests in the pipeline to make sure the extension continue to work, it almost feels like they are purposely doing this.

I have now experienced the consequences of ”move fast and break things”. I realize how much software quality means to me. Its not fun being on the receiving end, especially when it affects my daily workflow.

If any of you, see anyone hype up LLMs again, please refer them to the state of Codex vscode extension.

pluc 3 hours ago|
It's as if there was a reason the whole industry was obsessed with quality up to like 3 years ago
warpspin 3 hours ago||
All I'd want is a CLI with a few tools AND a built-in, properly configurable and working sandbox. Seems that's too much too ask.
phoghed 3 hours ago|
Just be the 10th person to make one this week.
quotemstr 4 hours ago||
Refusal to adhere to the XDG specification is a big signal that the app is going to be a general bull in a china shop. It's not that hard to do OS- and distribution-appropriate package management.
whimblepop 3 hours ago|
A well-behaved application should not only use XDG on Linux, but it should use platform-native conventions on macOS as well: "~/Library/Application Support", etc.
kristjansson 3 hours ago||
not to mention the daemon mode breaks a bunch of assumptions one might have about about codex CLI e.g. that codex CLI inherits the env vars of the shell that invokes it.

—no-daemon is the way, but still feels like the noose is tightening …

jbverschoor 3 hours ago||
Sandbox everything if the OS is not doing what it’s supposed to do
ashishb 1 hour ago|
Exactly, that's what I do, I even up end up writing my own for this purpose - https://github.com/ashishb/amazing-sandbox
hackerbrother 2 hours ago|
Claude has been doing this already.
More comments...