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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:53 AM 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 29 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
11 sourcesTMtmpnode·Aug 30, 2026Submission
Data Exfil: OpenAI polices private chats exfiltrated through Codex Memories
2 points · Open discussionCan a harness have a true deterministic scheduler and task orchestrator?
1 points · Open discussionI have built a pretty full version of that idea in rust (codex tui2). There's a while tonne of downsides that make it basically impossible to really get to 100% good on this.
> Under the hood it's still a terminal app, but from the UI author's perspective you're not fighting terminfo, CSI sequences, or varying terminal support. You get proper cursor tracking, scroll regions, and editable text areas out of the box.
All that is not true. Take scrolling for example. Each terminal emulator implements this subtly differently (mouse/trackpad/speed etc.), scrolling will never feel native unless you push the control of it into the terminal emulator.
There's more than that, each and every point on this becomes something that you have a gap between native and the terminal emulator that you're building to run in the terminal.
See https://github.com/
Read the rest
openai/codex/issues/8344 and https://github.com/openai/codex/pull/9640
Claude code and gemini have both had various versions of the same idea at times. I'm unsure where they ended up.
OpenAI Codex adds hidden "Daybreak Blue" and "Daybreak Red" cybersecurity models
2 points · Open discussion> Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight.
What sucks is that every issue tracker for these agent harnesses are the same, and this shit hides real issues!
For example, Codex started encrypting messages from a agent to the sub-agents when you use Sol + Ultra, which is terrible for debugging for obvious reasons. This GitHub issue exists for this: https://github.com/openai/codex/issues/28058
Fine, the opening issue isn't concise exactly, but it's mostly clear what's going on. After a few messages, someone who uses LLMs without reviewing their output starts participating in the discussion, pastes huge walls of texts completely missing the point and overall just bloating the conversation so now whenever a maintainer actually want to address it, they have to wade through 20+ mess
Read the rest
ages of just pure shit and bloat, to even understand what's going on.
Kind of wish some projects started having forums specifically for people who pay for forum access, or some other gate to get rid of these LLM lowlifers who cannot compose a simple message to explain what's in their head, and instead have to ruin perfectly fine conversations/discussions with their verbal poop.
Codex on AWS bedrock bug causing 10x charges
148 points · Open discussionSince when?
https://learn.chatgpt.com/docs/codex/cli
https://github.com/openai/codex
Looks like it's still a more-or-less-open-source product called Codex CLI.
FWIW, there have been issues with various versions of ChatGPT not knowing what Codex is -- at least in the (IIRC) GPT-5.3 timeframe, there were serious issues with the knowledge cutoff.
In Asana cleared 5 years of engineering work in 2 weeks with CodexCodeX v0.148.0 cannot use GPT-5.6 Sol
1 points · Open discussionCodex adds experimental thread/revert support
2 points · Open discussionI 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.
In Codex in ChatGPT desktop app for Linux is now in previewMinor factual correction: The Codex client is open source. https://github.com/openai/codex
In What I learned by putting GitHub Copilot behind a MitM proxy