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
https://t.co/hsvsflUPmf
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.
70 Ideas to Reimagine Your Product Process With AI
so astra writes python to do everything which means we're going to have to rework this ui https://t.co/5cAttUtS6w
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!
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”?
Best Open-source AI Models for Cybersecurity that run fully offline on low hardware & The comparison
Just ask Astra to remove all the unnecessary text. Everywhere.
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.
@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.
I'm increasingly confused why people think "agent memory for enterprise/teams" is a real product category that makes any sense at all
@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.
万字长文 | Pi Agent 零基础实操:从打开终端到完成第一个真实任务
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.
🔥推荐: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技巧
Introducing pr-stats
AI has moved the bottleneck in software teams. Coding is much faster now than it used to, but PRs still require human review. That's because at the en...
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.
🚀 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
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.
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.
we have conjured an alien from a stargate
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
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.
How well do agents use test/verification techniques? https://t.co/7E31xiS2H0 https://t.co/schArJqkax
How to build a one-person $1M company with Grok Bot
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
agent-browser can now record at 60fps Just add --fps 60 https://t.co/xgjXjqUE1t
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.
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
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
Recently found this repo by @adithya_s_k I am telling you this freaking goldmine !! https://t.co/uEWe0yMues
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.