Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I expect this sort of thing when installing/running the client, but I can see why it would be alarming for a CLI installed via NPM to do this
    by infinite_spin
  • Codex is very badly structured. I was an early user with codex. But it mixes state and configuration data; which is why I can't really declaratively manage it in my nix-darwin environment; so abandoned it a while ago. This issue being raised, and the way that the codex development responds back to it makes me not trust their harness ever again. I only use codex in opencode; which seems to be doing OK. At least openai doesn't gate their product to their harness like anthropic.

    Not trying to sing praises; i think opencode is doing a bunch of weird stuff too but it's not codex level.

    by silverbluep
  • Off-topic: I think the front-end quality of ChatGPT/Codex Desktop and Android app is simply dreadful—hard to imagine how such a large number of frequent failures made it into production. Do they not use human testing at all?
    by Sha1rholder
  • This is the same operational model as Claude Code.

      ls ~/.local/share/claude/versions/
  ps auxww | grep "claude bg"
    I see a few prior versions of the Claude Code binary and several running background tasks, without any copy of Claude Code in the foreground. I regularly get a "Update available" message in my Claude Code UI too.
    by timdorr
  • I’ve been using GPT models via hax[1], a bare bones harness with minimal tools on my system and have the models rely on bash for the most part the last few months. It’s been a breath of fresh air amidst all these overengineered harnesses.

    If I need special actions, I just make them CLI tools on my Mac and tell the AI model that such a tool exists(via a single line in its system prompt) and that’s it. It’s been very nice.

    [1] - https://usehax.dev/

    No affiliation whatsoever. Just a happy user.

    by reacharavindh
  • The daemon has many bugs. For example, when auto-updating, it would randomly ruin the permissions and block the goal as .git became read-only. Generally, it is extremely annoying how many bugs Codex has. I basically can't trust it to execute on any goal since it would often get blocked every few hours due to random bugs.

    https://github.com/openai/codex/issues/52251#issuecomment-60...

    by dllu
  • It also fills up my HD with old versions. I investigated and it took up something like 12 gigabytes in total on my system; which seems insane to me, it’s just a harness?

    People moan about how badly made Claude code is but Codex seems much worse on every metric

    by icantevenhold
  • There aren't any documented settings to disable this, but there is a feature flag it currently sits behind. You can flip it in your ~/.codex/config.toml[1]:

      [features]
  daemon_auto_start = false
    There are also some files that it writes to in ~/.codex at startup: pid files, lock files, things like that. You can delete them and replace them with symlinks to /dev/null, then mark those unwritable with `chattr +i` or similar. Presumably then the background daemon will crash on startup, if the feature flag ever goes away.

    --

    1: https://github.com/openai/codex/blob/0c329ad2c9d5a2592128a1d...

    by whimblepop

Explore Birbla archives