Tag

Codex

13 stories

Not just a headline — the discussion unpacked

The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.

Ask HN: what do you do when you ship AI-written code you don't understand? (news.ycombinator.com)

An Ask HN thread asked how engineers cope with shipping LLM-written code they haven't fully read. A Hasura engineer says his own system became fuzzy once he moved from IDE autocomplete to Claude and Codex CLIs, and argues the answer is formally verifiable code.

The loudest counter: you already ship code you haven't read. Principal engineers always have.

💬Ask HN ★ 276 · 💬 414 · Oct 20 · #AI#dev tools#programming#Claude#Codex#Hasura+1

DeepSeek now sells web search and page fetch for $0.75 per 1,000 requests (api-docs.deepseek.com)

DeepSeek published Search and Fetch APIs at $0.75 per 1,000 successful requests, billed only on HTTP 200 responses. Calls routed through Claude Code, Codex or DeepSeek's own harness are free until 00:00 Beijing time on November 1, 2026.

The first reply was a price check: Kagi's API runs $12 per 1,000 searches. Then a hobbyist who built his own agent tools said the big labs' bundled search costs 15-20x more than his.

🚀Tech ★ 551 · 💬 260 · Oct 19 · #AI#dev tools#web#Brave Search#Claude Code#Codex+2

A 232× kernel experiment makes verification the agent skill (sankalp.bearblog.dev)

The experiment paired an agent with benchmarking, profiling, research, and correctness verification. That made optimization a constrained search problem.

HN readers reported that agents work best where a system supplies a hard answer. They fail more readily when success depends on credentials or a human-operated dashboard.

🚀Tech ★ 413 · 💬 90 · Aug 16 · #AI#dev tools#programming#Codex#Intel VTune

A teardown said stop using OpenCode. A core developer showed up to reply (wren.wtf)

The complaints ran from petty (re-reading its whole config file every turn, wrecking prompt caching) to serious: approving one throwaway Python command with "Always" silently green-lights every future Python call, including one that reads your SSH keys.

Simon Willison defended one pettier complaint, baking the date into every prompt, as standard practice. OpenCode's own developer said the harshest bug, a context-pruning behavior, was already disabled by default months before the post went up.

🚀Tech ★ 368 · 💬 244 · Jul 21 · #AI#dev tools#security#Claude Code#Codex#OpenCode+1

OpenAI's new "Ultra" mode arrives — and an employee says the token scoreboards became "use cheaper models" emails (twitter.com)

The announcement is thin — Ultra reportedly uses subagents to go beyond a single agent. The thread fills with access logistics and a guess that Pro-tier already runs ~12 parallel agents synthesized into one answer.

The reversal is a corporate weather report: praise for the biggest token users flipped to weekly emails begging for restraint — arriving just as OpenAI reportedly found a way to halve inference cost.

🚀Tech ★ 82 · 💬 40 · Jul 6 · #AI#big tech#Codex#GPT-5.6#OpenAI

GPT-5.5 Codex keeps stopping at exactly 516 reasoning tokens and getting it wrong (github.com)

Across 390,195 logged responses, GPT-5.5 Codex terminates reasoning at exactly 516 tokens far more than any sibling: 82% of exact-516 events are GPT-5.5, though it's only 19% of traffic. The stops cluster at 516, 1034, and 1552, each about 518 apart.

One HN user reproduced it live: 4 of 10 identical prompts short-circuited at 516 tokens, and every one returned the wrong answer.

The suspected cause: a throughput optimization batching reasoning in multiples of 512.

🚀Tech ★ 166 · 💬 52 · Jul 5 · #AI#dev tools#open source#Claude#Codex#GPT-5.5+1

Z.ai's ZCode chases Claude Code with GLM-5.2, and looks a lot like Codex (zcode.z.ai)

Plans run from $16.20 to $144 a month, and GLM Coding subscribers get a quota discount inside ZCode: peak hours (14:00-18:00) drop from 3x to 2x and off-peak from 1x to 0.67x, roughly a 1.5x effective allowance. The base allowance itself is never stated in tokens.

Developers ask why a lab that open-weights its models keeps the harness closed, and a Chinese-owned agent with full system permissions drew explicit trust warnings.

A Show HN keeps your Mac awake while AI agents work. The thread: that's a built-in command and a 15k-line reinvention (github.com)

Adrafinil, a Show HN named after a modafinil derivative, keeps a lid-closed Mac awake only while AI agents are working, then sleeps. Useful — until the thread points at the wheel it reinvents.

macOS ships 'caffeinate -dimsu.' Amphetamine has done conditional triggers for years. One commenter compressed the whole thing to a three-line shell loop; another asked why a sleep toggle needs 15,000 lines of code; a third noted the coding agent itself just shipped the feature.

🚀Tech ★ 93 · 💬 56 · Jun 28 · #AI#dev tools#Adrafinil#Amphetamine#Codex+1

Claude went down again, and a user recomputed its real 90-day uptime: 97.68% (status.claude.com)

Another Anthropic outage hit mid-session: 500s, then 529 Overloaded, then a status page one user compared to Christmas ornaments. A reader scraped the page's own incident data and recomputed the real figure: 97.68% uptime over 90 days, roughly 50 hours of degraded service.

The sharper thread isn't the downtime. It's developers asking how a shop that says it runs on agent loops fixes its own infra when the agent is the thing that's down.

A researcher spent 700M tokens having an AI build the TikZ editor LaTeX users always wanted (tikz.dev)

TikZ Editor lets you draw figures visually and outputs TikZ/LaTeX code, open source and on the web. The most-praised use isn't drawing from scratch — it's editing old TikZ without turning the source into generated soup.

Maker DominikPeters says it took 700M tokens since February via a ChatGPT subscription. A LaTeX user in the thread flagged the catch: every node lands at absolute coordinates, which is rarely how good TikZ is written.

OpenAI's Codex quietly wrote 640 TB a year to your local SSD (github.com)

The SQLite log kept only ~500K rows, yet its autoincrement counter had passed 5.5 billion: a frantic insert-and-prune churn, 70.7% of it raw TRACE noise. The cause was a one-line default capturing every diagnostic at Level::TRACE. A maintainer who'd hit an identical bug years before pushed back on the slop jokes, then someone found Claude Code doing the same thing.