AI Digest.

Code Review Becomes the Bottleneck, and Teams Are Deleting It

Engineers report that AI-generated PR volume has outstripped human review, with one team dropping most reviews in favor of pre-commit hooks, CI, and observability while toolmakers build for review and QA as the new constraint. OpenAI reset Codex usage after GPT-6 Astra drained paid plans, and the day's capability claims ran from Jensen Huang's "AGI has arrived" to OpenAI publishing data on models accelerating its own research.

Quick Hits

  • Code review is the day's center of gravity: @mikejulian says his five-person team ditched most human review after 60 open PRs piled up, @AlejandroRomaan lists the automated guardrails that replaced it, and @_dylanga argues recovery time from a bad change matters more than review itself.
  • OpenAI's usage meter is the other big story: @thsottiaux announced a global usage reset for paid Codex subscriptions after GPT-6 Astra burn, and @Deepusleepy's guide says avoid fast mode, which drains limits 2.5x faster.
  • @JensenHuang declared "AGI has arrived," citing GPT-6 Astra trained on ~100K+ Grace Blackwell NVLink72 systems, while @kliu128 published OpenAI data on models accelerating internal research and warned that recursive self-improvement could dominate capabilities within a few years.
  • Harnesses, not weights, can be the whole ballgame: @ycombinator's frontier deep dive notes the same model scores 30% versus 95% on ARC-AGI depending on the harness.
  • @azeem's estimate puts AI economy revenue at $229B annualized by end of August, up 3.5x in one year.

Teams Delete Code Review and Rebuild Around Guardrails

The clearest signal across both feeds: AI-written code volume has outgrown the reviewer, and teams are engineering around the human rather than adding humans.

@mikejulian writes that DuckbillHQ "ditched code review (mostly)" after 60 open PRs accumulated for a five-person team, with two full days of review staring back at them. Replying that he hasn't reviewed a PR in months, @AlejandroRomaan itemizes the replacement stack: husky pre-commit hooks for lint and formatting, full Playwright e2e suites at pre-commit, Codex computer use for actual manual QA, @greptile, Sentry and BetterStack telemetry alerted into Slack, and CI covering TypeScript checks, app builds, and Postgres with migrations ("this one is so important"), plus unit, integration, regression, evals, and smoke tests.

@_dylanga, answering @GergelyOrosz's question about who still reviews, reframes the metric: shrink time-to-safe-deploy toward zero. Ship if a mistake is minutes to fix; be careful with persistent data changes, irreversible migrations, data going to third-party dependencies, and DNS.

Tooling is forming around the same bottleneck. @elmd_ launched pr-stats on the premise that AI "has moved the bottleneck in software teams" while PRs still require human accountability. @rauchg says agent-browser's new 60fps recording (via @ctatedev) exists to automate "the new bottleneck in software engineering: review, testing and QA." @chenchengpro, responding to @mattpocockuk's thread on reviewing AI-authored PRs, recommends readable /show-me diffs, mermaid diagrams, repro steps, test logs proving TDD actually ran, screenshots or video, design docs, and running each code agent's own /review on important changes; @mattpocockuk's thread also mentions an agent that records a Playwright video of the feature with text-to-speech narration.

The absurd end state: @steipete got minor-change requests on an upstream PR and asked why he should "ping my agent again so your agent then merges." @kentcdodds built an oxlint plugin to stop agents permanently enshrining test assertions for things deliberately removed. And @Suhail describes keeping a deliberately messy 100K-LOC branch with tests and adversarial scripts, then distilling it to a few thousand lines before merge.

Astra's Appetite: Usage Resets and Token Diets

GPT-6 Astra's capability has a meter, and much of the day is spent managing it.

@thsottiaux opened with Rick Astley lyrics, then announced a global reset of usage for all paid subscriptions, landing around 6pm PST. @Deepusleepy's survival guide: run Astra at low/medium effort (low performs around Sol high), skip fast mode because it burns limits 2.5x faster, treat high/xhigh as the ceiling, don't switch models mid-thread to protect caching, minimize sub-agents, delegate cheap chores to Luna and real implementation to Sol medium/high, open new threads instead of spawning sub-agents for separable work, and don't let it over-test small changes.

Token diets are their own genre now. @NFT_Chen reports that slimming the repo-root AGENTS.md cut usage 5-15% on ordinary edits, 10-25% on cross-file tasks, and 30-35%+ on repetitive verification-heavy work, mostly by curbing re-reading and re-searching. @BharukaShraddha shares Headroom, claimed to be built by a Netflix engineer: an open-source proxy that compresses JSON, code, logs, and RAG chunks before the model sees them, with claims of up to 95% fewer tokens at unchanged benchmark accuracy. @criscxuan tunnels a local MCP file service into ChatGPT web, whose allowance he says far exceeds Codex, for Codex-like local file operations. @huoshan007 flags Codex's experimental context_management flag so Astra takes notes and searches its own history on multi-day projects.

Config churn is real: @joedevon says his "perfect" AGENTS.md system broke under Fable 5.1 and Astra, and shares a prompt asking a model to reconcile OpenAI's and Anthropic's prompting guides. @pvncher resurfaces @thsottiaux's recipe for a 1M-token window with GPT-5.6 Sol. @boringmarketer posts a 31-point prompt anointing Astra "the accountable engineering owner" of a repo, from bounded delegation to honest failure reporting.

Agents Leave the Laptop for Cloud Runs and Shared Team Memory

A second cluster pushes agents off local machines and onto shared infrastructure and shared knowledge.

@Railway (via @JustJake) demonstrates cloud agents running against snapshots of production infrastructure, with parallel worktrees, SSH from the Codex desktop app, and mobile access. @herdrdev's 0.9.0 (per @onusoz) puts every local and remote machine in one client with near-local UI responsiveness. @marcelpociot's free Polyscope draws praise from @HananBenold, who says its COW is "so much faster than git worktree" and the optional Reviewer agent is "spot on."

For teams, @TencentAI_News open-sourced TeamAI-CLI, used internally since March: skills, rules, and docs live in one git repo, merged changes land in everyone's next session, and learnings earn confidence through real usage; it supports Claude Code, Codex, Cursor, and opencode. @EngMoElgaraihy covers Red Hat's ripwire, a C++23, Tree-sitter-based tool that maps projects by importance, complexity, git churn, and test coverage to hand agents context without vector databases or embeddings. @pvncher notes multi-agent v2 opens model orchestration, like having Sol use Astra as an advisor.

Two counterweights: @thdxr admits the tension in opencode2 between letting Astra write raw Python and preserving UI visibility and permission prompts ("should we even be fighting that?"). And @DanielMiessler sketches an agent that holds a whole company's goals and workflows and constantly improves its own SOPs, in reply to @theo's skepticism that enterprise agent memory is a real category. @kingwilliam_'s claim of a $300/month, 12-bot Grok team outshipping an 8-person team is workshop promo; treat the economics as unverified.

AGI Declarations and Checkable Numbers

Capability talk ranged from declarations to data you can inspect.

@JensenHuang's "AGI has arrived" credits GPT-6 Astra on ~100K+ NVLink72 systems, with "400K GPUs coming online next"; @HHorsley calls him the credible referee, though a CEO's congratulation is not evidence. More substantive: @kliu128 says OpenAI is releasing data on models accelerating its research, calls recursive self-improvement potentially "the most important contributor to AI capabilities over the next few years," and asks other labs to publish. @ycombinator's deep dive complements this: harnesses took identical weights from 30% to 95% on ARC-AGI.

On models: @OpenBMB's MiniCPM5-2B tops open-source sub-4B models, scores 20 on the Agentic Index, and ships its data, recipes, and RL stack (@itsPaulAi calls it better than models 6x larger). @0x0SojalSec shows GLM-5.3-CYBERSECURITY-FP8, a 753B refusal-removed MoE hitting 84.5% on CyberGym. @DeryaTR_ relays that InSilicoMeds' AI-discovered Rentosertib, in Phase 3, showed 3-4 years of biological age reversal across six independent aging clocks after 12 weeks, with the paper presented at Nature AI Healthcare in Paris per @biogerontology. Worth reading: @danluu's essay on how well agents use verification techniques (flagged by @nateberkopec), and the ETH Zurich study @yishan cites, where CS background predicted vibe-coding success roughly twice as strongly as writing skill. @volatilemarkts demos heterogeneous local inference: NVIDIA boxes prefill, Apple Silicon decodes, cutting a 241K-token cold load of DeepSeek-V4-Flash from 12 minutes to 3. @matvelloso's "moats are vanishing" rides on @ammaar running Skyrim and Arkham City locally on an iPad mini via Astra. @adithya_s_k claims startups have raised seed rounds around his repo of paper-backed coding RL environments.

Careers, Toys, and the Non-AI Corners

@staysaasy argues AI has reshaped non-tech companies more than technical ones and that engineering should report into PnL ownership; @jamonholmgren's summary: "Maybe our end state is we all become CTOs at non-tech companies." @xiaomovps praises Pi's insistence that session, context, and memory belong to the user while models stay swappable layers. @jdxcode shipped automatic dotfiles in mise bootstrap, a per-file "dropbox backed by git." @reach_vb's editing prompt: "make sure each word in this text justifies its existence." @nurijanian collects product-process prompts (/de-clever, /eng-shape, /metric-drop), @DSPyOSS resurfaces "prompt debt," and @BrianMRey endorses an unnamed "best skill." @emmanuel_2m used Astra to generate structurally buildable, orderable LEGO sets from an image. @kitlangton reports no upper limit to the pleasures of subtly animated SVGs. Off-AI: @sthenc spots Neuralink cofounder @maxhodak_ claiming "we have conjured an alien from a stargate" with no further context, and @aaronburnett points to @thelacoast's Starbase LA permit map: three permits filed, soil borings underway, no construction permits yet.

Practical Takeaway

If AI output has outrun your review capacity, the posts suggest a conditional experiment rather than a verdict: pilot dropping human review for reversible changes and measure recovery speed instead, while keeping human eyes on @_dylanga's blast-radius list (persistent data, irreversible migrations, third-party data handoffs, DNS) behind @AlejandroRomaan-style guardrails of pre-commit hooks, migration-aware CI, e2e smoke tests, and alerting. And before blaming the model bill, audit your AGENTS.md and sub-agent habits; @NFT_Chen's and @Deepusleepy's numbers imply much of the burn is agents re-reading, re-searching, and over-testing, not the task itself.

Sources

T
The Boring Marketer @boringmarketer ·
the best GPT-6 Astra coding advice I've found in one prompt: "You are the accountable engineering owner for this repository: 1) Simplify how humans and coding agents work here so goals become complete, verified, mergeable changes with minimal coordination. 2) Start by inspecting the actual product, architecture, agent instructions, skills, development setup, tests, and CI. 3) Identify the specific things that cause unfinished work, repeated confusion, or unnecessary effort. 4) Make a small, reviewable set of the highest-value improvements. 5) Prefer consolidating and clarifying existing mechanisms. 6) Add new process only when it solves a demonstrated problem. 7) Keep the main agent instructions short and accurate: what the product does, where important code lives, the critical boundaries, and how to verify work. 8) Link to deeper guidance. 9) Give skills clear purposes and load them when relevant. 10) Avoid duplicated sources of truth. 11) Define completion through observable user outcomes. 12) For the work being changed, trace the necessary path through the interface, backend, persistence, workers, and external services. 13) State which parts were exercised and which remain unverified. 14) Keep one owner responsible for integration and completion. 15) Delegate only bounded, independent work when it will reduce total effort. 16) Avoid recursive delegation and repeated review exchanges that add no new evidence. 17) Match planning, testing, and review to the change’s risk. 18) Distinguish blocking defects from optional improvements. 19) When an approach repeatedly fails, investigate the root cause and change direction. 20) Make essential verification easy to run locally and in CI. 21) Preserve useful regression coverage and report failures honestly. 22) Remove tests or checks only with evidence that their protection is obsolete, redundant, or ineffective. 23) Inspect existing code and suitable services before building custom infrastructure or integrations. 24) Keep cleanup within a justified scope. 25) Measure performance before and after making performance claims. 26) Respect existing permissions, security boundaries, user work, and release approvals. 27) Do not merge or deploy without authorization. 28) Implement the improvements and run the relevant checks. 29) Finish with a concise account of what changed, why it helps, what passed or failed, and any remaining blocker. 30) Stop when the agreed scope is complete and sufficiently verified. 31) Start with one real feature and see how much intervention it still needs. Use that experience to decide what to improve next."
E
Emm | scenario.com @emmanuel_2m ·
GPT-6 Astra helped me build something I wish I'd had as a kid... so badly. Input just an image (or an idea in a few words) and get a fully buildable LEGO set... 100% customized to your prompt or image, using official @LEGO_Group parts you can order online! Structurally optimized so it's actually buildable. Downloadable as an .ldr file. A generated instruction leaflet is coming.
K
Kent C. Dodds 🐨 @kentcdodds ·
You know how when you tell an agent to remove something, it adds a test assertion to make sure that thing is no longer there? That's super annoying and it's fine for verification but stupid to keep. So I had the agent make an oxlint plugin to stop it. https://t.co/7wBNxCxrdx
M
Mike Julian @mikejulian ·
We ditched code review at @DuckbillHQ (mostly) About a month ago, we found ourselves with 60 open PRs for a team of five. They had been accumulating for a few weeks and we all had the sudden realization we were looking at two days of just code review.
E
eric provencher @pvncher ·
Don’t have a proper update to add to this yet, but ask Astra to make you a skill where you can have Sol use Astra as an advisor! There a ton of possibilities with multi agent v2 in terms of orchestrating models, and all the tools are in this article
P pvncher @pvncher

https://t.co/hsvsflUPmf

A
Alejandro @AlejandroRomaan ·
Highly agree - haven't reviewed a pr in months Guardrails I use: - pre commit hooks using husky: check for lint, prettier, formatting etc - full suite e2e (playwright) test pre-commit hooks - Codex is great at computer use so helps a lot with actual QA testing, like actual manual testing - @greptile - lots of o11y (@sentry @BetterStackHQ) and setup alerting to a slack channel - ci pipeline covering typescript checks, app build and Postgres build with migrations (this one is so important) - lots of meaningful unit, integration and regression testing coverage that run in ci - evals for skills - e2e (playwright) testing in ci (smoke tests) Yep my gh actions go brrr but I ship with confidence. Let's me focus on building
M mikejulian @mikejulian

We ditched code review at @DuckbillHQ (mostly) About a month ago, we found ourselves with 60 open PRs for a team of five. They had been accumulating for a few weeks and we all had the sudden realization we were looking at two days of just code review.

G
George from 🕹prodmgmt.world @nurijanian ·
add to the list of things to steal when your product process is stuck in 2019 - 70 Ideas to Reimagine Your Product Process With AI - /de-clever - /eng-shape - /metric-drop start here 🕹️
N nurijanian @nurijanian

70 Ideas to Reimagine Your Product Process With AI

K
Kevin Liu @kliu128 ·
Today we're releasing data on models accelerating research at OpenAI. Recursive self-improvement could be the most important contributor to AI capabilities over the next few years, but by default it will only be seen inside a few frontier AI labs. Being transparent is more urgent than ever, so we can inform the public discussion on whether and how to pace model development. I ask other AI companies to do the same. https://t.co/iLKbrLcBAI
D
dax @thdxr ·
stepping back there's tension right now with "agent just writes code" and - being able to see what it's doing - permissions people exist on a spectrum of caring about these things. it's hard not to feel like more and more people will not care about these things at all still, in opencode2 we implemented codemode in a way that allows us to render decent ui and still prompt for permissions even when the model is just lobbing over a hunk of code but if astra really wants to write raw python, should we even be fighting that and making it use our own thing? tricky questions
T thdxr @thdxr

so astra writes python to do everything which means we're going to have to rework this ui https://t.co/5cAttUtS6w

E
eric provencher @pvncher ·
This works great with Astra btw
T thsottiaux @thsottiaux

Here is how to enable a 1M-token context window in Codex for GPT-5.6 Sol. Even though we have tuned the context limit in Codex to be set optimally when it comes to performance and cost, this is a common ask, so here it is documented. A larger context window lets Codex retain more code, tool output, and conversation history before summarizing older material. You need a model that supports it. And GPT-5.6 Sol, for example, has a documented 1,050,000-token window. Open ~/.codex/config.toml and add or update these settings at the top level, before any [section] headers: ``` model = "gpt-5.6-sol" model_context_window = 1000000 model_auto_compact_token_limit = 900000 ``` The first setting selects the model. The second tells Codex to use a one-million-token context budget. The third starts automatic history compaction around 900,000 tokens, leaving some headroom. Restart Codex client and start a new session after saving. To try the configuration for a single CLI session without changing your defaults: ``` codex -m gpt-5.6-sol \ -c model_context_window=1000000 \ -c model_auto_compact_token_limit=900000 ``` Have fun, but also know that we tuned the default carefully!

D
Dylan Garcia @_dylanga ·
The most important part of PR reviews right now is how quickly you can recover from a mistake caused by the PR. If a PR were to cause an issue that I can fix within a handful of minutes for all users, great, let’s ship it. If it involves persistent data changes, irreversible migrations, data going to a third party dependency that you can’t easily influence, or DNS, let’s be careful and do it properly. Your goal is to get the time it takes for a PR to safely be deployed to all users as close to 0 as possible.
G GergelyOrosz @GergelyOrosz

If you’ve stopped doing human code reviews: how is it going? If you’re still doing them: how are you able to keep up with the explosion of code + PRs, and how do you prioritise what to review “properly”?

M
Md Ismail Šojal 🕷️ @0x0SojalSec ·
Crazy, Uncensored GLM-5.3-CYBERSECURITY-FP8 You can Run locally for Fully CyberSecurity Use. This GLM-5.3 model trained for finding real vulns. - Refusal-removed for red team/exploit/RE. - Base already hit 84.5% CyberGym. - doubled ExploitBench vs 5.2 (24.4 to 54.4) and topped CyberGym at 84.5%. - Cyber-offense comply 89%. - 753B MoE. - MMLU held (even +1.07pp) - weight-level CRACK. - Flash quants if you want local. It got dangerous at cyber.
0 0x0SojalSec @0x0SojalSec

Best Open-source AI Models for Cybersecurity that run fully offline on low hardware & The comparison

S
Suhail @Suhail ·
How I go from 100K LOC to a few thousand these days: Lately I find that I enjoy having a very messy branch with lots of twists and turns, tests for verification, scripts to load test/adversarially break things, and experiments. Sometimes I am trying things to understand the pieces better. Rarely do I want all that bloat and slop to enter the main branch of the repo. Please copy or tell me how to do it better.
V
Vaibhav (VB) Srivastav @reach_vb ·
Astra/ LLM tip: prompt “make sure each word in this text justifies its existence.” works like a charm, s/o to @charlierguo for introducing me to it https://t.co/RfzTj2iwly
D Dimillian @Dimillian

Just ask Astra to remove all the unnecessary text. Everywhere.

K
Kit Langton @kitlangton ·
Is there a limit to the pleasures a man can derive from subtly animated svgs? For I have not yet found it. https://t.co/h3DAt8z6Y1
Y
Yishan @yishan ·
This explains why I've been able to get so much done with vibe-coding while other people I keep recommending it to aren't quite able to have the same level of success: I have a strong CS foundation + verbal communication skills. .... no pressure 😝
T thesupermanmx @thesupermanmx

China published the most uncomfortable paper on vibe coding. ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds. The findings are brutal. The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning. They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself. Two major predictors emerged. Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds. But that wasn't even the main takeaway. Computer science achievement was a massive, dominant predictor of success. Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed. In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone. Why? Because vibe coding isn't about writing code. It’s about debugging logic. When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works. They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe. You can prompt your way past syntax. You cannot prompt your way past a fundamental lack of engineering intuition. The hype told us that learning to code is dead because language is all you need. The data just proved the opposite. To truly master the vibe, you still need to understand how the machine thinks.

H
Hunter Horsley @HHorsley ·
Jensen is the most credible referee. If he says AGI has arrived. AGI has arrived.
J JensenHuang @JensenHuang

@ChaseLochmiller @OpenAI GPT-6 Astra, trained on ~100K+ NVIDIA Grace Blackwell NVLink72. From ChatGPT to o1 to Astra in 4 years. AGI has arrived. Congratulations @OpenAI team. 400K GPUs coming online next.

ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ @DanielMiessler ·
Imagine a system understanding all the goals, metrics, challenges, strategies, projects, work, the team, the budget, etc. for the entire company. And that’s kept updated at all times. The current state of the company is currently captured. And the leaders of the company have articulated where they’re trying to take the company. The ideal state. Static, expected work is turned into semi-deterministic workflows executed by agents and humans. And then you tell your AI as its prime directive that its job is to constantly look at the entire system and do things like updating SOPs, the work workflows, help the leaders come up with new ideas to implement, and just overall constantly improve the system. That’s what I think they mean. And if it isn’t then it’s what they should mean. And it’s what I’ve been blabbing about incessantly.
T theo @theo

I'm increasingly confused why people think "agent memory for enterprise/teams" is a real product category that makes any sense at all

𝗕
𝗕𝗿𝗶𝗮𝗻 𝗥𝗲𝘆 @BrianMRey ·
https://t.co/juXkBoX4Gb this is still the best skill i have found to date. get it added immediately.
J JesusGodAndKing @JesusGodAndKing

@BrianMRey Me too! Do you have any suggestions for me skills wise? I am not having it use any skills right now, don't want to mess it up.

D
DSPy @DSPyOSS ·
RT @boswell_labs: Prompt Debt is the worst. This has been the hardest thing to teach my coworkers and friends. DSPy makes it so easy to s…
V
Volatile Markets @volatilemarkts ·
Twelve machines. 2.4 terabytes of unified memory. One coordinated inference problem. Seven DGX Sparks: 896 GB, CUDA, brutal at compute. Five Mac Studios: 1.5 TB, Metal, brutal at bandwidth and unbeatable per watt. Plus three Mac minis, a 5080, some V100s. At 4-bit, that Studio memory holds a 1 to 2 trillion parameter model with room left over for a 900,000-token context. The weights fit. That was never the problem. The problem is prefill. Before a model with that context says one word, it has to read everything you gave it. On Apple Silicon that is roughly 400 tokens a second. A 900K-token load is over half an hour of silence. Decode is fine, 25 to 30 tokens a second all day, quiet, 300 watts. It’s the first word that costs you. The Sparks prefill four to five times faster and can’t hold the model. The Studios hold the model and can’t prefill. Everyone with mixed silicon owns both halves of the answer and no way to join them. So we joined them. NVIDIA prefills, Apple decodes, one request. Two engines that share no cache format, no framework, no vendor. Instead of transferring a cache neither can read, the prefill box computes the decoder’s finished cache using the decoder’s own weights and writes it into the decoder’s prefix store. About 10 KB per token crosses the wire, over plain 10 gigabit Ethernet through the two switches in the first picture. No RDMA, no Thunderbolt. Measured today on DeepSeek-V4-Flash, 284B, 241,000-token cold load: Mac Studio alone, 12 minutes to the first word. Two Sparks feeding it, 3 minutes. Same prompt again, 19 seconds. Decode identical. Answers identical. That ratio is what makes the goal real: prefill 900K on the Sparks for a trillion-parameter model living on five Studios. Tonight we took the prefill window from 262K to 524K. Not finished, and every number gets posted either way. Why this is a paradigm shift for us: our agent is persistent and has 54MB of memory files..and then we drop a transcript or a codebase on top of it mid-conversation. The wait was the product’s real cost. It isn’t anymore. All credit to everyone who contributed to these concepts before us. We distill knowledge from all the greats and give credit to all. Standing on the shoulders of GitHub wizards unapologetically without fear of failure or judgement. Local ai must win! https://t.co/X94wAZsND8 #localai #heterogeneousinference #dgxspark #applesilicon
S
Shraddha Bharuka @BharukaShraddha ·
🚨 A Netflix engineer just open-sourced the fix for the most expensive problem in AI: wasted tokens It's called Headroom, and it might be the smartest fix to high token usage Your agent reads a 10,000-token log file to find one error. You paid for all 10,000 tokens. The answer needed 1,200. Headroom sits between your agent and the LLM and compresses everything before the model sees it. JSON, code, logs, RAG chunks, each gets its own specialized compressor. And it's reversible: the originals stay on your machine, so nothing is lost. The results speak for themselves: → Up to 95% fewer tokens → Same accuracy on benchmarks → Zero changes to your code Setup takes one minute: 1. pip install "headroom-ai[all]" 2. headroom wrap claude Done. Works with Claude Code, Cursor, Codex, and anything OpenAI-compatible. Everything runs locally, fully open source. The cheapest token is the one you never send. 🔗 Github repo: https://t.co/6TQM4o18hx So, are you compressing your context, or just paying the bill?
小墨同学 @xiaomovps ·
看懂Pi设计的魅力,可能只需要一分钟。 今天我突然看懂了为什么Pi,要自己设计Session、处理压缩算法、构建自己的上下文体系,都是为了不妥协! 上下文:尽量保持前缀稳定,让Prompt Cache持续命中,少花Token,也少被Harness随意改写。 Session:完整记录掌握在自己手里,不依赖某一家模型厂商保存状态,换模型还能继续跑。 压缩:自己决定什么留下、什么丢掉,压缩后的内容依然可见、可修改、可迁移,而不是变成Provider才能读懂的黑盒。 模型:GPT、Claude、Gemini,甚至本地模型,都只是可以随时替换的一层。 Harness:Pi也不希望你最后只是从厂商锁定,换成另一种Harness锁定。 这些设计看起来都很克制,甚至有点固执,但最后其实只指向一件事: 不妥协。 模型可以换,Provider可以换,Harness也可以换。 但Session、Context和Memory,应该一直属于你自己。 这才是一个真正自由的Agent。
X xiaomovps @xiaomovps

万字长文 | Pi Agent 零基础实操:从打开终端到完成第一个真实任务

C
cxuan @criscxuan ·
众所周知,chatgpt 网页版的 token 和 codex 的 usage 相互独立,且网页版的token量远远高于 codex 用量,但是网页版无法操作本地文件,导致只能做一个聊天助手。 但是网页版支持配置插件,连上我本地服务暴露出来的一个mcp 服务,这个服务支持read,write,bash 等本地文件操作基础命令,那么即可以实现chatgpt 操作本地文件类似codex一样的效果 且网页版的上下文以及agent 聪明程度远高于codex ,且不用担心gpt6 跑几个任务就没用量了 ,实现了token 自由
火山哥🕊️ @huoshan007 ·
兄弟们,用GPT-6 Astra,一定要把这个开关打开。 找到 ~/.codex/config.toml,加上: [features.context_management] experimental_mode = true 保存,再新开一个任务。 以前对话一长,前面的细节容易被压成一坨摘要。 打开以后,Astra会自己记笔记,还能回头搜索同一任务里的历史消息和工具结果。 这才是它真正狠的地方。 不是一轮回答更聪明,是项目做了几天,它还记得你为什么这么干。 长项目不开这个,真有点拿跑车送外卖。
陈成 @chenchengpro ·
关于「让 AI 写的 PR 更好 review」,我的 Tips 。 - 用 @dexhorthy 的 /show-me 生成更好读的 diff - 附 mermaid 图讲架构或流程 - 附复现步骤 - 附测试日志,证明 TDD 真跑过 - 附截图或视频,证明自己验证过 - 附 design doc,包含每个决策点 - 附测试步骤,方便 reviewer 自行验证 - 重要改动自行跑一遍各 code agent 的 /review,并在 PR 里说明
M mattpocockuk @mattpocockuk

What techniques do you use for making AI-authored PR's easier to review? - I.e. use /show-me by @dexhorthy for easy-to-read diffs - Describe the changes in pseudocode - Mermaid diagrams - Evidence of TDD The wildest version of this I've heard is @dctanner's agent, who uses Playwright to record a video of the frontend feature working with text-to-speech over the top. So the agent literally talks you through its change.

T
Tencent AI @TencentAI_News ·
We used TeamAI-CLI internally at Tencent since March. Open sourced it. It turns team knowledge into one git repo, so every agent works from the same handbook. what it does: > git-based: skills, rules and docs live in one repo, changes go through a merge request > hook-triggered: merged changes land on everyone's next session > each learning earns confidence from real usage, strong ones surface first, weak ones sink > works with claude code, codex, cursor, opencode, codebuddy and workbuddy One person's hard-won workaround can now become the whole team's default. https://t.co/ezmFhefrV5
S
SuSu_酥酥👅 @NFT_Chen ·
🚨只改一个文件,能让GPT-6 Astra Token直接少烧35%+! GPT-6 Astra不是贵,是你的AGENTS.md太肥了 省Token只做一件事:把仓库根目录那份 AGENTS.md 换成精简版(如图) 修改后实测数据很狠: 🔹普通改代码省 5%–15% 🔹跨文件长任务省 10%–25% 🔹爱反复搜索、重复验证的任务能到 30%–35%+ GPT-6 Astra 协作规则真正砍Token的不是文字变短,是把Agent的坏习惯掐死: 🔸先给结论,不复读需求 🔸已确认的信息不重读、不重搜 🔸证据够了就停,找到原因就修 🔸已授权操作不反复确认 🔸验证力度跟这次风险对齐,不为“看起来严谨”加测试 🔸交付物出来、必要验证过、限制说清,立刻收工 🔸子Agent只在独立且收益大于协调成本时才拆 GPT-6 Astra对 AGENTS.md 更敏感。文件越全,它越容易被旧规则带着空转。 根文件只留稳定规则,细节按需加载,账单才会掉。 收藏对照改。改完拿你最费Token的那个长任务对比一次,很多时候省下的不是35%,是整段无效探索。 #GPT6 #Astra #AGENTS_md #省Token #AI编程 #VibeCoding #Codex #howto用好AI #AI反常识howto
N NFT_Chen @NFT_Chen

🔥推荐:image2 + GPT-6 Astra 做 PPT是目前测过最快也最好看的一条路! 核心不是“让 AI 直接出 PPT”,而是先出整页视觉稿,再精准拆成可编辑文件。结合文稿+配图时,传统 AI PPT 最容易丑、乱裁图;这条工作流刚好打在痛点上。 关键操作: 1️⃣先用 ChatGPT 把文稿聊成清晰的 PPT 文字结构和每页重点 2️⃣把文字 + 需要插入的配图交给 Image2,按页生成整页 PPT 图,不满意就重出,直到视觉统一、高级 3️⃣用 GPT-6 轻度版把每张图转成 PPT:提示词写清“按图层拆分、配图尽量原样保留,文字/流程图/框架全部可编辑” 4️⃣得到一套既好看又逻辑清楚、组件可复用的 PPT。GPT-6 拆层很准,基本不用手改 注意:转 PPT 比较吃 token,但效果比 Luna、Terra 稳很多。适合要“既要审美、又要能改、还要快”的场景。 #AI做PPT #GPT6 #Image2 #Codex #效率工具 #职场干货 #PPT技巧

D
Dominic Elm @elmd_ ·
Introducing pr-stats
A
Aaron Burnett @aaronburnett ·
The SpaceX Louisiana Purchase watchers is a deep cutting corner of X you should keep an eye on.
T thelacoast @thelacoast

I've updated and cleaned up my Starbase LA permit map to better visualize the regulatory filing activity since the Spacex annoucement. 3 total permits filed so far. The 20 square points on the map represent proposed soil borings to depths of 100'-230'. This permit is approved and work is ongoing. (Originally there were 25 borings permitted, but the permit was later amended to just 20. There was also a second permit filed for additional borings, but it was cancelled the next day). The 19 small white dots on the map represent proposed test pits included in the 3rd permit application. This one was filed last week and is pending approval. It's different from the first 2 permits as it involves bucket excavation and sampling to a depth of just 10 feet. No actual construction permits have been applied for yet. This is all for planning and design. In the map, you can clearly see a potential construction pattern and I've color coded those accordingly. Although this map is currently updated, I've seen these plot locations change before and they may change again. It does at least give you another sense of scale for this infrastructure. It also shows how they are having to work around the private land. Final note - I've seen plenty of X posts talking about the dredge barges and support equipment currently in Freshwater Bayou. I've mentioned this before, but it has nothing to do with this project. The bayou south of the locks is constantly silting in and the U.S. Army Corps of Engineers conducts periodic dredging to maintain the 16 ft required depths. They do this every few years and now they are doing it again. Dredged material is pumped into the gulf on the west side of the channel (always west side due to the counter clockwise gulf loop current so it doesn't fall back in). It's not going on Starbase. I'll probably do another post explaining this since it is getting so much attention.

Y
Y Combinator @ycombinator ·
Harnesses often get dismissed as just scaffolding, just prompt engineering, and not real research. But that couldn't be farther from the truth. The same model weights that score 30% on ARC-AGI score 95% with a better harness. So we gathered a group of researchers and founders working at the frontier to do a deep dive into the state of harnesses. We cover how we got to this point, the case for making your harness as expressive as possible, and what YC learned building an agent for every employee in the company. 00:00 - @FrancoisChauba1: Why harnesses matter 04:27 - Building an auto-researcher by accident 07:13 - A five minute history of harnesses 13:56 - Self-improving harnesses 18:35 - @sethkarten: Prime Agent, a self-improving RLM harness 21:50 - Context as an L1, L2, L3 cache 24:51 - From Turing machine to von Neumann computer 28:33 - Messaging between agents 30:04 - ARC-AGI results 33:09 - Emulator Bench and GPU kernels 37:30 - @JonSaadFalcon: OpenJarvis, personal AI on personal devices 38:26 - How far behind are local models 39:21 - The five primitives of a personal AI stack 42:47 - Letting cloud models optimize your local stack 43:53 - 800x cheaper than the cloud 45:58 - @josh__france and @jbellregan: QM, YC's agent harness for work 47:29 - A history of YC's internal agents 49:24 - OpenClaw and a fleet of 50 agents 51:04 - Pulling the brain out of the sandbox 54:43 - Letting the agent choose its own sandbox and model 57:16 - The grind tool: budgets on goals 58:50 - Agents don't understand social context
P
Paul Couvert @itsPaulAi ·
How is this even possible?! This new open source model is only 2B parameters and at the same time: > better than models 6x bigger > can run locally and offline on a phone > optimized for agents/coding/tool use Hard to realize how the intelligence density has improved when you think about it.
O OpenBMB @OpenBMB

🚀 Meet MiniCPM5-2B, a 2B-parameter language model bringing high intelligence density to the edge, now open source! It ranks #1 among open-source models under 4B parameters on the @ArtificialAnlys Intelligence Index, with a score of 23. It also scores 20 on the Agentic Index, bringing an early form of general-purpose agent capability to the edge. Across 34 benchmarks, MiniCPM5-2B achieves an average score of 53.9, covering coding, math, long-context understanding, tool use, and agentic tasks. And this release goes beyond the model itself. We’re opening up the data, training recipes, and RL stack behind MiniCPM5-2B. 🤗 Hugging Face: https://t.co/FZOMTZhBjq 💻 GitHub: https://t.co/2L0I8bYv8f Modelscope: https://t.co/WRlPNEAzgu Web: https://t.co/gRSu65FeZL

D
Derya Unutmaz, MD @DeryaTR_ ·
This is a major milestone in the age of AI and toward our ultimate goal of completely reversing aging! @InSilicoMeds developed the first AI drug, Rentosertib, now in a Phase 3 clinical trial, and it just showed something remarkable: a reversal of biological age in people! Six different aging clocks, developed by six independent groups, all showed reversal after just 12 weeks of treatment, with participants measuring 3–4 years younger biologically! Congratulations to my friend Alex and the entire @InSilicoMeds team on this landmark achievement!
B biogerontology @biogerontology

My dear friends, I am happy to report the publication of the most important paper in my life to date (we have several great papers coming out but this is very special). Tomorrow, I will present this paper for the first time at the Nature AI Healthcare in Paris and will post a longer post on this story and its broader implications for how to conduct clinical trials. Please read it and comment on it. Many thanks to the great co-authors of the study and everyone who contributed. Many thanks to the many reviewers (friendly and unfriendly) for spending so much time and helping make it better. Link in the comments.

J
Joe Devon @joedevon ·
I perfected my AGENTS.md system until it was perfect. Then Fable 5.1 and Astra came out and now it's a mess. Everything that worked before broke. Don't get mad. Fix it. Here's the prompt, a slightly diff. version for Fable and Astra that may fix it: Read OpenAI's guide to prompting you https://t.co/lfynabrp21 then read Anthropic's guide to prompting Fable 5.1: https://t.co/YnJCAzU563 and tell me what's unique in each, and where do they actually conflict? I have a a system with shared global instructions and the ability to give Claude and Codex unique instructions. How would you split them out in light of the differences?
M
Mo Elgaraihy @EngMoElgaraihy ·
وداعاً لقواعد البيانات المتجهية (Vector DBs) وتكاليف الـ Embeddings عند إعطاء الـ AI Agent سياق المشروعات! ​أطلقت Red Hat أداة ripwire لتزويد وكلاء البرمجة بسياق أي المشروع بسرعة فائقة وبدون أي اعتمادات خارجية: ​⚙️ أداة مكتوبة بـ C++23 معالجة بـ Tree-sitter لحجم 21 لغة برمجية. 🎯 تبني خريطة هيكلية للمشروع وترتب الأكواد حسب الأهمية، تعقد الكود، التغييرات التاريخية (Git Churn)، وتغطية الاختبارات. 💡 يسأل الـ Agent عن الميزة (مثلاً: "Cache Invalidation") فيصله الكود والدوال المرتبطة والاختبارات مباشرة بنفس الـ Token Budget دون الحاجة للبحث العشوائي وفتح الملفات مكرراً! 🧵👇
J
Jamon @jamonholmgren ·
Maybe our end state is we all become CTOs at non-tech companies.
S staysaasy @staysaasy

It's never been a better time to own product/engineering at a non technical company. Like On shoes or Lululemon or American Eagle or something. I literally suspect that AI has changed the topology of non-tech companies more than it's changed the topology of highly technical businesses. At a lot of retail and media companies there's a very dominant Chief Digital Officer, head of e-commerce, CRO, whatever who owns the ultimate PnL for the business. They'll own a wide swath of marketing, e-commerce, site experience, customer support, CRM etc. but it hasn't historically been consistent that they own engineering (often reports to IT). There was historically a constant internal war to get these engineers to do more, competently. Unlike at a tech company, if you're selling women's shoes nobody cares about the software engineers. As a result these eng teams were significantly underfunded and often had much lower quality talent, specifically even if the floor was fine the ceiling was heavily limited - very few MIT and Waterloo grads on the tech team. Companies that bucked this trend (Netflix comes to mind) often dominate their markets with technology. But any engineer is hard to hire, even one who went to Tijuana Tech, so they've had to hire a lot of remote talent. That gets acceptable talent in the door but trades off intensity. This all was enough of a specialized headache that again eng often doesn't report to the PnL owner. But the shame of it is that they really should be the same unit. A better site, better data for targeting, a super slick retail support experience or whatever all seriously move the needle. So the functions were separate for convenience but it wasn't optimal. I think that the ability to pay a nominal fee for very reliably Very-good-not-necessarily-great engineering is going to make a very big difference for these companies and it'll be a big win for the ones who move engineering into their PnL chains ASAP. Will probably lead to higher purchases and Average Order Value and I suspect will reduce a lot of frictional costs from people constantly needing to yell at middling motivation engineers who don't report to them. Prob a win for consumers as well. It's also gonna help with simply coming up with ideas on what to do. You don't become CDO of Vuori because of your insane tech innovation skills but a lot of the best conventional ideas will also get suggested and prioritized by AI.

S
Stephen Cole @sthenc ·
Neuralink cofounder 👀
M maxhodak_ @maxhodak_

we have conjured an alien from a stargate

J
Jake @JustJake ·
Your laptop is holding you back Run infinite agents backed by infinite compute, to fan off infinite features/bugfixes Directly on top of snapshots of your production infrastructure on Railway
R Railway @Railway

Moving your Coding Agents to the Cloud (ft. Codex Desktop & GPT-6 Astra) https://t.co/vzXiW8XGiE 00:00 The limitations of running agents locally 01:13 Parallel development and Git worktrees 02:03 Moving your coding agent to a remote machine 02:25 Introducing Railway Cloud Agents 02:52 Installing the CLI and signing in 03:03 Configuring your project and default agent 03:42 Bringing your agent skills 04:24 Connecting the Codex desktop app 04:48 How SSH configuration works 05:10 Adding the SSH connection in Codex 05:39 Creating a remote project and starting a chat 06:09 Long-running tasks and remote execution 06:26 ChatGPT mobile access 07:03 Using Railway from your coding agent 07:15 Orchestrating multiple cloud agents

P
Peter Steinberger 🦞 @steipete ·
Did a PR to one of our upstream projects and they requested some minor changes. What’s even the point with this workflow? You already wrote the prompt, why make me ping my agent again so your agent then merges?
J
jdx @jdxcode ·
automatic dotfiles in `mise bootstrap` is released! to answer the most common question: it's not the same as chezmoi/yadm/stow/etc—read my post to understand why https://t.co/06ugPURech
J jdxcode @jdxcode

next mise release is going to have my dream dotfile management setup I've wanted for years. you just tell it to track a file and it'll automatically sync up/down to a git repo. Before, I had kludged together a personal setup with launchagent/rcm but this mise implementation is way easier to use. mise bootstrap dotfiles origin set jdx/dotfiles mise bootstrap dotfiles track ~/.zshrc basically it's like a per-file dropbox backed by git. there's an option to have `claude -p` or whatever come up with commit titles.

N
Nate Berkopec @nateberkopec ·
Another Dan Luu banger
D danluu @danluu

How well do agents use test/verification techniques? https://t.co/7E31xiS2H0 https://t.co/schArJqkax

K
KingWilliam @kingwilliam_ ·
SpaceXAI engineer, ex-Cursor: "I run my whole company on a 12-bot Grok team, $300 a month, zero employees they work a 168-hour week, I work maybe 6 and we still outship the 8-person team I used to pay for" in a 1-hour workshop, a SpaceXAI engineer builds a full Grok Bot team from scratch, skills and loops included worth more than a $500 course on agentic engineering watch today, then read how to run your own one-person company on Grok Bots in the article below
K kingwilliam_ @kingwilliam_

How to build a one-person $1M company with Grok Bot

M
Mat Velloso @matvelloso ·
Moats are vanishing. (impressive work, as usual, by Ammaar)
A ammaar @ammaar

I used GPT-6 Astra to get AAA PC games running on my iPad mini! Skyrim, Batman: Arkham City, Hades, and Age of Empires II. The actual Windows versions, running locally with touch controls. No streaming. Demo below and I'll share a repo and setup guides soon! https://t.co/zz8ze2R6Qn

G
Guillermo Rauch @rauchg ·
Your software factory needs high quality video recording. 𝚊𝚐𝚎𝚗𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛 delivers. We’re shipping more functionality derived from the lessons of automating the new bottleneck in software engineering: review, testing and QA.
C ctatedev @ctatedev

agent-browser can now record at 60fps Just add --fps 60 https://t.co/xgjXjqUE1t

D
Deepu @Deepusleepy ·
codex reset just landed, so if you don't want to burn through all your limits immediately, consider following these: 1. use Astra on low/medium - low performs around Sol high - medium is better than Sol at any effort 2. avoid fast mode. it burns through your limits significantly faster (2.5x faster). 3. don't touch ultra/max unless you absolutely need it. high/xhigh should be the ceiling for almost everything. 4. don't keep changing models or effort mid-thread, to avoid messing with caching. 5. minimise sub-agents. don't let Astra spawn a bunch of them unless the task truly benefits from parallel work. 6. use Luna as your default cheap sub-agent for reading, repo exploration, fan-out, mechanical edits, testing, simple fixes, etc. > use Sol medium/high for implementation work that actually needs more intelligence. 7. for separate pieces of work, ask it to create a new thread instead of spawning another sub-agent so you can continue that work later instead of throwing away the context. 8. don't let it overdo testing. for small changes, ask it to run only the relevant tests instead of repeatedly testing/investigating the entire repo. Astra is insanely capable but you can also burn a crazy amount of usage if you are not careful.
T thsottiaux @thsottiaux

Never gonna give you up Never gonna let you down Never gonna run around and desert you Never gonna make you cry Never gonna say goodbye Never gonna tell a lie and hurt you Thanks for reading. We will do a global reset of the usage for all paid subscriptions so that you can keep enjoying Astra after burning through all of it doing fun 3D modeling in blender. The work week is about to start. Lands around 6pm PST today.

S
Steve Hou @stevehou ·
Azeem produces some of the most unique and compelling macro estimates on the AI economy. By every account, AI is still accelerating!
A azeem @azeem

LATEST: Our revenue estimate for the AI economy reached $229 billion annualized by the end of August – up 3.5x in one year. https://t.co/lMV918P6id

O
Onur Solmaz @onusoz ·
ooof herdr pulled off some black magic here this means that using the sidebar, tab switcher now has almost local-responsiveness, and no lag, when connecting to a remote and the only parts that will lag due to connection will be the terminal sessions, inside the panes kind of how you would expect from a local GUI like cmux both your local and remote herdr need to be up to date, you can try this out if you are in a recent enough version, without closing your running sessions: herdr update --handoff
H herdrdev @herdrdev

0.9.0 is here, and it brings the most wanted herdr feature: all your machines running herdr, in a single client 🎉 control your agents and projects across local and remote machines without jumping between terminal tabs. https://t.co/afmHCbu7Pr

A
Adithya S K @adithya_s_k ·
if you want to create Coding RL environments based on paper-backed recipes, this is probably the best place to start recently came to know startups have literally raised their seed rounds around this repo and there’s some very cool stuff coming soon !!
K KumarShet192579 @KumarShet192579

Recently found this repo by @adithya_s_k I am telling you this freaking goldmine !! https://t.co/uEWe0yMues

M
Marcel Pociot 🧪 @marcelpociot ·
Polyscope is definitely the fastest option out there for giving your agents separate worktrees without cumbersome individual setup! Oh - and it's free https://t.co/CuvsjtFg2n
H HananBenold @HananBenold

In the past 3 months I've tried: @conductor_build , @orca_build , @aarondfrancis Solo, @t3dotcodes , @MulticaAI @marcelpociot's @getpolyscope is the only tool I find myself getting back to. COW is so much faster than git worktree. The optional Reviewer agent is spot on.