🔥 TOP SIGNAL

The practical unit of agentic coding is shifting from a single chat to a supervised handoff. Riley Brown’s CURSOR DELEGATE makes Grokbot the mailbox and Cursor the worker, gives delegated agents a private scratch repository, and returns the cloud agent’s full response; Kody v2026.08.23 makes its factory loop pauseable, scrollable, and inspectable with inline tool calls. @rileybrown +1

For practitioners, separate the control and handoff surface from execution, and make state and tool activity visible rather than burying them in one chat. @rileybrown +1

⚡ TRY THIS

• Build the mailbox-to-worker bridge. Riley Brown’s posted pattern uses literal triggers such as “Send this to Cursor,” “Ask 5.6 Sol,” and “Delegate this.” Route the request to gpt-5.6-sol; only set model_params.reasoning to high when the user asks for “high” or “5.6 Sol high.” Keep the delegated agent’s scratch work in a private repository and return the full Cursor response, not a paraphrase. @rileybrown

• Use Codex’s side chat as a second control lane. While the main thread is running, open /side chat to stage the next question, test review, or follow-up instead of waiting; Derrick Choi calls the feature underrated, and Riley Brown says he uses side chat more than main chat. @derrickcchoi +1

• When the sandbox lacks hardware, move the test—not the goal—to CI. Simon Willison gave Claude Fable 5 this task:

  Put https://smolmachines.com through its paces as a fast secure sandbox. Explore what it would take to use this to run untrusted Python and JavaScript code in a way that is limited in what RAM and CPU time it can take up (protection against "while true") with no network access and filesystem access only to designated files

  Goal is to be able to use this to execute user-provided tasks for things like data transformations

  When the web container had no /dev/kvm, the agent detected the limit, ran the real test battery in a temporary GitHub Actions workflow on the branch, collected logs, and removed the workflow in the final commit. Simon Willison’s Newsletter

• Clamp verbosity before changing models. Boris Cherny says Opus is strong at long-running work and coding but has a known verbosity quirk; the immediate Claude Code workaround is claude /config outputStyle=concise. @bcherny

📡 WHAT SHIPPED

• Codex usage reset and efficiency fixes landed. Tibo identified excess usage from images in long sessions with multiple compactions, high p95+ usage from Computer History, and conversation-title generation; the promised full reset covered all paid subscriptions. The follow-up says the reset propagated and fixes for those issues landed. @thsottiaux +1

• Kody v2026.08.23 — the homepage now plays an auto-progressing agentic conversation that can be paused, scrolled, and inspected, with tool calls opening inline. The release also makes Kody the stated system of record for memories, email, secrets, packages, and connected surfaces; adds scoped packages.invoke specifiers; and prevents UI deploys from resetting MCP connections or running jobs. github

• OmaPilot entered alpha. SpencerGBull released the first OmaPilot plugin alpha for OmarchyLinux and is seeking testers; DHH says the prototype runs on a local Qwen 27B model and that a version is planned for Omarchy 4.1. Treat it as a harness experiment, not a production-ready agentic OS. @SpencerGBull +1

• The surrounding Omarchy ecosystem crossed 1,000 plugins. DHH announced the milestone at omarchyplugins.com, a useful adoption signal for the platform in which OmaPilot is being developed. @dhh

• Client-artifact warning: @b_nnett reports that Cursor’s Grok bot 0.18.0 shipped with runtime source maps enabled and links reconstructed source and downloads. Audit source-map exposure and other shipped artifacts before putting a cloud-agent client in a sensitive workflow. @b_nnett

🎬 GO DEEPER

• 🎧 Talking Postgres — 23:01: “Could I explain this to somebody else?”. The episode’s stated production bar is whether you can explain AI-written code to someone else; its show notes frame understanding, rather than code generation, as the bottleneck. Use this as the review-standard segment. talkingpostgres

• 🎧 Talking Postgres — 09:12: red-green TDD makes agents exercise every line. The timestamp is a compact entry point for turning an agent’s implementation loop into an executable test loop. talkingpostgres

• 🧩 Kody v2026.08.23 release notes. Study the concrete boundary work: a visible factory loop, Kody as system of record, scoped package calls, and session isolation across UI deploys. github

• 🧪 smolmachines / smolvm sandbox research. The useful pattern is the escape hatch: detect an environment constraint, move privileged testing to a suitable runner, preserve logs, and clean up the temporary automation. Simon Willison’s Newsletter

Editorial take: The winning loop today is not “more autonomy”; it is an explicit handoff, a recoverable environment, and an inspection surface around every consequential run. @rileybrown +2