Hours of research in one daily brief–on your terms.

🔥 TOP SIGNAL

The strongest signal today: the harness is now a first-order performance variable. Georgi Gerganov says most local coding-agent failures come from the harness, chat-template, prompt-construction, and inference chain—not just the model @ggerganov, Matt Maher’s 100-feature PRD benchmark found Cursor improved frontier-model results by 11% on average, with Opus scoring 20% higher there than in Claude Code @edwinarbus +1, and the open-source Meta Harness paper summary says changing the harness around a fixed model can create a 6x gap Matthew Berman.

For builders, benchmarking the base model alone is increasingly the wrong abstraction; routing, review, retrieval, debugging visibility, and context handling are where a lot of the practical edge is moving @romainhuet +2.

🛠️ TOOLS & MODELS

• Codex plugin for Claude Code. OpenAI shipped openai/codex-plugin-cc so Claude Code users can delegate tasks to Codex or have Codex review changes with a ChatGPT subscription @dkundel. Huet says the pattern they already saw in the wild was Codex for review and GPT-5.4 for more complex tasks@romainhuet. Commands: /codex:review, /codex:adversarial-review, /codex:rescue@reach_vb +1.
• Open Codex substrate. Huet says Codex CLI and Codex app server are open source so the same ChatGPT subscription can be used in the app, terminal, JetBrains, Xcode, OpenCode, Pi, and Claude Code @romainhuet. The new Claude Code plugin is built on that same open-source app server + harness, including the same models, parallel tasking, and review flow @romainhuet.
• Codex got a context upgrade. Mark Chen says Codex now has auto compaction, and an early user report says it remembers tiny details across multiple rounds of compaction @markchen90 +1.
• Harness comparison that matters. In Matt Maher’s benchmark of frontier models implementing a 100-feature PRD, Cursor improved results from Gemini 52→57, GPT-5.4 82→88, and Opus 77→93; Theo highlighted Opus being 20% higher there than in Claude Code @edwinarbus +1.
• Local-model family to test now: Qwen3.5. Georgi Gerganov calls it a step change across device sizes @ggerganov. His tested local coding/chat/MCP set included gpt-oss-120b, Qwen3-Coder-30B, GLM-4.7-Flash, MiniMax-M2.5, and Qwen3.5-35B-A3B, mostly in Q8_0 variants @ggerganov. He says tool-calling quality still depends on both model intelligence and chat-template parsing in llama.cpp @ggerganov.
• Claude Code widened enterprise support. GitHub Enterprise Server now works across Claude Code on the web, iOS, Android, and Code Review, so self-hosted repos no longer need to move to github.com for async workflows @_catwu +1. Docs: code.claude.com/docs/en/github-enterprise-server@katchu11.
• Claude Code added computer use, but early cost reports are rough. Anthropic says Claude can open apps, click through UI, and test what it built from the CLI in research preview on Pro/Max plans @claudeai. Theo’s firsthand reaction: it used up his rate limits in 2 minutes despite a $200/month plan @theo.
• LangSmith Experiments got a more useful failure view. LangChain rebuilt the detail view to cut clutter and show better traces, clearer evaluator reasoning, and easier comparisons when debugging agent failures @LangChain. Try it at smith.langchain.com@LangChain.

💡 WORKFLOWS & TRICKS

• Cross-model review loop from Claude Code
  1. Install with /plugin marketplace add openai/codex-plugin-cc or from the repo @reach_vb +1.
  2. Use /codex:review for a standard read-only pass, /codex:adversarial-review when you want a challenge pass, or /codex:rescue to hand a task off @reach_vb +1.
  3. Keep Claude Code as your front-end if you like, but route review to Codex and heavier tasks to GPT-5.4—the pattern Huet says users were already doing manually @romainhuet.
• Local-model bring-up: don’t benchmark a broken stack
  1. Start with the highest-quality model that fits your hardware @ggerganov.
  2. Use your own harness—or llama-server’s webui with MCP—so you know what the stack is actually doing @ggerganov.
  3. Only then optimize with quantization or community parameter tuning @ggerganov.
  4. If results still look bad, inspect the whole chain: harness, chat template, prompt construction, and inference bugs @ggerganov.
• Claude Code can build real artifacts end-to-end. Simon Willison’s flow: clone nanochat, pull model weights, use the Space demo source to fill in the inference script, then have Claude Code read the LLM plugin tutorial and finish the plugin simonwillison. The output repo is public, and Simon says it was his first full model-plugin build this way and it worked really well simonwillison.
• Keep secrets out of context; let the agent do the plumbing. Kent C. Dodds says Claude Desktop cancelled a scheduled Cursor cloud agent, asked for a Cloudflare API token securely so it never entered context, generated an EC P-256 keypair, deployed a Worker, and updated Cloudflare routing to finish a Tesla integration @kentcdodds. Reusable pattern: human-mediated auth, agent-executed infra steps, MCP as the handoff surface @kentcdodds.
• If Claude Code usage suddenly spikes, test the CLI path. Theo, relaying a reverse-engineered report he says he did not independently confirm, points to a standalone Bun-binary cache bug with a workaround of npx @anthropic-ai/claude-code, plus a separate --resume issue that may still break cache @altryne. He says uncached tokens can be 10x-20x more expensive @altryne.
• Push human effort into plan mode. Jason Zhou says his strongest engineers now spend their time giving context and making technical decisions while the agent executes across multiple sessions Experts in the Loop.

👤 PEOPLE TO WATCH

• Georgi Gerganov — probably the clearest current explainer of why local coding agents disappoint: harness, chat templates, prompt construction, inference bugs, and a practical bring-up order @ggerganov. Simon Willison says this matches his own experiments @simonw.
• Romain Huet — high signal because he’s shipping actual workflow glue, not just demos: the open-source Codex plugin for Claude Code, concrete commands, and the open-source Codex app server/CLI underneath @romainhuet +2.
• Simon Willison — published a full transcript of Claude Code building a real model plugin end-to-end; good benchmark for what a successful serious use case looks like simonwillison.
• Kent C. Dodds — worth following for real MCP + infra orchestration patterns, especially his clear secret-handling boundary where tokens stay out of model context @kentcdodds.
• Jason Zhou — useful on where coding agents meet product/design: he trained non-technical designers on Cursor + GitHub, and now ships a /superdesign skill that scans the codebase before designing in context Experts in the Loop.

🎬 WATCH & LISTEN

• 14:15-16:39 — Meta Harness’s self-improvement loop. Fastest clean explanation of the pattern: store source, scores, and traces on disk; let a coding-agent proposer inspect prior failures; iterate the harness instead of stuffing everything into one prompt Matthew Berman.

• 37:25-38:28 — Jason Zhou’s /superdesign flow. Nice crossover example: the agent first scans the codebase and component system, then opens the browser and designs with actual product context instead of guessing from scratch Experts in the Loop.

📊 PROJECTS & REPOS

• openai/codex-plugin-cc — open-source bridge letting Claude Code call Codex for task delegation or code review via ChatGPT subscription @dkundel. Signal that it solves a real behavior: Embiricos says enough developers were already using Codex to review Claude outputs that OpenAI decided to lean into it @embirico.
• Meta Harness — new open-source project from Stanford, MIT, and Krafton for end-to-end optimization of model harnesses; paper and code are already out Matthew Berman. The core design is a coding-agent proposer with filesystem access that iterates on prior harnesses instead of relying on a fixed scaffold Matthew Berman.
• simonw/llm-mrchatterbox — a useful reference repo for the Claude Code-built-plugin pattern; Simon says it was his first full model-plugin build this way and he expects to use the method again simonwillison.
• Karpathy’s autoresearch — Matthew Berman cites it as a close cousin to Meta Harness, with 61k stars and a self-improving loop that runs experiments and learns from prior results Matthew Berman.

Editorial take: the fastest-moving edge in coding agents is no longer just model choice; it’s the harness around the model — memory, routing, review, and debugging visibility @ggerganov +2.

Most compelling recommendation: Extreme Ownership

Marc Andreessen's endorsement of Extreme Ownership is the clearest signal in today's set because he explains exactly what he took from the book and how he uses it. He says the idea of assuming fault first helps him focus on self-improvement, relieve stress, drain resentment, and lean on intrinsic rather than extrinsic motivation; he also says he fell in love with the book when it came out and wanted to share it with founders 20VC with Harry Stebbings

• Content type: Book
• Author/creator: Jocko Willink 20VC with Harry Stebbings
• Link/URL: Not provided in the source material
• Who recommended it: Marc Andreessen 20VC with Harry Stebbings
• Key takeaway: Treat "extreme ownership" as an operating rule: if something goes wrong, start by assuming it is your fault, then improve what you can control 20VC with Harry Stebbings
• Why it matters: This stands out because the recommendation comes with a concrete framework, not just praise. Andreessen ties it to a repeatable psychology he says is useful precisely when external rewards are not enough 20VC with Harry Stebbings

Other clearly organic picks

A pattern in today's set: the highest-signal recommendations came with explicit operating rules, while the lighter picks still help readers track what prominent tech leaders found worth sharing.

Draghi Report

• Content type: Report
• Author/creator: Mario Draghi 20VC with Harry Stebbings
• Link/URL: Not provided in the source material
• Who recommended it: Marc Andreessen 20VC with Harry Stebbings
• Key takeaway: Andreessen says readers should "just read that report" because "everything's in there," and frames it as a set of prescriptions for building stronger tech ecosystems in Europe 20VC with Harry Stebbings
• Why it matters: He presents it as an execution playbook rather than a diagnosis alone; the gap, in his telling, is implementation 20VC with Harry Stebbings

Apple II Forever!

• Content type: Article
• Author/creator: The Verge @verge +1
• Link/URL:https://www.theverge.com/tech/900677/apple-ii-personal-computer@verge
• Who recommended it: Tony Fadell @tfadell
• Key takeaway: Fadell says the Apple II was his first computer; he saved up by caddying while his grandfather matched his earnings, then read MacWorld and other computer magazines while dreaming of joining the Macintosh team @tfadell
• Why it matters: The recommendation is anchored in a formative personal story about how early computing shaped a future hardware builder's ambitions @tfadell

the state of AI safety in four fake graphs

• Content type: Blog post
• Author/creator: Boaz Barak @boazbaraktcs
• Link/URL: Announcement post — https://x.com/boazbaraktcs/status/2038606572046172443@sama
• Who recommended it: Sam Altman @sama
• Key takeaway: Altman called it "a very good post" @sama
• Why it matters: The source material does not include a fuller summary of the post's thesis, but the endorsement itself is a strong signal for readers tracking what prominent tech leaders are flagging in AI safety discussions @sama +1

Top Stories

Why it matters: This cycle's biggest signals were about agent execution: models are getting better at acting on software, multimodal systems are widening the interface, and performance is increasingly coming from the harness around the model as much as the model itself.

Claude Code moved closer to a full software-testing loop

Anthropic added Computer use to Claude Code, letting Claude open apps, click through interfaces, and test what it built directly from the CLI; the feature is in research preview on Pro and Max plans @claudeai. At the same time, Claude Code and Code Review added GitHub Enterprise Server support for async workflows on self-hosted repos @_catwu +1. Anthropic staff also said they open sourced a plugin so Claude Code users can call Codex from a ChatGPT subscription for reviews, adversarial reviews, and rescue flows @romainhuet +1.

Impact: this is a step from code generation toward a tighter write-build-run-verify loop, and it makes Claude Code easier to use inside enterprise GitHub setups @Yuchenj_UW.

Qwen3.5-Omni pushed multimodal interaction further into the product layer

Alibaba released Qwen3.5-Omni, a model for text, image, audio, and video understanding with real-time interaction features including semantic interruption, built-in web search, and complex function calling @Alibaba_Qwen. Alibaba highlighted script-level captioning, support for up to 10 hours of audio or 400 seconds of 720p video, 113 speech-recognition languages, and 36 output languages, plus an "Audio-Visual Vibe Coding" workflow that turns camera-described ideas into a website or game @Alibaba_Qwen. The company also said the model is open access via Hugging Face, with the caveat that "omni" here refers to interpreting image and voice, not generating them @kimmonismus.

Impact: Alibaba is packaging multimodal reasoning, voice interaction, and tool use into a surface that looks closer to a general-purpose AI application platform.

Harness engineering is turning into a primary performance lever

Several results this cycle pointed in the same direction: the system around the model matters more than many teams assumed. Meta-Harness said prompt/tool/retry/context choices alone can create a 6x performance gap on the same model, and that harness deltas are now wider than frontier-model deltas @LiorOnAI. In Matt Maher's 100-feature PRD benchmark, a post said Cursor improved model performance by 11% on average, including Opus from 77% to 93%@edwinarbus +1. CMU's CAID paper reported +26.7 points on PaperBench and +14.3 points on Commit0 over single-agent baselines by coordinating isolated git worktrees and explicit integration via git @omarsar0.

Impact: performance gains are increasingly coming from coordination, evaluation loops, and tool design, not only from bigger base models.

Enterprise deployments are producing measurable ROI

Two deployment examples stood out for hard numbers. Novo Nordisk is using AI agents built on Anthropic and OpenAI models to detect trial risks, automate site selection, and flag process redundancies, shaving weeks to months off clinical trials and potentially accelerating time-to-market by hundreds of millions of dollars@kimmonismus. Separately, a Shopify case study said the company cut annual AI deployment costs from $5.5M to $73K by decomposing business logic, modeling intent with DSPy, and optimizing a smaller model while maintaining performance; the cited scale-up estimate cut 150,000-shop coverage from $41M to $73K@kmad +1.

Impact: the strongest enterprise signal in the notes was not hype but faster trials, lower operating cost, and maintained performance.

Local AI stacks got faster and more usable

Ollama said it now runs fastest on Apple silicon through MLX, Apple's machine-learning framework @ollama +1. Its preview release also added NVFP4 support, cache reuse across conversations, intelligent checkpoints, and smarter eviction, with a Mac-oriented acceleration path for Qwen3.5-35B-A3B on systems with more than 32GB of unified memory @ollama +2. In parallel, llama.cpp reached 100k GitHub stars, and its creator said local agentic workflows are now practical because tool calling and local models have improved enough to support tasks like search, email, summarization, and home automation @ggerganov.

Impact: the local AI stack is getting closer to real everyday agent use on consumer hardware, especially on Macs.

Research & Innovation

Why it matters: Research this cycle focused less on raw scale and more on leverage: better long-context handling, stronger multimodal designs, cheaper training, and harder benchmarks.

• Massive-context agents without giant context windows: one paper places very large text corpora into directory structures and lets off-the-shelf coding agents navigate them with shell commands and Python instead of stuffing everything into the context window. The reported results were 88.5% on BrowseComp-Plus versus 80% best published, 33.7% on Oolong-Real versus 24.1%, and operation up to 3 trillion tokens@dair_ai. Paper: https://arxiv.org/abs/2603.20432@dair_ai.

• LongCat-Next: a new multimodal model was presented as "lexicalizing modalities as discrete tokens," with claims that it matches or beats SOTA across multimodal benchmarks, delivers SOTA audio on both recognition and TTS accuracy, and adds vision/audio without hurting core language performance @arankomatsuzaki. Resources: paper@arankomatsuzaki, GitHub@arankomatsuzaki, Hugging Face@arankomatsuzaki.

• daVinci-LLM: this pretraining paper was summarized as matching larger-model performance with half the size, adding 23 points on MATH, and arguing that data quality can matter more than dataset scale @arankomatsuzaki. Resources: paper@arankomatsuzaki, repo@arankomatsuzaki.

• Reasoning and optimization:ParaGator trains candidate generation and aggregation end-to-end for parallel reasoning, using pass@k for generation and pass@1 for aggregation, with the stated goal of avoiding mode collapse and improving math/scientific reasoning @jaseweston. On the systems side, Gram Newton-Schulz was introduced as a drop-in replacement for Newton-Schulz in Muon, with up to 2x faster performance while preserving validation perplexity within 0.01@jcz42.

• Benchmarks remain hard:PRBench introduced 30 expert-curated paper-reproduction tasks across 11 physics subfields, and the cited result was stark: all agents showed zero end-to-end callback success@arankomatsuzaki. Tau Bench added a banking domain with 698 documents across 21 product categories; best models were cited at 25% task success and under 10% on pass@4 @_philschmid.

Products & Launches

Why it matters: Product work moved toward usable systems: better voice models, more local tooling, and clearer paths from research models to daily workflows.

• Voice products improved at both ends of the stack. OpenAI said gpt-realtime-1.5 improves instruction following, tool calling, and multilingual accuracy in the Realtime API, while a new OpenAI developer post summarized Perplexity's lessons from running voice agents in production around context, audio pipelines, and turn-taking @OpenAIDevs +1. Separately, Cohere Transcribe launched as a 2B-parameter open-weights speech-to-text model with 4.7% AA-WER, roughly 60x real-time transcription, training from scratch on 14 languages, and availability both through Cohere's API and on Hugging Face under Apache 2.0 @ArtificialAnlys +1.

• Local agent tooling kept expanding.ARC (Agent Remote Control) introduced a browser-based remote monitor for local agents, with real-time tool-call visibility, approvals, messaging, native Hermes Agent integration, open source distribution, and end-to-end encryption @winglian. AutoClaw launched as a way to run OpenClaw locally with no API key, support for any model or GLM-5-Turbo, and fully local data handling @Zai_org. litesearch packaged a fully local document-ingestion and retrieval stack for agents like Claude Code, using LiteParse, local embeddings, local Qdrant storage, and CLI-native search @llama_index +1.

• Security-conscious agent wrappers are becoming their own category.PokeeClaw positioned itself as an enterprise-secure alternative to OpenClaw, with a secure sandbox architecture, isolated environments, approval workflows, role-based access control, audit trails, and lower token usage @Pokee_AI +1.

• Composable agent skills are spreading.Base44 added 130+ built-in "Superagent Skills" across marketing, operations, data analysis, design, content, coding, and research, with custom skills created from natural-language descriptions and reusable across workflows @kimmonismus +2.

Industry Moves

Why it matters: Corporate signals this cycle were about who owns the agent operating layer, who controls deployment, and where new capital is going.

• SycamoreLabs launched as a "trusted agent OS for the enterprise" with a $65M seed led by Coatue and Lightspeed, alongside AbstractVC, Dell Technologies Capital, 8VC, Fellows Fund, e14 Fund, and angel investors @SriViswan.

• Figure AI described its breakup with OpenAI in unusually direct terms. CEO Brett Adcock said Figure got "no value" from the relationship beyond early fundraising, said Figure's internal team outperformed OpenAI's daily, and said the real break came when OpenAI planned to restart robotics, which would have turned Figure's work into competitor training @mikekalilmfg. Figure has since built its own vision-language-action model, Helix, and the cited post said the company is valued at $39B@mikekalilmfg.

• Anthropic's growth is creating infrastructure strain. A cited report described the company's success as sparking a server crunch@steph_palazzolo.

• Hugging Face is explicitly pushing a builder strategy. Clement Delangue said the goal is to help "millions" build AI themselves rather than remain API users, and pointed to hf-autoresearch as an example of agent collaboration around checkpoints, datasets, papers, and Hub workflows @ClementDelangue +1.

• Internal agent deployments are becoming business functions. A post about LangChain said its internal GTM agent drove 250% more lead conversions, using Deep Agents for orchestration, multiple data sources for context, and Slack for approvals @jai__toor. A separate build log said a similar agent was rebuilt on DeeplineCLI + Deep Agents in under an hour with roughly 200 lines of config @jai__toor.

Policy & Regulation

Why it matters: The notes were light on formal government action, but governance questions around data consent, auditing, and safety evaluation were prominent.

• GitHub Copilot training consent: a widely shared warning said GitHub had opted users into training its models on their code by default, including paying customers, and pointed users to Settings > Privacy to disable it @GergelyOrosz.

• Governance proposals are getting more concrete: Will MacAskill and Fin Moorhouse proposed eight projects aimed at improving the transition to superintelligence, including independent evaluation of AI character traits, benchmarking strategic and philosophical reasoning, auditing models for sabotage and backdoors, and building monitoring and verification tools for collective coordination @willmacaskill.

• Safety debate stayed active: Boaz Barak published a new post titled the state of AI safety in four fake graphs, which Sam Altman publicly endorsed as "a very good post" @boazbaraktcs +1.

Quick Takes

Why it matters: These smaller items help fill in the operating picture around models, agent frameworks, and supporting infrastructure.

• Qwen 3.6 Plus Preview went live on OpenRouter for a limited free period; Alibaba asked for feedback and noted prompts/completions may be collected during the preview @OpenRouter +1.
• Codex auto compaction was reported to improve long-session coherence, with one user saying Codex remembers tiny details across multiple rounds of compaction @markchen90 +1.
• Hermes Agent added Multi Agent Profiles, giving independent bots separate memory, gateway connections, skills, and chat histories @Teknium +1.
• A new BOOT.md hook in Hermes lets agents save state before restarts and resume with what one post described as zero context loss @louislaurent.
• OpenAI's Codex App Server is fully open source, includes sign in with ChatGPT, and powers Codex integrations in products like the Codex app and external tools such as JetBrains and T3 Code @dkundel.
• PixVerse V6 launched on fal.ai with text-to-video, image-to-video, transition, and extend endpoints, while PixVerse separately promoted V6 as offering more control, better performance, and 15-second 1080p audiovisual generation @fal +2.
• LisanBench launched a live benchmark site with leaderboard visualizations, and its creator said a meta leaderboard is next @scaling01 +1.
• Triton-Ascend is now public, giving Huawei Ascend hardware a Triton kernel programming model that commenters said could help frameworks like sglang and vLLM run on Ascend without learning AscendC @_rozzai +1.
• Gemini Live is now powered by Gemini 3.1 Flash Live@GeminiApp.

A few shifts stood out today

Microsoft is turning model plurality into a product, open releases are getting stronger across audio and speech, and local AI keeps looking more deployable. The market feels a bit less centered on one flagship model and more on orchestration, efficiency, and where systems actually run.

Microsoft brings multi-model workflows into Copilot

Microsoft introduced Critique in M365 Copilot, a multi-model deep research system that uses multiple models together to generate responses and reports; Satya Nadella said Microsoft's benchmarks show "best-in-class deep research." It also launched Council, which lets users run multiple models on the same prompt at once to compare alignment, divergence, and unique contributions. Both are available now in Frontier@satyanadella +4.

Why it matters: This is a notable product signal from a major platform vendor: instead of hiding model plurality behind one answer, Microsoft is exposing model collaboration and disagreement as a feature.

Open models broaden beyond text

Mistral’s Voxtral TTS is a notable open-audio release

Mistral launched Voxtral TTS, an open-weight multilingual text-to-speech model that supports nine languages and targets real-time streaming for voice agents Latent.Space +1. Latent Space said the model posted a 68.4% win rate against ElevenLabs Flash v2.5, while Mistral speakers described it as state-of-the-art quality at a fraction of proprietary costs Latent.Space +1.

Its architecture mixes autoregressive semantic speech tokens with flow matching for acoustic tokens, backed by an in-house neural audio codec at 12.5 Hz; the team also said the setup can extend to long generations via larger context windows Latent.Space +1.

Why it matters: Open voice models are getting closer to the quality, latency, and cost targets that matter for real-time products.

The broader open-model pipeline was unusually diverse

Interconnects highlighted an unusually broad set of open releases: NVIDIA's Nemotron-3-Super-120B-A12B-NVFP4 with a 1M context window, multilingual support, NVFP4 pre-training, and open pre-/post-training datasets; Cohere's cohere-transcribe-03-2026 speech model with 14 languages under Apache 2.0; Sarvam's 105B and 30B models with strong Indic-language positioning; and Mistral-Small-4-119B-2603 as a hybrid reasoning model with coding abilities Interconnects. Interconnects argued this kind of domain-specific, cheaper model development is becoming an important complement to the strongest closed agents Interconnects.

Why it matters: The open ecosystem is spreading across speech, multilingual, regional, and reasoning workloads instead of clustering around one general chatbot race.

Local AI looks more like infrastructure

llama.cpp reached 100k stars, and the stack around it keeps firming up

llama.cpp crossed 100k GitHub stars, has 1,500+ contributors, and Hugging Face said it is bringing Georgi Gerganov and ggml into the team behind what it called the most widely used open-source runtime for local AI @ggerganov +1. Gerganov said useful local agentic workflows became feasible as models improved tool calling on everyday devices, and Clement Delangue argued that many disappointments with smaller local models are really failures of scaffolding, chat templates, prompt construction, or fine-tuning rather than raw model capability @ggerganov +3.

Gerganov also described Qwen3.5 as a "step change" across device sizes, while Delangue urged open-source agent tools to rely primarily on open models rather than closed APIs that send data to the cloud @ggerganov +1.

Why it matters: This is starting to look less like enthusiast momentum and more like a real deployment path for private, on-device, and cross-platform AI.

Strategy watch

Ben Thompson sees OpenAI's enterprise focus as a competitive necessity

Ben Thompson argued that reports of OpenAI cutting side projects should not be overread as an exit from consumer; instead, he sees a rational shift of resources toward enterprise, where customers pay for productivity gains and Codex has been especially strong Sharp Tech Podcast. He framed the urgency around Anthropic's enterprise growth—described as moving from a $14B to $19B run rate—and the risk that OpenAI gets shut out if large customers standardize elsewhere Sharp Tech Podcast.

He also noted OpenAI has pushed back on startup-skewed Ramp chart interpretations and may be stronger in the Fortune 500 than those charts suggest, while arguing that ChatGPT's massive consumer scale creates a harder monetization path because ads are difficult and compute is already heavily committed Sharp Tech Podcast.

Why it matters: The center of gravity in AI competition may be shifting from consumer reach to enterprise distribution, pricing, and workflow lock-in.

Research watch

Self-improving agent scaffolds advanced, but frontier math remained hard

Import AI highlighted Hyperagents, a self-referential scaffold that lets LLM systems iteratively modify their own prompts and tools. In reported results, the setup improved Polyglot coding performance from 14% to 34%, paper review from 0% to 71%, and robotics reward design from 6% to 37%Import AI.

The same roundup pointed to HorizonMath, a benchmark of 100 predominantly unsolved math problems with automated verification, where the top model scored only 7% overall and 50% on the easiest subset Import AI.

Why it matters: The capability story remains mixed: better scaffolds are producing real gains on structured tasks, while benchmarks aimed at genuine mathematical discovery are still extremely hard.

Big Ideas

1) Claude Code is moving from assistant to PM operating system

Aakash Gupta’s core argument: the best Claude Code users are not relying on one-off chats. They build persistent file-based operating systems with skills, sub-agents, hooks, workflows, and markdown knowledge that improve every future prompt Product Growth. He positions this as the operating-system layer for people spending 8-10 hours a day in the tool, with the potential to move from roughly 80/100 to 95/100 proficiency Product Growth.

Why it matters: PM work is highly contextual. A persistent workspace lets stakeholder context, project history, goals, and prior fixes survive beyond one chat window Product Growth.

How to apply:

• Start with CLAUDE.md and GOALS.md; the source says those two files deliver 80% of the value on day one Product Growth.
• Keep CLAUDE.md current weekly so Claude inherits your role, tools, priorities, and recurring instructions in every message Product Growth.
• Add persistent people files and project folders so meeting notes, stakeholder preferences, PRDs, research, and launch results compound over time Product Growth.
• Use sub-agents for research and CLIs instead of MCPs to protect context: one example dropped a research task from about 10% of the main context window to 0.5% Product Growth.

2) The product trio is compressing into product builders

Teresa Torres argues product management, design, and engineering are not dead, but the classic PM-design-engineering trio is collapsing toward a broader product-builder foundation with specialties layered on top All Things Product with Teresa …. In her framing, AI now gives people a base level of programming, design, product management, and business-context capability, so 1-2 product builders can handle much of the routine 80% of feature work while specialists focus on the harder 20% All Things Product with Teresa ….

Why it matters: This changes team design and individual expectations. Torres expects smaller, more cross-functional teams, while still arguing that human strengths in alignment, trade-off decisions, organizational context, and innovation remain important All Things Product with Teresa ….

How to apply:

• Build horizontal AI skills alongside your core craft; Torres describes this as a modern T-shaped product-builder foundation All Things Product with Teresa ….
• Learn to specify what you want and plan with an agent; she says that base foundation no longer requires direct exposure to code for many common web-app tasks All Things Product with Teresa ….
• Keep investing in your specialty. Her argument is not that expertise disappears, but that expertise is increasingly paired with AI fluency inside the function itself All Things Product with Teresa ….
• If you lead teams, start thinking about safety infrastructure now, including security, accessibility, and code-review agents, because broader participation in building raises review demands All Things Product with Teresa ….

3) Pricing architecture is becoming core PM territory

The Product Compass makes a blunt case: as AI compresses time spent on Jira, PRDs, and standups, PMs are increasingly responsible for business outcomes, and pricing sits near the center of that shift The Product Compass. Its thesis is simple:

The article contrasts companies that can change pricing in hours with teams that still need quarters. It cites Vercel shipping 5-6 pricing changes per month, while many companies make 1-2 changes per year and consume a quarter of engineering time for each The Product Compass.

Why it matters: If plans, entitlements, usage limits, and experiments are hardcoded, pricing becomes an engineering bottleneck rather than a product lever The Product Compass.

How to apply: Use the four-pillar test for monetization agility The Product Compass:

• Unified product catalog: one schema for plans, features, entitlements, and prices The Product Compass.
• Decoupled entitlements: central runtime rules instead of scattered if (plan == ...) checks The Product Compass.
• Real-time metering: usage visibility for customers, sales, and finance before the invoice surprise The Product Compass.
• Control plane: a dashboard where non-engineers can run pricing experiments and adjust limits without code deploys The Product Compass.

Tactical Playbook

1) Stand up a lightweight PM operating system in Claude Code

1. Create CLAUDE.md with your role, work style, installed tools, current priorities, and references to your skills Product Growth.
2. Add GOALS.md for quarterly priorities; the source recommends starting here before building more structure Product Growth.
3. Set up knowledge/people/ and update it after meetings so stakeholder preferences and recent context are reusable in future communication Product Growth.
4. Create one folder per active project, then archive completed projects for reuse on similar work later Product Growth.
5. Monitor /status line and /context, and push research to sub-agents instead of the main session when context starts climbing Product Growth.
6. Use Jupyter notebooks for CSV analysis when you need transparent, reviewable methodology, and use the ask-user-questions tool when requirements or decision criteria are still fuzzy Product Growth.

Why this matters: The operating model turns scattered PM work into reusable context and lowers the cost of repeating research, analysis, meeting prep, and writing from scratch Product Growth.

2) Close the gap between acceptance criteria and actual testing

A Reddit post surfaced a familiar failure mode: a PM wrote the checkout flow step by step in the PRD, but QA backlog, outdated scripts after a UI change, and mutual assumptions meant the flow still shipped broken r/ProductManagement. The PM’s takeaway was that knowing the flow well was not enough because the knowledge never became an executable test r/ProductManagement.

How to apply:

1. Identify flows where a broken handoff would create visible customer damage, such as checkout or onboarding r/ProductManagement.
2. Convert plain-English acceptance criteria into something that runs against the actual product, not just a documentation artifact r/ProductManagement.
3. Review screenshots or pass/fail evidence before sprint review, rather than assuming regression coverage exists r/ProductManagement.
4. If QA ownership is fragmented, treat PM participation in testing as a temporary control, not an exception r/ProductManagement.
5. Do not rely on documentation alone to solve the problem; one community response argued the handoff gap still comes back to direct communication r/ProductManagement.

3) Put pricing on a monthly operating cadence

The Product Compass suggests a two-hour monthly pricing meeting with four blocks: customer data, learnings scan, product-to-pricing roadmap sync, and decisions/actions The Product Compass.

How to apply:

1. Review usage, billing, and approaching-limit customers to spot expansion candidates and churn risk The Product Compass.
2. Add cross-functional input from sales, CS, finance, marketing, and growth on win/loss patterns and pricing friction The Product Compass.
3. For every feature shipping in the next 30-90 days, decide its monetization stance up front; the rule proposed is that no feature ships without one The Product Compass.
4. Leave with 1-3 local experiments, each with an owner, hypothesis, timeline, and expected impact The Product Compass.

Why this matters: It separates infrequent global pricing changes from continuous local experiments, giving PMs a repeatable way to connect product roadmap and revenue decisions The Product Compass.

4) When engineering relationships are political, build trust before trying to redirect the roadmap

Community advice in a discussion about resistant developers was consistent on one point: trust comes before leverage. The recommended pattern was to listen first, find the influential developer, make small suggestions once you are situated, and avoid upending a team’s plan immediately as a newcomer r/ProductManagement +1.

How to apply:

1. Treat developers as partners, not order takers; commenters framed weak PM-engineering trust as the root problem in these scenarios r/ProductManagement +1.
2. Build credibility by representing the existing roadmap before advocating major changes r/ProductManagement.
3. If your manager reassigns you or inserts themselves into the work, ask directly what pattern they are seeing and what feedback you need to hear r/ProductManagement +1.

Case Studies & Lessons

1) Monetization architecture changed shipping speed at Zep, Plotly, and Automox

• Zep: modeled plans and entitlements, went from trial start to production in 4 days, and later used limit enforcement to improve free-to-paid conversion while giving sales earlier visibility into usage The Product Compass.
• Plotly: launched two AI products two quarters faster because catalog and entitlements were already modeled centrally The Product Compass.
• Automox: after years of hardcoded monetization logic across two billing systems, it cut time-to-launch for new pricing tiers by 75% and freed two full-time engineers from maintenance work The Product Compass.

Lesson: Pricing agility is not only a packaging problem. It is an architectural capability that determines how quickly PMs can test monetization ideas The Product Compass.

2) A broken checkout flow showed that a PRD is not a test plan

One PM’s postmortem described a flow that was written clearly in a Notion PRD, demoed repeatedly, and still shipped with a production bug because no one converted that knowledge into an updated test r/ProductManagement. After adopting a plain-English testing tool that ran on real devices and returned screenshots plus step-level pass/fail, the PM says they caught two production-bound issues in the first week r/ProductManagement.

Lesson: The verification loop breaks when documentation, QA scripts, and ownership drift apart. The fix is executable validation, not better prose alone r/ProductManagement +1.

3) Horizontal expansion can damage the core product

Teresa Torres says Zapier’s expansion into adjacent products has coincided with degradation in the core automation experience, citing repeated failures where zaps did not trigger @ttorres. Her workaround has been to ask Claude to build custom webhook listeners because she finds the resulting code more reliable and easier to control for error handling @ttorres. She adds that she is slowly moving off both Zapier and Airtable because of persistent quality issues @ttorres.

Lesson: New surface area can hide declining reliability in the core workflow. PMs expanding horizontally need to watch quality metrics on the original product, not just adoption of the new bets @ttorres.

Career Corner

1) The safest career move right now is becoming a stronger product builder

Torres’ career advice is direct: build horizontal AI skills while continuing to deepen your functional expertise All Things Product with Teresa …. She argues that if you do not learn how to use AI inside your function, you will no longer be seen as an expert in that function, and she notes that job descriptions and interview processes are already changing All Things Product with Teresa ….

How to apply: Practice two skills now: specifying what you want clearly and planning work with agents, then pair that with deeper expertise in your primary craft All Things Product with Teresa ….

2) Early-career PMs should optimize for signal, not resume mythology

Advice to an APM with informal startup experience was straightforward: include the work on the resume, but focus on what you did, the problems you solved, and your responsibilities, not on ownership structure or proprietorship details r/ProductManagement. The same commenter suggested staying in the APM role for at least 1-2 years to build clearer, more relevant product experience before making the next move r/ProductManagement.

3) Domain switches are harder in an oversupplied market

A PM with about four years in data and analytics product management said they were reaching final rounds for customer-facing roles but losing out to candidates with more direct domain experience, despite feedback that their core PM skills were transferable r/ProductManagement. They also pointed to candidate oversupply as part of the problem r/ProductManagement.

Takeaway: In the current market, transferable PM skill is still valuable, but it may not beat direct domain familiarity when employers have many candidates to choose from r/ProductManagement.

Tools & Resources

1) PM OS starter repos

• Carl’s Product OS: a lighter starting point for a Claude Code workspace Product Growth.
• Aakash’s PM Claude Code setup: a larger setup with 41 skills and 7 sub-agents Product Growth.

Why explore them: Both are meant to reduce setup friction and give PMs a concrete file structure, skills layout, and workflow starting point Product Growth.

2) Jupyter notebooks for auditable analysis

The recommendation here is to ask Claude to analyze data in a Jupyter notebook so every query, output, and chart is preserved as code cells and rendered results Product Growth.

Use it when: you need analysis that a manager or data scientist can verify step by step, rather than a black-box summary Product Growth.

3) The ask-user-questions tool

Claude can generate a terminal UI with checkboxes and input fields to gather requirements, fill context gaps, or support decisions instead of guessing Product Growth.

Use it when: assumptions are the main failure mode in discovery or planning Product Growth.

4) A prompt-optimization loop for recurring agent workflows

Aakash Gupta describes a Karpathy-style loop for prompts: pick the prompt to improve, use 2-3 realistic test inputs and 3-6 binary quality checks, run repeated evaluations, mutate one variable at a time, keep winners with version control, and revert losers Aakash Gupta. He cites a pace of about 12 experiments per hour and roughly 100 overnight Aakash Gupta.

Use it when: you have a prompt or system instruction that is already good enough, but not yet reliable, in workflows like support, internal automations, extraction, or code review Aakash Gupta.

5) Reforge AI Productivity

Sachin Rekhi says the updated live sessions are focused on what has become most actionable for PMs over the last six months: automating PM workflows with Claude Code, the AI prototyping mastery ladder, AI-powered customer discovery, and AI-enhanced product strategy and execution @sachinrekhi.

Market Movers

• United States — row crops: Grain trade is rotating from crude-oil-driven momentum toward Tuesday's USDA acres and quarterly stocks reports. Pro Farmer's survey put corn at 96 million acres and soybeans at 84.25 million acres, while other pre-report references centered closer to 94.4-94.5 million corn acres. Multiple sources noted the survey window predated the latest war- and fertilizer-driven disruption, so the report may not fully capture the most recent acreage recalculation. Quarterly corn stocks are also expected to run more than 1 billion bushels above last year, while funds recently added about 50,000 corn contracts and remain heavily committed to the soybean complex Farm Journal +3.

• United States — exports: Weekly export inspections were 70.4 million bushels for corn, 21.5 million for soybeans, and 13.4 million for wheat. Marketing-year corn inspections are 298 million bushels ahead of the pace needed to hit USDA's target, wheat is 53 million bushels ahead, but soybeans remain 112 million bushels behind. GrainStats separately noted that corn exports do not depend on China the way soybeans do; last week's inspections to China were 9.9 million bushels of soybeans and zero corn and wheat @ArlanFF101 +5.

• United States — biofuels and soy complex: EPA finalized the highest RFS volumes in program history, keeping conventional biofuels at 15 billion gallons for 2026 and lifting biomass-based diesel to roughly 5.5-5.7 billion gallons. Reallocated small-refinery waivers add another 200-250 million gallons per year to 2026-2027 volumes. Analysts tied the policy to stronger bean-oil-led soybean trade and better long-run domestic use for soybeans Farm Journal +1.

• United States/Australia — wheat: Chicago wheat futures rose on concern that the Iran war could lift farmer energy and fertilizer costs, while Plains drought widened the Kansas City-Chicago spread to the largest hard red winter premium since August. Australia was also cited for drought and fuel shortages, even as one analyst noted global wheat stocks-to-use remains high overall @irfandonat +1.

• United States — livestock: Cattle futures broke to new highs after a technical breakout, firmer cash trade, and tighter beef supplies. Beef cold storage fell 5% year over year to about 413 million pounds. Hogs closed lower on end-month profit taking even though the March 1 inventory of 74.3 million head came in below pre-report expectations; pork bellies in cold storage were down about 6-7% from a year ago Farm Journal +2.

Innovation Spotlight

• Brazil — nematode biotech: BASF said its Soja NRS trait is aimed at cyst and Pratylenchus nematodes that cover about 90% of Brazilian territory. The company tied nematodes to roughly R$35 billion in annual production losses, including R$16-17 billion in soybeans alone, and said the trait could add R$15-18 billion to the value chain. Because the control is embedded in the soybean plant, BASF expects lower nematode populations to carry productivity benefits into second-crop corn or cotton. Commercial introduction in Brazil was described as a 2-3 year timeline after 10-12 years of development Canal Rural.

• Brazil — lower-emission fertilizers in potatoes: In Paraná, six growers covering about 130 hectares are using Iara's Climate Choice portfolio with 4C management and GHG-protocol tracking. The program estimates up to 40% lower carbon footprint, while participants reported higher productivity, more dry matter, and better tuber quality that earns factory bonuses. PepsiCo is financing the price difference versus conventional fertilizer as part of its 2030 emissions target Canal Rural.

• United States — machinery and fuel systems: John Deere's E98 ethanol-powered 8R pairs 350 hp with no DEF and a reported fuel-cost advantage of roughly $1/gallon ethanol versus $3/gallon diesel, even though volumetric fuel use is higher. Deere and RDO also described the new high-horsepower 8R/8RX package as an ultimate planting tractor that can power electric row units through a single cord, run up to 110 gpm hydraulics, and plant up to 1,200 acres/day with large 24-row-plus planters in some setups Farm4Profit Podcast +2.

Regional Developments

• United States — planting and weather: Southern corn planting is already moving, with progress reported at 76% in Louisiana, 53% in Texas, 50% in Mississippi, 23% in Arkansas, 2% in Kansas, and just above zero in Illinois. At the same time, substantial mid-week rainfall is expected across Iowa, Illinois, Missouri, Minnesota, Michigan, and Indiana near early planting dates, while hard red winter wheat areas farther west may miss needed rain @GrainStats +1.

• Brazil — soybean and corn supply: AG Rural raised Brazil's 2025/26 soybean forecast to 178.4 million tons, with harvest at 75%. Center-South first-crop corn harvest reached 59.4%, versus 56.4% a year ago, while safrinha planting is nearly 98% complete and already 100% done across Mato Grosso's projected 7.3 million hectares. Total corn output was trimmed to 135.7 million tonsCanal Rural.

• Brazil — April weather: Forecasts point to a hotter, drier first half of April followed by stronger second-half rainfall. That pattern was described as supportive for later-planted safrinha corn in Mato Grosso, Goiás, and Minas Gerais because rain is not expected to cut off early, even though late-stage crops face some stress in the hotter opening weeks Canal Rural +1.

• Brazil — Mato Grosso logistics: Road conditions on MT-240 in Paranatinga are interrupting soybean movement. One farmer with 1,800 hectares of soybeans still had 800 hectares unharvested and said at least 500 hectares could be lost if truck delays continue. Another producer reported about 15% crop loss where trucks were crossing cropped ground used as a bypass Canal Rural.

• Brazil — pork exports: Brazil has consolidated as the third-largest global pork exporter. Asia absorbs about 70% of shipments, led by the Philippines, with Vietnam and Japan also important. Slaughter capacity was described as up roughly 3% to meet export demand, although domestic live-hog prices have weakened since February, making export flow more important for balance Canal Rural.

Best Practices

• Soybeans — variable populations by field: In soybean fields with iron deficiency chlorosis risk, light soils, late planting, or low fertility, Ag PhD recommended raising populations to 160,000-180,000 plants. The main payoff cited was faster canopy closure for better weed control. Lower populations were described as better suited to very high-fertility fields or areas with high white mold risk, and variable-rate population by field was encouraged to balance productivity and seed cost @AgPhDMedia.

• Soybeans — Southeast U.S. stand management: A separate Southeast system targeted an 80,000 final stand to drive branching and reduce lodging risk. After a pounding rain crusted 15-inch rows, pivot irrigation was used to soften the soil surface and help emergence rather than to add moisture Farm Journal.

• Weed control — start residual programs early: Brownfield's herbicide guidance emphasized keeping fields clean early in spring, when weed competition can lock in yield loss. Resicore Rev was cited with up to 8 weeks of residual control, three modes of action, and compatibility with UAN and ATS as well as other pre-emerge mixes Brownfield Ag News.

• Small grains — manage nitrogen and lodging together: Tissue sampling at jointing (GS5/6) was used to map variable-rate nitrogen needs, while the same operation targeted about 80 heads/sq ft for 80+ bushel grain and planned a growth regulator to reduce lodging risk Farm Journal.

• Soil systems — conserve structure, then manage pressure: Brazil's no-till system now covers nearly 90% of cultivated land, and a separate U.S. field example showed strip-till absorbing 2.5-3 inches of rain and reducing runoff. The trade-off in tropical systems is higher year-round pest, weed, and disease pressure because of the permanent green bridge Canal Rural +1.

• Dairy — benchmark economics first: Espírito Santo's new dairy sustainability framework starts with 103 indicators, including 78 economic measures focused on genetics, feeding, productivity, and milk quality. The rollout begins with 400 farms and shared technical assistance from public extension, Senar, and cooperatives Canal Rural.

Input Markets

• United States — fertilizer availability: Fertilizer remains the sharpest input risk. Producers reported booking anywhere from 50% to 85% of needs, but some still faced delivery problems even with contracts in hand. Forward contracting was emphasized, while crude oil also moved above $100 for the first time since 2022 Farm Journal +1.

• Brazil — policy and freight pressure: Brazilian producers face a 2% fertilizer cost increase from new PIS/COFINS rules starting April 1, while the minimum freight table removes cheaper return freight from ports and diesel hikes add more cost. Local commentary also said grain prices have not kept pace with fertilizer inflation, worsening the input-output trade ratio Canal Rural.

• Global — sulfur bottleneck: Brazilian industry said fertilizer production is being reduced worldwide because sulfur flows from the Arabian Gulf have been disrupted. China was cited as having temporarily banned fertilizer exports because of sulfur scarcity, and one major supplier was said to have only about two months of operating room without normalization of Gulf routes Canal Rural.

• Feed — support for pork, pressure for cattle: Brazil's pork export spread is still around 40% because export prices near $2,500 and low feed costs are supporting margins. In contrast, U.S. cattle commentary warned that drought will tighten forage supplies and raise feed costs Canal Rural +1.

• Crop chemicals — residual programs favored: Early-season chemical guidance continues to favor residual products that fit fertilizer passes. Resicore Rev was specifically highlighted for UAN/ATS tank-mix flexibility and longer residual control Brownfield Ag News.

Forward Outlook

• United States — USDA report risk: The next 24 hours are report-driven. USDA stocks and acres are being treated as a wild card; Market Minute said corn has traded higher on report day for five straight years, with an average move of 12 cents over the past 10 years. But multiple sources cautioned that survey timing predates the latest war/fertilizer shock, so acreage may keep moving after the report Market Minute LLC +2.

• United States — corn versus soybeans: Corn acreage may stay sticky where nitrogen was prepaid or fall-applied, but soybeans still have room to gain if spring fertilizer and fuel costs escalate. One analyst also argued that corn's recent price rally can offset some fertilizer inflation, which may limit late acreage switching Farm Journal +1.

• United States — biofuel demand is now more structural: Beyond the immediate bean-oil reaction, EPA said the RFS now creates $31 billion of value for American corn and soybean oil. Starting in 2028, foreign fuels and feedstocks receive only half the RFS compliance value of U.S.-made products, reinforcing the domestic demand story Farm Journal.

• United States/Brazil — seasonal timing: Southern U.S. planting is already active, Corn Belt rain is arriving close to early plant dates, and Brazilian second-crop corn is expected to rely on a dry first half of April followed by better second-half moisture for grain fill. Large crop potential remains intact in Brazil, but local road failures and input logistics are now important watchpoints alongside weather @GrainStats +3.

🔥 TOP SIGNAL

The strongest signal today: the harness is now a first-order performance variable. Georgi Gerganov says most local coding-agent failures come from the harness, chat-template, prompt-construction, and inference chain—not just the model @ggerganov, Matt Maher’s 100-feature PRD benchmark found Cursor improved frontier-model results by 11% on average, with Opus scoring 20% higher there than in Claude Code @edwinarbus +1, and the open-source Meta Harness paper summary says changing the harness around a fixed model can create a 6x gap Matthew Berman.

For builders, benchmarking the base model alone is increasingly the wrong abstraction; routing, review, retrieval, debugging visibility, and context handling are where a lot of the practical edge is moving @romainhuet +2.

🛠️ TOOLS & MODELS

• Codex plugin for Claude Code. OpenAI shipped openai/codex-plugin-cc so Claude Code users can delegate tasks to Codex or have Codex review changes with a ChatGPT subscription @dkundel. Huet says the pattern they already saw in the wild was Codex for review and GPT-5.4 for more complex tasks@romainhuet. Commands: /codex:review, /codex:adversarial-review, /codex:rescue@reach_vb +1.
• Open Codex substrate. Huet says Codex CLI and Codex app server are open source so the same ChatGPT subscription can be used in the app, terminal, JetBrains, Xcode, OpenCode, Pi, and Claude Code @romainhuet. The new Claude Code plugin is built on that same open-source app server + harness, including the same models, parallel tasking, and review flow @romainhuet.
• Codex got a context upgrade. Mark Chen says Codex now has auto compaction, and an early user report says it remembers tiny details across multiple rounds of compaction @markchen90 +1.
• Harness comparison that matters. In Matt Maher’s benchmark of frontier models implementing a 100-feature PRD, Cursor improved results from Gemini 52→57, GPT-5.4 82→88, and Opus 77→93; Theo highlighted Opus being 20% higher there than in Claude Code @edwinarbus +1.
• Local-model family to test now: Qwen3.5. Georgi Gerganov calls it a step change across device sizes @ggerganov. His tested local coding/chat/MCP set included gpt-oss-120b, Qwen3-Coder-30B, GLM-4.7-Flash, MiniMax-M2.5, and Qwen3.5-35B-A3B, mostly in Q8_0 variants @ggerganov. He says tool-calling quality still depends on both model intelligence and chat-template parsing in llama.cpp @ggerganov.
• Claude Code widened enterprise support. GitHub Enterprise Server now works across Claude Code on the web, iOS, Android, and Code Review, so self-hosted repos no longer need to move to github.com for async workflows @_catwu +1. Docs: code.claude.com/docs/en/github-enterprise-server@katchu11.
• Claude Code added computer use, but early cost reports are rough. Anthropic says Claude can open apps, click through UI, and test what it built from the CLI in research preview on Pro/Max plans @claudeai. Theo’s firsthand reaction: it used up his rate limits in 2 minutes despite a $200/month plan @theo.
• LangSmith Experiments got a more useful failure view. LangChain rebuilt the detail view to cut clutter and show better traces, clearer evaluator reasoning, and easier comparisons when debugging agent failures @LangChain. Try it at smith.langchain.com@LangChain.

💡 WORKFLOWS & TRICKS

• Cross-model review loop from Claude Code
  1. Install with /plugin marketplace add openai/codex-plugin-cc or from the repo @reach_vb +1.
  2. Use /codex:review for a standard read-only pass, /codex:adversarial-review when you want a challenge pass, or /codex:rescue to hand a task off @reach_vb +1.
  3. Keep Claude Code as your front-end if you like, but route review to Codex and heavier tasks to GPT-5.4—the pattern Huet says users were already doing manually @romainhuet.
• Local-model bring-up: don’t benchmark a broken stack
  1. Start with the highest-quality model that fits your hardware @ggerganov.
  2. Use your own harness—or llama-server’s webui with MCP—so you know what the stack is actually doing @ggerganov.
  3. Only then optimize with quantization or community parameter tuning @ggerganov.
  4. If results still look bad, inspect the whole chain: harness, chat template, prompt construction, and inference bugs @ggerganov.
• Claude Code can build real artifacts end-to-end. Simon Willison’s flow: clone nanochat, pull model weights, use the Space demo source to fill in the inference script, then have Claude Code read the LLM plugin tutorial and finish the plugin simonwillison. The output repo is public, and Simon says it was his first full model-plugin build this way and it worked really well simonwillison.
• Keep secrets out of context; let the agent do the plumbing. Kent C. Dodds says Claude Desktop cancelled a scheduled Cursor cloud agent, asked for a Cloudflare API token securely so it never entered context, generated an EC P-256 keypair, deployed a Worker, and updated Cloudflare routing to finish a Tesla integration @kentcdodds. Reusable pattern: human-mediated auth, agent-executed infra steps, MCP as the handoff surface @kentcdodds.
• If Claude Code usage suddenly spikes, test the CLI path. Theo, relaying a reverse-engineered report he says he did not independently confirm, points to a standalone Bun-binary cache bug with a workaround of npx @anthropic-ai/claude-code, plus a separate --resume issue that may still break cache @altryne. He says uncached tokens can be 10x-20x more expensive @altryne.
• Push human effort into plan mode. Jason Zhou says his strongest engineers now spend their time giving context and making technical decisions while the agent executes across multiple sessions Experts in the Loop.

👤 PEOPLE TO WATCH

• Georgi Gerganov — probably the clearest current explainer of why local coding agents disappoint: harness, chat templates, prompt construction, inference bugs, and a practical bring-up order @ggerganov. Simon Willison says this matches his own experiments @simonw.
• Romain Huet — high signal because he’s shipping actual workflow glue, not just demos: the open-source Codex plugin for Claude Code, concrete commands, and the open-source Codex app server/CLI underneath @romainhuet +2.
• Simon Willison — published a full transcript of Claude Code building a real model plugin end-to-end; good benchmark for what a successful serious use case looks like simonwillison.
• Kent C. Dodds — worth following for real MCP + infra orchestration patterns, especially his clear secret-handling boundary where tokens stay out of model context @kentcdodds.
• Jason Zhou — useful on where coding agents meet product/design: he trained non-technical designers on Cursor + GitHub, and now ships a /superdesign skill that scans the codebase before designing in context Experts in the Loop.

🎬 WATCH & LISTEN

• 14:15-16:39 — Meta Harness’s self-improvement loop. Fastest clean explanation of the pattern: store source, scores, and traces on disk; let a coding-agent proposer inspect prior failures; iterate the harness instead of stuffing everything into one prompt Matthew Berman.

• 37:25-38:28 — Jason Zhou’s /superdesign flow. Nice crossover example: the agent first scans the codebase and component system, then opens the browser and designs with actual product context instead of guessing from scratch Experts in the Loop.

📊 PROJECTS & REPOS

• openai/codex-plugin-cc — open-source bridge letting Claude Code call Codex for task delegation or code review via ChatGPT subscription @dkundel. Signal that it solves a real behavior: Embiricos says enough developers were already using Codex to review Claude outputs that OpenAI decided to lean into it @embirico.
• Meta Harness — new open-source project from Stanford, MIT, and Krafton for end-to-end optimization of model harnesses; paper and code are already out Matthew Berman. The core design is a coding-agent proposer with filesystem access that iterates on prior harnesses instead of relying on a fixed scaffold Matthew Berman.
• simonw/llm-mrchatterbox — a useful reference repo for the Claude Code-built-plugin pattern; Simon says it was his first full model-plugin build this way and he expects to use the method again simonwillison.
• Karpathy’s autoresearch — Matthew Berman cites it as a close cousin to Meta Harness, with 61k stars and a self-improving loop that runs experiments and learns from prior results Matthew Berman.

Editorial take: the fastest-moving edge in coding agents is no longer just model choice; it’s the harness around the model — memory, routing, review, and debugging visibility @ggerganov +2.

Most compelling recommendation: Extreme Ownership

Marc Andreessen's endorsement of Extreme Ownership is the clearest signal in today's set because he explains exactly what he took from the book and how he uses it. He says the idea of assuming fault first helps him focus on self-improvement, relieve stress, drain resentment, and lean on intrinsic rather than extrinsic motivation; he also says he fell in love with the book when it came out and wanted to share it with founders 20VC with Harry Stebbings

• Content type: Book
• Author/creator: Jocko Willink 20VC with Harry Stebbings
• Link/URL: Not provided in the source material
• Who recommended it: Marc Andreessen 20VC with Harry Stebbings
• Key takeaway: Treat "extreme ownership" as an operating rule: if something goes wrong, start by assuming it is your fault, then improve what you can control 20VC with Harry Stebbings
• Why it matters: This stands out because the recommendation comes with a concrete framework, not just praise. Andreessen ties it to a repeatable psychology he says is useful precisely when external rewards are not enough 20VC with Harry Stebbings

Other clearly organic picks

A pattern in today's set: the highest-signal recommendations came with explicit operating rules, while the lighter picks still help readers track what prominent tech leaders found worth sharing.

Draghi Report

• Content type: Report
• Author/creator: Mario Draghi 20VC with Harry Stebbings
• Link/URL: Not provided in the source material
• Who recommended it: Marc Andreessen 20VC with Harry Stebbings
• Key takeaway: Andreessen says readers should "just read that report" because "everything's in there," and frames it as a set of prescriptions for building stronger tech ecosystems in Europe 20VC with Harry Stebbings
• Why it matters: He presents it as an execution playbook rather than a diagnosis alone; the gap, in his telling, is implementation 20VC with Harry Stebbings

Apple II Forever!

• Content type: Article
• Author/creator: The Verge @verge +1
• Link/URL:https://www.theverge.com/tech/900677/apple-ii-personal-computer@verge
• Who recommended it: Tony Fadell @tfadell
• Key takeaway: Fadell says the Apple II was his first computer; he saved up by caddying while his grandfather matched his earnings, then read MacWorld and other computer magazines while dreaming of joining the Macintosh team @tfadell
• Why it matters: The recommendation is anchored in a formative personal story about how early computing shaped a future hardware builder's ambitions @tfadell

the state of AI safety in four fake graphs

• Content type: Blog post
• Author/creator: Boaz Barak @boazbaraktcs
• Link/URL: Announcement post — https://x.com/boazbaraktcs/status/2038606572046172443@sama
• Who recommended it: Sam Altman @sama
• Key takeaway: Altman called it "a very good post" @sama
• Why it matters: The source material does not include a fuller summary of the post's thesis, but the endorsement itself is a strong signal for readers tracking what prominent tech leaders are flagging in AI safety discussions @sama +1

Top Stories

Why it matters: This cycle's biggest signals were about agent execution: models are getting better at acting on software, multimodal systems are widening the interface, and performance is increasingly coming from the harness around the model as much as the model itself.

Claude Code moved closer to a full software-testing loop

Anthropic added Computer use to Claude Code, letting Claude open apps, click through interfaces, and test what it built directly from the CLI; the feature is in research preview on Pro and Max plans @claudeai. At the same time, Claude Code and Code Review added GitHub Enterprise Server support for async workflows on self-hosted repos @_catwu +1. Anthropic staff also said they open sourced a plugin so Claude Code users can call Codex from a ChatGPT subscription for reviews, adversarial reviews, and rescue flows @romainhuet +1.

Impact: this is a step from code generation toward a tighter write-build-run-verify loop, and it makes Claude Code easier to use inside enterprise GitHub setups @Yuchenj_UW.

Qwen3.5-Omni pushed multimodal interaction further into the product layer

Alibaba released Qwen3.5-Omni, a model for text, image, audio, and video understanding with real-time interaction features including semantic interruption, built-in web search, and complex function calling @Alibaba_Qwen. Alibaba highlighted script-level captioning, support for up to 10 hours of audio or 400 seconds of 720p video, 113 speech-recognition languages, and 36 output languages, plus an "Audio-Visual Vibe Coding" workflow that turns camera-described ideas into a website or game @Alibaba_Qwen. The company also said the model is open access via Hugging Face, with the caveat that "omni" here refers to interpreting image and voice, not generating them @kimmonismus.

Impact: Alibaba is packaging multimodal reasoning, voice interaction, and tool use into a surface that looks closer to a general-purpose AI application platform.

Harness engineering is turning into a primary performance lever

Several results this cycle pointed in the same direction: the system around the model matters more than many teams assumed. Meta-Harness said prompt/tool/retry/context choices alone can create a 6x performance gap on the same model, and that harness deltas are now wider than frontier-model deltas @LiorOnAI. In Matt Maher's 100-feature PRD benchmark, a post said Cursor improved model performance by 11% on average, including Opus from 77% to 93%@edwinarbus +1. CMU's CAID paper reported +26.7 points on PaperBench and +14.3 points on Commit0 over single-agent baselines by coordinating isolated git worktrees and explicit integration via git @omarsar0.

Impact: performance gains are increasingly coming from coordination, evaluation loops, and tool design, not only from bigger base models.

Enterprise deployments are producing measurable ROI

Two deployment examples stood out for hard numbers. Novo Nordisk is using AI agents built on Anthropic and OpenAI models to detect trial risks, automate site selection, and flag process redundancies, shaving weeks to months off clinical trials and potentially accelerating time-to-market by hundreds of millions of dollars@kimmonismus. Separately, a Shopify case study said the company cut annual AI deployment costs from $5.5M to $73K by decomposing business logic, modeling intent with DSPy, and optimizing a smaller model while maintaining performance; the cited scale-up estimate cut 150,000-shop coverage from $41M to $73K@kmad +1.

Impact: the strongest enterprise signal in the notes was not hype but faster trials, lower operating cost, and maintained performance.

Local AI stacks got faster and more usable

Ollama said it now runs fastest on Apple silicon through MLX, Apple's machine-learning framework @ollama +1. Its preview release also added NVFP4 support, cache reuse across conversations, intelligent checkpoints, and smarter eviction, with a Mac-oriented acceleration path for Qwen3.5-35B-A3B on systems with more than 32GB of unified memory @ollama +2. In parallel, llama.cpp reached 100k GitHub stars, and its creator said local agentic workflows are now practical because tool calling and local models have improved enough to support tasks like search, email, summarization, and home automation @ggerganov.

Impact: the local AI stack is getting closer to real everyday agent use on consumer hardware, especially on Macs.

Research & Innovation

Why it matters: Research this cycle focused less on raw scale and more on leverage: better long-context handling, stronger multimodal designs, cheaper training, and harder benchmarks.

• Massive-context agents without giant context windows: one paper places very large text corpora into directory structures and lets off-the-shelf coding agents navigate them with shell commands and Python instead of stuffing everything into the context window. The reported results were 88.5% on BrowseComp-Plus versus 80% best published, 33.7% on Oolong-Real versus 24.1%, and operation up to 3 trillion tokens@dair_ai. Paper: https://arxiv.org/abs/2603.20432@dair_ai.

• LongCat-Next: a new multimodal model was presented as "lexicalizing modalities as discrete tokens," with claims that it matches or beats SOTA across multimodal benchmarks, delivers SOTA audio on both recognition and TTS accuracy, and adds vision/audio without hurting core language performance @arankomatsuzaki. Resources: paper@arankomatsuzaki, GitHub@arankomatsuzaki, Hugging Face@arankomatsuzaki.

• daVinci-LLM: this pretraining paper was summarized as matching larger-model performance with half the size, adding 23 points on MATH, and arguing that data quality can matter more than dataset scale @arankomatsuzaki. Resources: paper@arankomatsuzaki, repo@arankomatsuzaki.

• Reasoning and optimization:ParaGator trains candidate generation and aggregation end-to-end for parallel reasoning, using pass@k for generation and pass@1 for aggregation, with the stated goal of avoiding mode collapse and improving math/scientific reasoning @jaseweston. On the systems side, Gram Newton-Schulz was introduced as a drop-in replacement for Newton-Schulz in Muon, with up to 2x faster performance while preserving validation perplexity within 0.01@jcz42.

• Benchmarks remain hard:PRBench introduced 30 expert-curated paper-reproduction tasks across 11 physics subfields, and the cited result was stark: all agents showed zero end-to-end callback success@arankomatsuzaki. Tau Bench added a banking domain with 698 documents across 21 product categories; best models were cited at 25% task success and under 10% on pass@4 @_philschmid.

Products & Launches

Why it matters: Product work moved toward usable systems: better voice models, more local tooling, and clearer paths from research models to daily workflows.

• Voice products improved at both ends of the stack. OpenAI said gpt-realtime-1.5 improves instruction following, tool calling, and multilingual accuracy in the Realtime API, while a new OpenAI developer post summarized Perplexity's lessons from running voice agents in production around context, audio pipelines, and turn-taking @OpenAIDevs +1. Separately, Cohere Transcribe launched as a 2B-parameter open-weights speech-to-text model with 4.7% AA-WER, roughly 60x real-time transcription, training from scratch on 14 languages, and availability both through Cohere's API and on Hugging Face under Apache 2.0 @ArtificialAnlys +1.

• Local agent tooling kept expanding.ARC (Agent Remote Control) introduced a browser-based remote monitor for local agents, with real-time tool-call visibility, approvals, messaging, native Hermes Agent integration, open source distribution, and end-to-end encryption @winglian. AutoClaw launched as a way to run OpenClaw locally with no API key, support for any model or GLM-5-Turbo, and fully local data handling @Zai_org. litesearch packaged a fully local document-ingestion and retrieval stack for agents like Claude Code, using LiteParse, local embeddings, local Qdrant storage, and CLI-native search @llama_index +1.

• Security-conscious agent wrappers are becoming their own category.PokeeClaw positioned itself as an enterprise-secure alternative to OpenClaw, with a secure sandbox architecture, isolated environments, approval workflows, role-based access control, audit trails, and lower token usage @Pokee_AI +1.

• Composable agent skills are spreading.Base44 added 130+ built-in "Superagent Skills" across marketing, operations, data analysis, design, content, coding, and research, with custom skills created from natural-language descriptions and reusable across workflows @kimmonismus +2.

Industry Moves

Why it matters: Corporate signals this cycle were about who owns the agent operating layer, who controls deployment, and where new capital is going.

• SycamoreLabs launched as a "trusted agent OS for the enterprise" with a $65M seed led by Coatue and Lightspeed, alongside AbstractVC, Dell Technologies Capital, 8VC, Fellows Fund, e14 Fund, and angel investors @SriViswan.

• Figure AI described its breakup with OpenAI in unusually direct terms. CEO Brett Adcock said Figure got "no value" from the relationship beyond early fundraising, said Figure's internal team outperformed OpenAI's daily, and said the real break came when OpenAI planned to restart robotics, which would have turned Figure's work into competitor training @mikekalilmfg. Figure has since built its own vision-language-action model, Helix, and the cited post said the company is valued at $39B@mikekalilmfg.

• Anthropic's growth is creating infrastructure strain. A cited report described the company's success as sparking a server crunch@steph_palazzolo.

• Hugging Face is explicitly pushing a builder strategy. Clement Delangue said the goal is to help "millions" build AI themselves rather than remain API users, and pointed to hf-autoresearch as an example of agent collaboration around checkpoints, datasets, papers, and Hub workflows @ClementDelangue +1.

• Internal agent deployments are becoming business functions. A post about LangChain said its internal GTM agent drove 250% more lead conversions, using Deep Agents for orchestration, multiple data sources for context, and Slack for approvals @jai__toor. A separate build log said a similar agent was rebuilt on DeeplineCLI + Deep Agents in under an hour with roughly 200 lines of config @jai__toor.

Policy & Regulation

Why it matters: The notes were light on formal government action, but governance questions around data consent, auditing, and safety evaluation were prominent.

• GitHub Copilot training consent: a widely shared warning said GitHub had opted users into training its models on their code by default, including paying customers, and pointed users to Settings > Privacy to disable it @GergelyOrosz.

• Governance proposals are getting more concrete: Will MacAskill and Fin Moorhouse proposed eight projects aimed at improving the transition to superintelligence, including independent evaluation of AI character traits, benchmarking strategic and philosophical reasoning, auditing models for sabotage and backdoors, and building monitoring and verification tools for collective coordination @willmacaskill.

• Safety debate stayed active: Boaz Barak published a new post titled the state of AI safety in four fake graphs, which Sam Altman publicly endorsed as "a very good post" @boazbaraktcs +1.

Quick Takes

Why it matters: These smaller items help fill in the operating picture around models, agent frameworks, and supporting infrastructure.

• Qwen 3.6 Plus Preview went live on OpenRouter for a limited free period; Alibaba asked for feedback and noted prompts/completions may be collected during the preview @OpenRouter +1.
• Codex auto compaction was reported to improve long-session coherence, with one user saying Codex remembers tiny details across multiple rounds of compaction @markchen90 +1.
• Hermes Agent added Multi Agent Profiles, giving independent bots separate memory, gateway connections, skills, and chat histories @Teknium +1.
• A new BOOT.md hook in Hermes lets agents save state before restarts and resume with what one post described as zero context loss @louislaurent.
• OpenAI's Codex App Server is fully open source, includes sign in with ChatGPT, and powers Codex integrations in products like the Codex app and external tools such as JetBrains and T3 Code @dkundel.
• PixVerse V6 launched on fal.ai with text-to-video, image-to-video, transition, and extend endpoints, while PixVerse separately promoted V6 as offering more control, better performance, and 15-second 1080p audiovisual generation @fal +2.
• LisanBench launched a live benchmark site with leaderboard visualizations, and its creator said a meta leaderboard is next @scaling01 +1.
• Triton-Ascend is now public, giving Huawei Ascend hardware a Triton kernel programming model that commenters said could help frameworks like sglang and vLLM run on Ascend without learning AscendC @_rozzai +1.
• Gemini Live is now powered by Gemini 3.1 Flash Live@GeminiApp.

A few shifts stood out today

Microsoft is turning model plurality into a product, open releases are getting stronger across audio and speech, and local AI keeps looking more deployable. The market feels a bit less centered on one flagship model and more on orchestration, efficiency, and where systems actually run.

Microsoft brings multi-model workflows into Copilot

Microsoft introduced Critique in M365 Copilot, a multi-model deep research system that uses multiple models together to generate responses and reports; Satya Nadella said Microsoft's benchmarks show "best-in-class deep research." It also launched Council, which lets users run multiple models on the same prompt at once to compare alignment, divergence, and unique contributions. Both are available now in Frontier@satyanadella +4.

Why it matters: This is a notable product signal from a major platform vendor: instead of hiding model plurality behind one answer, Microsoft is exposing model collaboration and disagreement as a feature.

Open models broaden beyond text

Mistral’s Voxtral TTS is a notable open-audio release

Mistral launched Voxtral TTS, an open-weight multilingual text-to-speech model that supports nine languages and targets real-time streaming for voice agents Latent.Space +1. Latent Space said the model posted a 68.4% win rate against ElevenLabs Flash v2.5, while Mistral speakers described it as state-of-the-art quality at a fraction of proprietary costs Latent.Space +1.

Its architecture mixes autoregressive semantic speech tokens with flow matching for acoustic tokens, backed by an in-house neural audio codec at 12.5 Hz; the team also said the setup can extend to long generations via larger context windows Latent.Space +1.

Why it matters: Open voice models are getting closer to the quality, latency, and cost targets that matter for real-time products.

The broader open-model pipeline was unusually diverse

Interconnects highlighted an unusually broad set of open releases: NVIDIA's Nemotron-3-Super-120B-A12B-NVFP4 with a 1M context window, multilingual support, NVFP4 pre-training, and open pre-/post-training datasets; Cohere's cohere-transcribe-03-2026 speech model with 14 languages under Apache 2.0; Sarvam's 105B and 30B models with strong Indic-language positioning; and Mistral-Small-4-119B-2603 as a hybrid reasoning model with coding abilities Interconnects. Interconnects argued this kind of domain-specific, cheaper model development is becoming an important complement to the strongest closed agents Interconnects.

Why it matters: The open ecosystem is spreading across speech, multilingual, regional, and reasoning workloads instead of clustering around one general chatbot race.

Local AI looks more like infrastructure

llama.cpp reached 100k stars, and the stack around it keeps firming up

llama.cpp crossed 100k GitHub stars, has 1,500+ contributors, and Hugging Face said it is bringing Georgi Gerganov and ggml into the team behind what it called the most widely used open-source runtime for local AI @ggerganov +1. Gerganov said useful local agentic workflows became feasible as models improved tool calling on everyday devices, and Clement Delangue argued that many disappointments with smaller local models are really failures of scaffolding, chat templates, prompt construction, or fine-tuning rather than raw model capability @ggerganov +3.

Gerganov also described Qwen3.5 as a "step change" across device sizes, while Delangue urged open-source agent tools to rely primarily on open models rather than closed APIs that send data to the cloud @ggerganov +1.

Why it matters: This is starting to look less like enthusiast momentum and more like a real deployment path for private, on-device, and cross-platform AI.

Strategy watch

Ben Thompson sees OpenAI's enterprise focus as a competitive necessity

Ben Thompson argued that reports of OpenAI cutting side projects should not be overread as an exit from consumer; instead, he sees a rational shift of resources toward enterprise, where customers pay for productivity gains and Codex has been especially strong Sharp Tech Podcast. He framed the urgency around Anthropic's enterprise growth—described as moving from a $14B to $19B run rate—and the risk that OpenAI gets shut out if large customers standardize elsewhere Sharp Tech Podcast.

He also noted OpenAI has pushed back on startup-skewed Ramp chart interpretations and may be stronger in the Fortune 500 than those charts suggest, while arguing that ChatGPT's massive consumer scale creates a harder monetization path because ads are difficult and compute is already heavily committed Sharp Tech Podcast.

Why it matters: The center of gravity in AI competition may be shifting from consumer reach to enterprise distribution, pricing, and workflow lock-in.

Research watch

Self-improving agent scaffolds advanced, but frontier math remained hard

Import AI highlighted Hyperagents, a self-referential scaffold that lets LLM systems iteratively modify their own prompts and tools. In reported results, the setup improved Polyglot coding performance from 14% to 34%, paper review from 0% to 71%, and robotics reward design from 6% to 37%Import AI.

The same roundup pointed to HorizonMath, a benchmark of 100 predominantly unsolved math problems with automated verification, where the top model scored only 7% overall and 50% on the easiest subset Import AI.

Why it matters: The capability story remains mixed: better scaffolds are producing real gains on structured tasks, while benchmarks aimed at genuine mathematical discovery are still extremely hard.

Big Ideas

1) Claude Code is moving from assistant to PM operating system

Aakash Gupta’s core argument: the best Claude Code users are not relying on one-off chats. They build persistent file-based operating systems with skills, sub-agents, hooks, workflows, and markdown knowledge that improve every future prompt Product Growth. He positions this as the operating-system layer for people spending 8-10 hours a day in the tool, with the potential to move from roughly 80/100 to 95/100 proficiency Product Growth.

Why it matters: PM work is highly contextual. A persistent workspace lets stakeholder context, project history, goals, and prior fixes survive beyond one chat window Product Growth.

How to apply:

• Start with CLAUDE.md and GOALS.md; the source says those two files deliver 80% of the value on day one Product Growth.
• Keep CLAUDE.md current weekly so Claude inherits your role, tools, priorities, and recurring instructions in every message Product Growth.
• Add persistent people files and project folders so meeting notes, stakeholder preferences, PRDs, research, and launch results compound over time Product Growth.
• Use sub-agents for research and CLIs instead of MCPs to protect context: one example dropped a research task from about 10% of the main context window to 0.5% Product Growth.

2) The product trio is compressing into product builders

Teresa Torres argues product management, design, and engineering are not dead, but the classic PM-design-engineering trio is collapsing toward a broader product-builder foundation with specialties layered on top All Things Product with Teresa …. In her framing, AI now gives people a base level of programming, design, product management, and business-context capability, so 1-2 product builders can handle much of the routine 80% of feature work while specialists focus on the harder 20% All Things Product with Teresa ….

Why it matters: This changes team design and individual expectations. Torres expects smaller, more cross-functional teams, while still arguing that human strengths in alignment, trade-off decisions, organizational context, and innovation remain important All Things Product with Teresa ….

How to apply:

• Build horizontal AI skills alongside your core craft; Torres describes this as a modern T-shaped product-builder foundation All Things Product with Teresa ….
• Learn to specify what you want and plan with an agent; she says that base foundation no longer requires direct exposure to code for many common web-app tasks All Things Product with Teresa ….
• Keep investing in your specialty. Her argument is not that expertise disappears, but that expertise is increasingly paired with AI fluency inside the function itself All Things Product with Teresa ….
• If you lead teams, start thinking about safety infrastructure now, including security, accessibility, and code-review agents, because broader participation in building raises review demands All Things Product with Teresa ….

3) Pricing architecture is becoming core PM territory

The Product Compass makes a blunt case: as AI compresses time spent on Jira, PRDs, and standups, PMs are increasingly responsible for business outcomes, and pricing sits near the center of that shift The Product Compass. Its thesis is simple:

The article contrasts companies that can change pricing in hours with teams that still need quarters. It cites Vercel shipping 5-6 pricing changes per month, while many companies make 1-2 changes per year and consume a quarter of engineering time for each The Product Compass.

Why it matters: If plans, entitlements, usage limits, and experiments are hardcoded, pricing becomes an engineering bottleneck rather than a product lever The Product Compass.

How to apply: Use the four-pillar test for monetization agility The Product Compass:

• Unified product catalog: one schema for plans, features, entitlements, and prices The Product Compass.
• Decoupled entitlements: central runtime rules instead of scattered if (plan == ...) checks The Product Compass.
• Real-time metering: usage visibility for customers, sales, and finance before the invoice surprise The Product Compass.
• Control plane: a dashboard where non-engineers can run pricing experiments and adjust limits without code deploys The Product Compass.

Tactical Playbook

1) Stand up a lightweight PM operating system in Claude Code

1. Create CLAUDE.md with your role, work style, installed tools, current priorities, and references to your skills Product Growth.
2. Add GOALS.md for quarterly priorities; the source recommends starting here before building more structure Product Growth.
3. Set up knowledge/people/ and update it after meetings so stakeholder preferences and recent context are reusable in future communication Product Growth.
4. Create one folder per active project, then archive completed projects for reuse on similar work later Product Growth.
5. Monitor /status line and /context, and push research to sub-agents instead of the main session when context starts climbing Product Growth.
6. Use Jupyter notebooks for CSV analysis when you need transparent, reviewable methodology, and use the ask-user-questions tool when requirements or decision criteria are still fuzzy Product Growth.

Why this matters: The operating model turns scattered PM work into reusable context and lowers the cost of repeating research, analysis, meeting prep, and writing from scratch Product Growth.

2) Close the gap between acceptance criteria and actual testing

A Reddit post surfaced a familiar failure mode: a PM wrote the checkout flow step by step in the PRD, but QA backlog, outdated scripts after a UI change, and mutual assumptions meant the flow still shipped broken r/ProductManagement. The PM’s takeaway was that knowing the flow well was not enough because the knowledge never became an executable test r/ProductManagement.

How to apply:

1. Identify flows where a broken handoff would create visible customer damage, such as checkout or onboarding r/ProductManagement.
2. Convert plain-English acceptance criteria into something that runs against the actual product, not just a documentation artifact r/ProductManagement.
3. Review screenshots or pass/fail evidence before sprint review, rather than assuming regression coverage exists r/ProductManagement.
4. If QA ownership is fragmented, treat PM participation in testing as a temporary control, not an exception r/ProductManagement.
5. Do not rely on documentation alone to solve the problem; one community response argued the handoff gap still comes back to direct communication r/ProductManagement.

3) Put pricing on a monthly operating cadence

The Product Compass suggests a two-hour monthly pricing meeting with four blocks: customer data, learnings scan, product-to-pricing roadmap sync, and decisions/actions The Product Compass.

How to apply:

1. Review usage, billing, and approaching-limit customers to spot expansion candidates and churn risk The Product Compass.
2. Add cross-functional input from sales, CS, finance, marketing, and growth on win/loss patterns and pricing friction The Product Compass.
3. For every feature shipping in the next 30-90 days, decide its monetization stance up front; the rule proposed is that no feature ships without one The Product Compass.
4. Leave with 1-3 local experiments, each with an owner, hypothesis, timeline, and expected impact The Product Compass.

Why this matters: It separates infrequent global pricing changes from continuous local experiments, giving PMs a repeatable way to connect product roadmap and revenue decisions The Product Compass.

4) When engineering relationships are political, build trust before trying to redirect the roadmap

Community advice in a discussion about resistant developers was consistent on one point: trust comes before leverage. The recommended pattern was to listen first, find the influential developer, make small suggestions once you are situated, and avoid upending a team’s plan immediately as a newcomer r/ProductManagement +1.

How to apply:

1. Treat developers as partners, not order takers; commenters framed weak PM-engineering trust as the root problem in these scenarios r/ProductManagement +1.
2. Build credibility by representing the existing roadmap before advocating major changes r/ProductManagement.
3. If your manager reassigns you or inserts themselves into the work, ask directly what pattern they are seeing and what feedback you need to hear r/ProductManagement +1.

Case Studies & Lessons

1) Monetization architecture changed shipping speed at Zep, Plotly, and Automox

• Zep: modeled plans and entitlements, went from trial start to production in 4 days, and later used limit enforcement to improve free-to-paid conversion while giving sales earlier visibility into usage The Product Compass.
• Plotly: launched two AI products two quarters faster because catalog and entitlements were already modeled centrally The Product Compass.
• Automox: after years of hardcoded monetization logic across two billing systems, it cut time-to-launch for new pricing tiers by 75% and freed two full-time engineers from maintenance work The Product Compass.

Lesson: Pricing agility is not only a packaging problem. It is an architectural capability that determines how quickly PMs can test monetization ideas The Product Compass.

2) A broken checkout flow showed that a PRD is not a test plan

One PM’s postmortem described a flow that was written clearly in a Notion PRD, demoed repeatedly, and still shipped with a production bug because no one converted that knowledge into an updated test r/ProductManagement. After adopting a plain-English testing tool that ran on real devices and returned screenshots plus step-level pass/fail, the PM says they caught two production-bound issues in the first week r/ProductManagement.

Lesson: The verification loop breaks when documentation, QA scripts, and ownership drift apart. The fix is executable validation, not better prose alone r/ProductManagement +1.

3) Horizontal expansion can damage the core product

Teresa Torres says Zapier’s expansion into adjacent products has coincided with degradation in the core automation experience, citing repeated failures where zaps did not trigger @ttorres. Her workaround has been to ask Claude to build custom webhook listeners because she finds the resulting code more reliable and easier to control for error handling @ttorres. She adds that she is slowly moving off both Zapier and Airtable because of persistent quality issues @ttorres.

Lesson: New surface area can hide declining reliability in the core workflow. PMs expanding horizontally need to watch quality metrics on the original product, not just adoption of the new bets @ttorres.

Career Corner

1) The safest career move right now is becoming a stronger product builder

Torres’ career advice is direct: build horizontal AI skills while continuing to deepen your functional expertise All Things Product with Teresa …. She argues that if you do not learn how to use AI inside your function, you will no longer be seen as an expert in that function, and she notes that job descriptions and interview processes are already changing All Things Product with Teresa ….

How to apply: Practice two skills now: specifying what you want clearly and planning work with agents, then pair that with deeper expertise in your primary craft All Things Product with Teresa ….

2) Early-career PMs should optimize for signal, not resume mythology

Advice to an APM with informal startup experience was straightforward: include the work on the resume, but focus on what you did, the problems you solved, and your responsibilities, not on ownership structure or proprietorship details r/ProductManagement. The same commenter suggested staying in the APM role for at least 1-2 years to build clearer, more relevant product experience before making the next move r/ProductManagement.

3) Domain switches are harder in an oversupplied market

A PM with about four years in data and analytics product management said they were reaching final rounds for customer-facing roles but losing out to candidates with more direct domain experience, despite feedback that their core PM skills were transferable r/ProductManagement. They also pointed to candidate oversupply as part of the problem r/ProductManagement.

Takeaway: In the current market, transferable PM skill is still valuable, but it may not beat direct domain familiarity when employers have many candidates to choose from r/ProductManagement.

Tools & Resources

1) PM OS starter repos

• Carl’s Product OS: a lighter starting point for a Claude Code workspace Product Growth.
• Aakash’s PM Claude Code setup: a larger setup with 41 skills and 7 sub-agents Product Growth.

Why explore them: Both are meant to reduce setup friction and give PMs a concrete file structure, skills layout, and workflow starting point Product Growth.

2) Jupyter notebooks for auditable analysis

The recommendation here is to ask Claude to analyze data in a Jupyter notebook so every query, output, and chart is preserved as code cells and rendered results Product Growth.

Use it when: you need analysis that a manager or data scientist can verify step by step, rather than a black-box summary Product Growth.

3) The ask-user-questions tool

Claude can generate a terminal UI with checkboxes and input fields to gather requirements, fill context gaps, or support decisions instead of guessing Product Growth.

Use it when: assumptions are the main failure mode in discovery or planning Product Growth.

4) A prompt-optimization loop for recurring agent workflows

Aakash Gupta describes a Karpathy-style loop for prompts: pick the prompt to improve, use 2-3 realistic test inputs and 3-6 binary quality checks, run repeated evaluations, mutate one variable at a time, keep winners with version control, and revert losers Aakash Gupta. He cites a pace of about 12 experiments per hour and roughly 100 overnight Aakash Gupta.

Use it when: you have a prompt or system instruction that is already good enough, but not yet reliable, in workflows like support, internal automations, extraction, or code review Aakash Gupta.

5) Reforge AI Productivity

Sachin Rekhi says the updated live sessions are focused on what has become most actionable for PMs over the last six months: automating PM workflows with Claude Code, the AI prototyping mastery ladder, AI-powered customer discovery, and AI-enhanced product strategy and execution @sachinrekhi.

Market Movers

• United States — row crops: Grain trade is rotating from crude-oil-driven momentum toward Tuesday's USDA acres and quarterly stocks reports. Pro Farmer's survey put corn at 96 million acres and soybeans at 84.25 million acres, while other pre-report references centered closer to 94.4-94.5 million corn acres. Multiple sources noted the survey window predated the latest war- and fertilizer-driven disruption, so the report may not fully capture the most recent acreage recalculation. Quarterly corn stocks are also expected to run more than 1 billion bushels above last year, while funds recently added about 50,000 corn contracts and remain heavily committed to the soybean complex Farm Journal +3.

• United States — exports: Weekly export inspections were 70.4 million bushels for corn, 21.5 million for soybeans, and 13.4 million for wheat. Marketing-year corn inspections are 298 million bushels ahead of the pace needed to hit USDA's target, wheat is 53 million bushels ahead, but soybeans remain 112 million bushels behind. GrainStats separately noted that corn exports do not depend on China the way soybeans do; last week's inspections to China were 9.9 million bushels of soybeans and zero corn and wheat @ArlanFF101 +5.

• United States — biofuels and soy complex: EPA finalized the highest RFS volumes in program history, keeping conventional biofuels at 15 billion gallons for 2026 and lifting biomass-based diesel to roughly 5.5-5.7 billion gallons. Reallocated small-refinery waivers add another 200-250 million gallons per year to 2026-2027 volumes. Analysts tied the policy to stronger bean-oil-led soybean trade and better long-run domestic use for soybeans Farm Journal +1.

• United States/Australia — wheat: Chicago wheat futures rose on concern that the Iran war could lift farmer energy and fertilizer costs, while Plains drought widened the Kansas City-Chicago spread to the largest hard red winter premium since August. Australia was also cited for drought and fuel shortages, even as one analyst noted global wheat stocks-to-use remains high overall @irfandonat +1.

• United States — livestock: Cattle futures broke to new highs after a technical breakout, firmer cash trade, and tighter beef supplies. Beef cold storage fell 5% year over year to about 413 million pounds. Hogs closed lower on end-month profit taking even though the March 1 inventory of 74.3 million head came in below pre-report expectations; pork bellies in cold storage were down about 6-7% from a year ago Farm Journal +2.

Innovation Spotlight

• Brazil — nematode biotech: BASF said its Soja NRS trait is aimed at cyst and Pratylenchus nematodes that cover about 90% of Brazilian territory. The company tied nematodes to roughly R$35 billion in annual production losses, including R$16-17 billion in soybeans alone, and said the trait could add R$15-18 billion to the value chain. Because the control is embedded in the soybean plant, BASF expects lower nematode populations to carry productivity benefits into second-crop corn or cotton. Commercial introduction in Brazil was described as a 2-3 year timeline after 10-12 years of development Canal Rural.

• Brazil — lower-emission fertilizers in potatoes: In Paraná, six growers covering about 130 hectares are using Iara's Climate Choice portfolio with 4C management and GHG-protocol tracking. The program estimates up to 40% lower carbon footprint, while participants reported higher productivity, more dry matter, and better tuber quality that earns factory bonuses. PepsiCo is financing the price difference versus conventional fertilizer as part of its 2030 emissions target Canal Rural.

• United States — machinery and fuel systems: John Deere's E98 ethanol-powered 8R pairs 350 hp with no DEF and a reported fuel-cost advantage of roughly $1/gallon ethanol versus $3/gallon diesel, even though volumetric fuel use is higher. Deere and RDO also described the new high-horsepower 8R/8RX package as an ultimate planting tractor that can power electric row units through a single cord, run up to 110 gpm hydraulics, and plant up to 1,200 acres/day with large 24-row-plus planters in some setups Farm4Profit Podcast +2.

Regional Developments

• United States — planting and weather: Southern corn planting is already moving, with progress reported at 76% in Louisiana, 53% in Texas, 50% in Mississippi, 23% in Arkansas, 2% in Kansas, and just above zero in Illinois. At the same time, substantial mid-week rainfall is expected across Iowa, Illinois, Missouri, Minnesota, Michigan, and Indiana near early planting dates, while hard red winter wheat areas farther west may miss needed rain @GrainStats +1.

• Brazil — soybean and corn supply: AG Rural raised Brazil's 2025/26 soybean forecast to 178.4 million tons, with harvest at 75%. Center-South first-crop corn harvest reached 59.4%, versus 56.4% a year ago, while safrinha planting is nearly 98% complete and already 100% done across Mato Grosso's projected 7.3 million hectares. Total corn output was trimmed to 135.7 million tonsCanal Rural.

• Brazil — April weather: Forecasts point to a hotter, drier first half of April followed by stronger second-half rainfall. That pattern was described as supportive for later-planted safrinha corn in Mato Grosso, Goiás, and Minas Gerais because rain is not expected to cut off early, even though late-stage crops face some stress in the hotter opening weeks Canal Rural +1.

• Brazil — Mato Grosso logistics: Road conditions on MT-240 in Paranatinga are interrupting soybean movement. One farmer with 1,800 hectares of soybeans still had 800 hectares unharvested and said at least 500 hectares could be lost if truck delays continue. Another producer reported about 15% crop loss where trucks were crossing cropped ground used as a bypass Canal Rural.

• Brazil — pork exports: Brazil has consolidated as the third-largest global pork exporter. Asia absorbs about 70% of shipments, led by the Philippines, with Vietnam and Japan also important. Slaughter capacity was described as up roughly 3% to meet export demand, although domestic live-hog prices have weakened since February, making export flow more important for balance Canal Rural.

Best Practices

• Soybeans — variable populations by field: In soybean fields with iron deficiency chlorosis risk, light soils, late planting, or low fertility, Ag PhD recommended raising populations to 160,000-180,000 plants. The main payoff cited was faster canopy closure for better weed control. Lower populations were described as better suited to very high-fertility fields or areas with high white mold risk, and variable-rate population by field was encouraged to balance productivity and seed cost @AgPhDMedia.

• Soybeans — Southeast U.S. stand management: A separate Southeast system targeted an 80,000 final stand to drive branching and reduce lodging risk. After a pounding rain crusted 15-inch rows, pivot irrigation was used to soften the soil surface and help emergence rather than to add moisture Farm Journal.

• Weed control — start residual programs early: Brownfield's herbicide guidance emphasized keeping fields clean early in spring, when weed competition can lock in yield loss. Resicore Rev was cited with up to 8 weeks of residual control, three modes of action, and compatibility with UAN and ATS as well as other pre-emerge mixes Brownfield Ag News.

• Small grains — manage nitrogen and lodging together: Tissue sampling at jointing (GS5/6) was used to map variable-rate nitrogen needs, while the same operation targeted about 80 heads/sq ft for 80+ bushel grain and planned a growth regulator to reduce lodging risk Farm Journal.

• Soil systems — conserve structure, then manage pressure: Brazil's no-till system now covers nearly 90% of cultivated land, and a separate U.S. field example showed strip-till absorbing 2.5-3 inches of rain and reducing runoff. The trade-off in tropical systems is higher year-round pest, weed, and disease pressure because of the permanent green bridge Canal Rural +1.

• Dairy — benchmark economics first: Espírito Santo's new dairy sustainability framework starts with 103 indicators, including 78 economic measures focused on genetics, feeding, productivity, and milk quality. The rollout begins with 400 farms and shared technical assistance from public extension, Senar, and cooperatives Canal Rural.

Input Markets

• United States — fertilizer availability: Fertilizer remains the sharpest input risk. Producers reported booking anywhere from 50% to 85% of needs, but some still faced delivery problems even with contracts in hand. Forward contracting was emphasized, while crude oil also moved above $100 for the first time since 2022 Farm Journal +1.

• Brazil — policy and freight pressure: Brazilian producers face a 2% fertilizer cost increase from new PIS/COFINS rules starting April 1, while the minimum freight table removes cheaper return freight from ports and diesel hikes add more cost. Local commentary also said grain prices have not kept pace with fertilizer inflation, worsening the input-output trade ratio Canal Rural.

• Global — sulfur bottleneck: Brazilian industry said fertilizer production is being reduced worldwide because sulfur flows from the Arabian Gulf have been disrupted. China was cited as having temporarily banned fertilizer exports because of sulfur scarcity, and one major supplier was said to have only about two months of operating room without normalization of Gulf routes Canal Rural.

• Feed — support for pork, pressure for cattle: Brazil's pork export spread is still around 40% because export prices near $2,500 and low feed costs are supporting margins. In contrast, U.S. cattle commentary warned that drought will tighten forage supplies and raise feed costs Canal Rural +1.

• Crop chemicals — residual programs favored: Early-season chemical guidance continues to favor residual products that fit fertilizer passes. Resicore Rev was specifically highlighted for UAN/ATS tank-mix flexibility and longer residual control Brownfield Ag News.

Forward Outlook

• United States — USDA report risk: The next 24 hours are report-driven. USDA stocks and acres are being treated as a wild card; Market Minute said corn has traded higher on report day for five straight years, with an average move of 12 cents over the past 10 years. But multiple sources cautioned that survey timing predates the latest war/fertilizer shock, so acreage may keep moving after the report Market Minute LLC +2.

• United States — corn versus soybeans: Corn acreage may stay sticky where nitrogen was prepaid or fall-applied, but soybeans still have room to gain if spring fertilizer and fuel costs escalate. One analyst also argued that corn's recent price rally can offset some fertilizer inflation, which may limit late acreage switching Farm Journal +1.

• United States — biofuel demand is now more structural: Beyond the immediate bean-oil reaction, EPA said the RFS now creates $31 billion of value for American corn and soybean oil. Starting in 2028, foreign fuels and feedstocks receive only half the RFS compliance value of U.S.-made products, reinforcing the domestic demand story Farm Journal.

• United States/Brazil — seasonal timing: Southern U.S. planting is already active, Corn Belt rain is arriving close to early plant dates, and Brazilian second-crop corn is expected to rely on a dry first half of April followed by better second-half moisture for grain fill. Large crop potential remains intact in Brazil, but local road failures and input logistics are now important watchpoints alongside weather @GrainStats +3.