HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
openai
codex
Rust2025–2026
openai / codex

codex

Lightweight coding agent that runs in your terminal

Command LineAI & Machine Learning
Explore on GitHubRead Hacker News discussions
163Distinct people
218Mentions
2Explicit recommenders
135.1KGitHub stars
REPOSITORY AT A GLANCE

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

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:17:07 AM UTC.

Announcing .NET 11 direct repository linkDebated

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 8

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.

0102030402025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 commentsApr 20252025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 12 mentions; 6 submissions, 6 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 13 mentions; 4 submissions, 9 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 14 mentions; 6 submissions, 8 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 14 mentions; 6 submissions, 8 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 15 mentions; 6 submissions, 9 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 41 mentions; 10 submissions, 31 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 11 mentions; 6 submissions, 5 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 16 mentions; 4 submissions, 12 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC1129
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC514
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC1037
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC514
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC404
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC826
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC312
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC1266
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC826
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC1349
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC1468
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC918
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC1468
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC927
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC1569
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC411031
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC1165
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC1019
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC16412

What Hacker News says

10 sources
incomingpain·Jun 23, 2025
stack overflow was declining for years, long before chatgpt. Clear in that graph. https://www.theregister.com/2019/10/01/stack_exchange_contro... It's completely within their right to eject people based on political opinions. I dont understand why a gender neutral website of anonymous people talking about gender neutral tech has any reason to inject gender or even be concerned about it. According the graph, 2017 peak, but when chatgpt launched, they were already 50% declined. After chatgpt, it increased the rate of decline but hardly was causal. >Reddit and other forums Reddit is declining just like Stack; for the same reasons. >A new product similar to Stack Overflow but tailored to the AI era with better user experience might emerge to bridge the gaps. Developers could ask questions in a centralized place and LLM providers could access
Read the rest
the difficult coding questions The one thing I recommended to github. Lets find a random issue for example: https://github.com/openai/codex/issues/1330 Why couldnt various AI have commented some answer? Perhaps co-pilot could read it, produce a fully tested agentic patch that maintainers could look at?
In How do LLMs and AI coding tools solve new problems when Stack Overflow is dead?
simonw·Jun 15, 2025
The situation on macOS is so frustrating. sandbox-exec / seatbelt has been marked as deprecated for nearly a decade now (since macOS Sierra in 2016) but it's still what everyone uses - here's OpenAI using it for their new Codex CLI: https://github.com/openai/codex/issues/215 Maybe the new "containers" stuff in macOS 26 is going to be a good replacement for that? It seems like that's a different solution though. All I want is an easy, documented, supported way to run a binary on my computer and say "it can only access these files, use this much RAM and it's not allowed to make any outbound network requests". It always surprises me how hard this is!
In How easy is it for a developer to "sandbox" a program?
mdaniel·Jun 1, 2025
For all this "AI is the future," how in the world does OpenAI's own codebase still have "TODO" comments for the most trivial thing I can possibly imagine? <https://github.com/openai/codex/blob/rust-v0.0.2505302325/co...> made extra wtf by a comment at the top of the file laying out that requirement, so no "?" required <https://github.com/openai/codex/blob/rust-v0.0.2505302325/co...> I would bet it took more wall-clock time to type out that comment than it would have for any number of AI agents to snap the required equivalent of `if not re.match(...): continue` into place
In Codex CLI is going native

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.