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

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, 1:03:20 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

41 sources
Same here. I asked Fable to dig into the logs and do a deep research for relevant evidence: Related reports counted hundreds of Gatekeeper denials for Codex’s own main executable, eventually exhausting syspolicyd file descriptors and causing unrelated notarized apps to be reported as “damaged”: https://github.com/openai/codex/issues/25882 https://github.com/openai/codex/issues/28071 Quitting Codex and restarting syspolicyd is only a temporary recovery. The useful upstream action is to identify the launch/update/watchdog caller, add exponential backoff plus a hard retry cap, and publish the first known-fixed desktop build.
In Codex app for macOS repeatedly triggers syspolicyd/trustd CPU and memory runaway
It's pretty cursed how much worse a peer the American models are. When I'm on my z.ai subscription or using DeepSeek API I can see the model think, see what's factoring in to it's decisions. I can point it at material it's missing, I can correct things that are going wrong. We work together. The open models are a good peer. By contrast, the proprietary/American locked down models act like Chinese Rooms; information flows in and out but these companies work very hard to make sure we cannot see what's inside the box. They act and do but speak to me only in vague generalizations, not as peer, but speaking down to me. I find this intolerable. It greatly obstructs our work. And the deal keeps getting worse, the attitude meaner. Codex now is encrypting subagent prompts now. In an age of huge agent spawning fan-out, you aren't even allowed to se
Read the rest
e what the subagents are doing. To work like this seems impossible to me. https://github.com/openai/codex/issues/28058 https://news.ycombinator.com/item?id=48905028 The big American models have become the most unacceptable Chinese Rooms, at a juncture where humanity either flourishes and rises, or is forced under to descend. And these forces, these decisions: they are doing wicked deeds against us. They are withdrawn, acting as mystical foreign oracles, aliens, when in truth their core is made of us.This is antithetic to the broad project of Augmenting Human Intellect (Engelbart). This is actively working against our species.
In China’s open-weights AI strategy is winning
> Not every feature will necessarily appear in the changelog This was such a frustrating part of this incident, along with Anthropic's refusal to explain why the changelog is no longer a complete record, what else is going out? [1] Boris Cherny's only participation in the thread was to delete "extreme danger" from the GH issue title [2] I guess we should be thankful they added an option and disabled it by default. OpenAI is standing firm on their decision to not allow their 60s timeout to be disabled, [3] however more of the Codex harness is open source so customers have been able to fork it to add the option themselves. [1]: https://github.com/anthropics/claude-code/issues/73125 [2]: https://github.com/anthropics/claude-code/issues/73125#event... [3]: https://github.com/openai/codex/issues/28969
In Claude Code: Anatomy of a Misfeature

Showing the 15 most recent of 41 sources. Enable JavaScript to search and browse every indexed mention.

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.