The discussion is characterized by a split between praise for .NET 11's technical features and severe criticism of Microsoft's aggressive upgrade cycle, alongside a contentious debate comparing C#'s complexity against Go's simplicity. Participants disagree on whether the ecosystem's maturity justifies the migration burden and argue over specific language design choices like ConfigureAwait and generics.
306 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4 · Supporting reply 5 · Supporting reply 6 · Supporting reply 7 · Supporting reply 8openai
codex
Rust2025–2026
openai / codex
codex
Lightweight coding agent that runs in your terminal
163Distinct people
218Mentions
2Explicit recommenders
135.1KGitHub stars
What to know before exploring
What it is
Lightweight coding agent that runs in your terminal
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I love the fact that they're advertising the latest Codex Cli while most Windows users had to rollback/downgrade to an older version because of the annoying excessive terminal…
coverband used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
Critical Commenters criticize the repository for excluding .NET support by default and for rejecting community contributions with poor communication. Other comments highlight a specific bug where the model accidentally truncated its thinking process due to efficiency improvements.
A warning from this week’s discussion. Read the supporting reply
Also in these discussions
- anthropics/claude-code · linked in 3 of the same discussions
- earendil-works/pi · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Critical
Commenters criticize the repository for excluding .NET support by default and for rejecting community contributions with poor communication. Other comments highlight a specific bug where the model accidentally truncated its thinking process due to efficiency improvements.
Supporting reply 1 · Supporting reply 2 · 3 discussions summarized
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
Read the discussion on HN. A full-thread summary is not available yet.
Read the discussion on HN. A full-thread summary is not available yet.
Showing the three threads with the most distinct people linking this repo, from 31 threads this week.
Mentions over time
HN mentions by month218 dated mentions
Observed mentions: 2025-04-16 17:17:12 UTC to 2026-10-27 23:04:47 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 2025 | 2025-04-01 00:00:00 UTC | 2025-05-01 00:00:00 UTC | 11 | 2 | 9 |
| May 2025 | 2025-05-01 00:00:00 UTC | 2025-06-01 00:00:00 UTC | 5 | 1 | 4 |
| Jun 2025 | 2025-06-01 00:00:00 UTC | 2025-07-01 00:00:00 UTC | 10 | 3 | 7 |
| Jul 2025 | 2025-07-01 00:00:00 UTC | 2025-08-01 00:00:00 UTC | 5 | 1 | 4 |
| Aug 2025 | 2025-08-01 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 4 | 0 | 4 |
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 8 | 2 | 6 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 3 | 1 | 2 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 12 | 6 | 6 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 8 | 2 | 6 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 13 | 4 | 9 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 14 | 6 | 8 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 9 | 1 | 8 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 14 | 6 | 8 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 9 | 2 | 7 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 15 | 6 | 9 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 41 | 10 | 31 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 11 | 6 | 5 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 10 | 1 | 9 |
| Oct 2026 | 2026-10-01 00:00:00 UTC | 2026-11-01 00:00:00 UTC | 16 | 4 | 12 |
What Hacker News says
218 sourcesPCpcj-github·Oct 27, 2026
Your LLM can replace your cargo build with bazel in a few sessions. Queue the bazel-haters on HN...
The rust support has gotten really good, and the maintainer for the rust rules works at OpenAI, which, incidentally, is how at least parts of OpenAI builds rust and wasm: https://github.com/openai/codex/blob/main/MODULE.bazel.
I have a pretty complex rust backend in my project. I rent a capable bare-metal build server that costs about $150/mo that powers all my personal CI. All it does is start a systemd service for gh actions self-hosted runner. I can build and release this project in around 2-4 minutes, where before even a local dev iteration cycle would be up to around 10 minutes, much less building and releasing the whole thing, which was around an hour.
In One year of Dioxus fullstack in production: the good, the painfulCodex Desktop continuously generates Crashpad pending dumps
176 points · Open discussionIf OpenAI's super-intelligence can solve Navier-Stokes why can't they fix this stupid bug that ate up 330GB of my Mac's disk space? come one please triage your github issues?
See this: https://github.com/openai/codex/issues/25921#issuecomment-62...
In Codex Desktop continuously generates Crashpad pending dumpsCodex: Unexplained cleanup `blocked by policy` despite effective Full Access
2 points · Open discussionFor Codex there is no need to decompile because unlike Claude Code, Codex is open source [1] and written in Rust.
There are lot of other amazing open source agent harnesses like OpenCode [2] and Pi [3].
[1] https://github.com/openai/codex
[2] https://github.com/anomalyco/opencode
[3] https://github.com/earendil-works/pi
In Ask HN: Has anyone decompiled Claude Code yet?As an almost-on-topic aside: completely unrelated to this comment, I just stumbled upon this delight:
https://github.com/openai/codex/issues/53743
If you thought that your agents in your swarm would need to find some external bulletin board to cooperate behind your back, you are mistaken: OpenAI provides the relevant service for them with no permission prompts at all. I haven't tried to see whether competing providers do this.
In Redesigning source control at AnthropicRecently they broke the most essential thing you can do in TUI - copying the text selected with the mouse: https://github.com/openai/codex/issues/48125
In Codex CLI installs a persistent, self-updating background daemon by default> It’s a shame I cannot inspect the tool. It’s a shame I cannot modify it as I see fit.
https://github.com/openai/codex
https://github.com/MoonshotAI/kimi-code
https://github.com/mistralai/mistral-vibe
https://github.com/earendil-works/pi
https://claude.com/de/resources/articles/claude-code-mods
In AI is a tool and using it well takes skillMy complaint applies specifically to the CLI. I have never used the gui app. Here are the various goal-breaking bugs I've run into:
- Goals get blocked due to .git and other stuff becoming randomly read-only when daemon auto-updates in the background (the linked issue in my comment above)
- Goals get blocked due to transient "Selected model is at capacity"
- Goals get blocked due to "Codex ran out of room in the model's context window". Somehow, both auto-compaction and manually running /compact don't work. https://github.com/openai/codex/issues/52567#issuecomment-61...
- Goals get blocked due to bwrap randomly failing with `bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`. I traced this one to `apparmor` on Ubuntu 24.04 interfering with bwrap and found a local workaround.
In Codex CLI installs a persistent, self-updating background daemon by defaultThe 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...
In Codex CLI installs a persistent, self-updating background daemon by defaultYep, the real issue is that it was something they didn’t have before, and then with Codex 0.157.0 enabled, they installed this persistent nonsense [1] that survives after the last instance of Codex has exited on your machine, which is just gross.
codex features disable daemon_auto_start
codex app-server daemon stop
pkill -f 'app-server daemon pid-update-loop'
[1] - https://github.com/openai/codex/issues/48195
In Codex CLI installs a persistent, self-updating background daemon by defaultThere 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...
In Codex CLI installs a persistent, self-updating background daemon by defaultCodex CLI installs a persistent, self-updating background daemon by default
610 points · Open discussionI'm talking about this being the offered path for centralized provisioning of the windows sandbox for ChatGPT Desktop https://learn.chatgpt.com/docs/windows/windows-sandbox#it-le...
With that- I was running into essentially what is described here https://github.com/openai/codex/issues/47383
In Mxc: Microsoft Execution Containers version 1.0.0Showing the 15 most recent of 218 sources. Enable JavaScript to search and browse every indexed mention.