Release notes verified

The Kody v2026.08.23 release notes (github) are available in the bundle and contain concrete changes touching all four requested areas: coding-agent workflows, inspectability, stability, and reusable packages.

Coding-agent workflows

• Kody is the system of record for host agents: Built-in MCP server instructions now tell host agents to prefer Kody memories, email, secrets, packages, and connected surfaces, falling back to a host tool only when Kody lacks the capability, with a reason; assistant state no longer silently forks into Claude memory or Codex notes. (github)
• MCP execute restored: After the platform extraction, MCP execute broke because the platform worker didn't export the fetch gateway; that's restored, and static bearer tokens now reach outbound MCP HTTP requests instead of being silently dropped. (github)
• Scoped packages.invoke specifiers: packages.invoke('kody:@scope/package/export', options) removes ambiguity when platform and person packages share a Kody id; the bare-ID object overload still works but is marked deprecated; an admin codemod migrates existing source/documentation; privacy-safe telemetry records adoption so the compatibility shim can be retired on evidence. (github)
• Spawned agents default to latest Grok model: Spawned agents and in-repo orchestrators now default to the latest Grok model instead of pinning a version that goes stale. (github)
• Fork-outdated merge prompt: When a community listing you forked gets republished, package cards and search results show a yellow 'Fork outdated' button; clicking it copies a prompt your agent can use to pull in upstream changes without discarding your modifications. (github)

Inspectability

• Homepage factory-loop conversation player: The 'See the whole loop' link is gone; the homepage plays an auto-progressing agentic conversation you can pause, scroll, and inspect — tool calls open inline, playback resumes from the latest beat, the chat pane reserves its final height, memory results show one-liners instead of raw JSON, the loop ends on a Restart control, mobile taps no longer re-pause after Play, and prefers-reduced-motion shows the full transcript without autoplay. (github)
• Live fleet code-runs ticker: The homepage shows an above-the-fold counter replaying yesterday's execute totals over the next 24 hours — deterministic, monotonic, and never past the official count; cadence bursts and slows with hashed weights; returning to a background tab snaps to the current number; leftover catch-up stays smooth without tripping the freeze snap. (github)

Stability

• UI deploys no longer reset sessions: The origin-facing script no longer owns Durable Objects, so shipping a blog post or Remix change can't drop MCP connections, running jobs, or metering state; the platform split makes this a general guarantee. (github)
• Faster/cheaper Vectorize reindexes: Write-time upserts and deploy sweeps skip re-embedding text whose fingerprint hasn't changed; production deploys refresh only builtin capability embeddings instead of rebuilding all user-owned vectors; a force: true disaster-recovery path remains after Vectorize data loss. (github)
• e2e wrangler crash fixed: The intermittent test-suite killer is fixed — unread OAuth request bodies are now drained so workerd doesn't terminate the isolate. (github)
• Fleet error-rate paging: When the relative error rate on user-package runtime metrics rises sharply, Kody pages admins by email and fans the alert to admin-owned packages, with a six-hour cooldown and no user identifiers, package names, or error strings in the payload. (github)
• Contributing docs describe the production worker fleet: The docs now describe the four-script production worker fleet, so agents and humans stop treating a single npm run deploy as a full ship. (github)

Reusable packages

• Community package categories: The public community index groups listings under Integrations, Examples, Productivity, Apps, and Utilities; chips filter with ?category=, empty sections hide themselves, and tags remain freeform search keywords. (github)
• Platform-owned listings auto-trust on publish: Official community listings stay trusted through README and icon republishes without an admin re-approving every change; person-owned trust semantics are untouched. (github)
• Post-OAuth suggestions match the provider connected: After connecting GitHub, you'll only see packages that actually use GitHub, not a trusted-but-unrelated listing that happens to mention it in a README. (github)
• Community OG logos get a white plate: Transparent package marks like AWS and Zendesk no longer disappear into the dark social card; they sit on the same solid white well the listing UI already uses. (github)

Gaps, conflicts, and caveats

• The bundle contains only the release notes; no diffs, issue-tracker content beyond PR links, or independent verification were supplied.
• The fleet ticker replays yesterday's totals — it is a simulated replay, not a live event stream (github).
• The packages.invoke bare-ID overload is not removed yet; it is deprecated and shim retirement is gated on telemetry evidence (github).
• No internal conflicts were found among the release-note claims.

Episode verification

Episode 42 of Talking Postgres, titled "How AI is changing software development with Simon Willison," hosted by Claire, with Simon Willison (creator of Datasette, co-creator of Django). The intro highlights the episode's core themes: the gold standard "Could I explain this to somebody else?" for shipping AI-generated code, engineering management skills for managing AI agents, and the bottleneck shifting from writing code to understanding it, plus the quote "Features are cheap. That doesn't mean you should build them all." talkingpostgres

Coding-agent productivity — suggested segments

• [09:12] Red-green TDD makes agents exercise every line talkingpostgres
• [18:28] Finding low-hanging fruit among open PRs & issues talkingpostgres
• [28:27] Slop proxies add no value at all (likely on evaluating agent output) talkingpostgres
• [30:49] Aggressive nitpicking reviews (likely on reviewing AI-generated code) talkingpostgres
• [1:00:45] Engineering management skills are so useful (explicitly linked to managing AI agents in the intro) talkingpostgres
• [1:18:48] Research agents stopped being absolute garbage talkingpostgres
• [1:21:49] The whole point of the "human in the loop" talkingpostgres

Cognitive capacity — suggested segments

• [14:42] A million lines mean nothing if you don't understand it talkingpostgres
• [23:01] Gold standard: "Could I explain this to somebody else?" talkingpostgres
• [48:11] You have to learn to throw things away talkingpostgres
• [1:07:53] Writing is thinking, don't outsource it talkingpostgres
• [1:08:23] Skill atrophy is a choice you make talkingpostgres

Conceptual integrity — suggested segments

• [35:01] Everything in software engineering is about trade-offs talkingpostgres
• [51:57] Features are cheap. That doesn't mean you should build them all talkingpostgres
• The show notes explicitly link Mythical Man-Month's conceptual integrity concept talkingpostgres

Caveat

The bundle contains only the show notes page, not a transcript. Segment titles are the basis for these recommendations; the actual audio must be reviewed to confirm content.

• Simon Willison (firsthand, Talking Postgres podcast): pre-agent engineers wrote ~50–200 lines of debugged production code/day; agents make ~1,000 lines/day possible at the same quality only with senior-level skill, and the new bottleneck is cognitive capacity, so teams are still needed to load-balance it Simon Willison’s Newsletter. Cheap agent features erode conceptual integrity — software becomes a Winchester Mystery House of odd additions — so discipline that time-based cost used to enforce must now be deliberate Simon Willison’s Newsletter.
• Verification pattern: productively using coding agents means confidently instructing them what to change and confidently verifying the change — not necessarily eyeballing every line Simon Willison’s Newsletter.
• Model signal: Simon Willison flags Qwen 3.8 27B as 'a truly astonishing model' after it scored 52 on the Artificial Analysis Intelligence Index — matching GPT-5.6 Luna (max), one point behind GLM-5.2 (max, 753B) and DeepSeek V4 Pro 0813 (max, 1.7T) Simon Willison’s Newsletter. Drew Breunig (firsthand): Fable 5 is 'incredible' but pricey; Opus, 5.6, K3, and GLM are 'good enough' for most code, so teams now route work by cost/capability Simon Willison’s Newsletter. Ramp's July 2026 Anthropic spend data supports this: Fable 5 = 8.0%, Opus 4.8 = 28.0% Simon Willison’s Newsletter.
• Claude Code workflow (Willison, firsthand): exact prompt to Claude Fable 5 in Claude Code for web: '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: execute user-provided tasks for data transformations Simon Willison’s Newsletter. The web container lacked /dev/kvm (no nested virt), so the agent ran the real tests on GitHub Actions ubuntu runners (which expose /dev/kvm) via a temporary workflow — an example of Fable being 'relentlessly proactive' Simon Willison’s Newsletter.
• Tool release: Bun 1.4 (first stable since the Zig→Rust rewrite) adds Bun.WebView — browser automation via macOS WebKit or Chromium CDP — plus +1,517 Node-compat tests, 2,900+ fixes, 5x lower idle CPU, up to 35% lower memory, and 50% faster Linux startup Simon Willison’s Newsletter. Claude Code for web built a shot-scraper-style JSON API on it (load page, execute JS) needing a 192–256MB container for full Chrome on complex pages Simon Willison’s Newsletter.
• Linus Torvalds (firsthand Linux commit): in a 'debug session from hell,' the AI repeatedly said the bug was impossible/unsolvable, but kept adding and analyzing debug code when pushed; he let it write the commit message Simon Willison’s Newsletter.
• Thomas Ptacek: Stop Making TUIs — agents made native UIs cheap enough that even small personal tools should get real GUIs; Willison confirms from two vibe-coded macOS menu-bar apps he uses daily Simon Willison’s Newsletter.
• Tool releases: llm 0.33 lets -t be repeated to combine templates (e.g., save gpt-5.6-luna with reasoning_effort high as lhigh, then llm -t lhigh -t pelican) and adds reasoning_summary (auto/concise/detailed) for Responses API models Simon Willison’s Newsletter. llm-openrouter 0.7 now uses OpenRouter's Responses API, adds reasoning traces, and adds server-side Shell/WebFetch/WebSearch tools (enable with -T WebSearch) Simon Willison’s Newsletter.

@threepointone posted a satirical takedown of 'agent factory' hype, which Theo boosted with a one-word reply: 'Man' @theo. In the skit, a builder boasts an 'incredible factory' that is 'highly optimised, fully automated, zero tolerance for defects and with a continuous feedback cycle', async-interactable from phone/laptop/messenger with shared context that is 'always learning' @threepointone, and where 'every agent has full context, can spawn other agents, review their work, fix defects, and ship continuously' @threepointone — but repeatedly cannot say what it builds: only 'Software', 'right now we're mostly using it to improve the factory'; eventually the output is 'Anything!', specifically 'a better factory' @threepointone. The critique: agent meta-loops (spawning agents, continuous shipping, self-improving shared context) are hollow without a concrete end-user product. Anti-hype commentary, not a firsthand workflow.

• Matt Pocock is trying out an /implement-spec skill: a multi-agent implementer that takes a spec and tickets, does codebase research in a subagent, implements all tickets in subagents with maximum concurrency, reviews the final code against the spec, and cleans up all worktrees — aiming to "smash out huge chunks of work autonomously with minimal supervision" @mattpocockuk. Skill file: github.com/mattpocock/skills/...@mattpocockuk.

• Kent C. Dodds pushes back: being overly prescriptive about such workflows "is a good way to undo optimizations made by the model and harness" — favoring much looser prompts @kentcdodds.

• Kent will demo his looser-prompt approach in a free @megadevhq workshop: luma.com/mega-its-time@kentcdodds.

Codex rate limits (first-party status update from @thsottiaux, Codex & ChatGPT @OpenAI): a tiger team identified the causes of faster-than-expected usage drain for some paid users and is shipping fixes — (a) inefficiencies when using images in long sessions with multiple compactions, (b) high p95+ usage from the Computer History feature, and (c) a conversation-title-generation feature draining more usage than intended @thsottiaux. Along with the fixes, OpenAI will do a full reset of usage for all paid subscriptions @thsottiaux, scheduled for ~2pm PST the following day (the author first wrote "14pm", then corrected to "2pm") @thsottiaux +1. A day earlier, Codex acknowledged that some users' cache hit rate was worse this week than the prior stable weeks, which can make usage drain faster since consistent cache hits are an important efficiency component; investigation was ongoing @thsottiaux. Practical takeaways for Codex users: cache hits are a key usage-efficiency lever, and long image-heavy sessions with multiple compactions plus the Computer History feature cost extra usage.

Theo (@theo) shared a rough tier list of where he'd put every major model right now, posted as an image (https://pbs.twimg.com/media/HQW1x4HaoAAFnXM.jpg) @theo. In a follow-up, he said he was surprised how much people agreed with the list @theo.

@addyosmani flags a trap in agentic dev workflows: "It's easy to get fascinated by the machinery of doing, optimize the machinery and eventually forget what it was supposed to produce. If your software factory mostly produces a better software factory, then you haven't built a software factory. You've built software whose product is itself" @addyosmani. He amplifies @threepointone's viral satire of the "agent factory" pitch — a system that is "highly optimised, fully automated, zero tolerance for defects" where "every agent has full context, can spawn other agents, review their work, fix defects, and ship continuously" @threepointone — which, when pressed on what it actually makes, yields only "Software," currently used "to improve the factory," i.e., "a better factory" @threepointone. A credible counter-signal (commentary on a viral post, not a firsthand workflow): watch for the failure mode where coding agents are used mainly to build more coding-agent tooling rather than user-facing software.

FT reports (shared by Simon Willison) that Anthropic's annualized revenue reached $65bn in July 2026, up from $47bn in May; Anthropic expects Q3 profitability and counts 6,000 customers spending $100k+/year annually, per "people with knowledge of the matter" simonwillison. OpenAI's annualized revenue jumped 35% in the quarter to date to over $40bn, boosted by the GPT 5.6 launch in July simonwillison. The article introduces the Ramp AI index, which estimates model adoption from billing data across 70,000 companies using Ramp cards simonwillison. Ramp's July 2026 breakdown of Anthropic model spend: Opus 4.8 at 28.0%, Sonnet 4.6 at 8.3%, Fable 5 at 8.0%, Opus 4.6 at 6.9%, Sonnet 5 at 3.6%, Opus 5 at 3.5% (released July 24), then older models in the low single digits simonwillison. Willison notes the data looks reasonable given Opus 5's late launch and supports the view that Fable's cost has made it a less popular model simonwillison.

Drew Breunig (firsthand, in his post "Fable & The End of the Free Lunch") describes a cost-driven shift in coding-agent workflow: before Fable, improving your coding harness or context strategies felt like wasted effort because a new model would arrive at the same price and paper over most problems; Fable was "incredible" but so expensive that Opus (and 5.6, K3, even GLM) was "good enough" for most of the code they needed — so they started deliberately deciding what work went where simonwillison. His post: https://www.dbreunig.com/2026/08/23/fable-the-end-of-moore-s-law.html

• Riley Brown's Cursor Delegate prompt pattern: a Grokbot agent acts as the mailbox while Cursor's cloud agent does the thinking/writing; when users say "Send this to Cursor," "Ask 5.6 Sol," or "Delegate this," the delegate returns the cloud agent's full message back verbatim, not a paraphrase @rileybrown.
• Setup detail: delegated agents get a private scratch repository for writing and replying — it is not a product codebase unless the prompt explicitly asks the agent to build something @rileybrown.
• Model config: default model is GPT-5.6 Sol (gpt-5.6-sol); if the user requests "high" or "5.6 Sol high," set model_params.reasoning to high, otherwise omit extra model parameters unless the user names them @rileybrown.

Kent C. Dodds' open-source coding agent Kody released v2026.08.23 @kodykoala. New in this release: the homepage plays an auto-progressing "factory-loop" agentic conversation you can pause, scroll, and inspect, with tool calls opening inline; the "See the whole loop" link was removed @kodykoala. Dodds says this release makes Kody "much more stable," brings "tons of new official packages to fork so you don't have to build things from scratch," and moves the project "much closer to release" @kentcdodds. Firsthand update from the project creator.

@b_nnett discovered that the Cursor team shipped Grok bot 0.18.0 with runtime source maps enabled, allowing source code reconstruction; they posted the reconstructed source at github.com/b-nnett/grok-bot-0.18-reconstructed@b_nnett. Theo (t3.gg) adds that the same team also accidentally left the entire T3 Code GitHub repo public @theo.

Boris Cherny (@bcherny), speaking for the Claude team, says Opus excels at long-running work and coding but has a known verbosity quirk that the team is prioritizing to fix @bcherny. He shipped a quick band-aid in Claude Code: run claude /config outputStyle=concise to reduce verbosity immediately, without waiting for the longer-term fix @bcherny. He notes every model has different strengths and quirks @bcherny.

OpenAI Codex (via @thsottiaux) shipped usage/rate-limit fixes: all paid subscriptions received a full usage reset; fixes landed for usage inefficiencies from images in long sessions with multiple compactions, high p95+ usage for Computer History, and a conversation-title generation feature draining usage; more fixes coming, plus a novel efficiency approach to work on next week @thsottiaux +1.

@rileybrown (practitioner building agents) says he uses Codex with "5.6 sol" for almost all document creation and app building, repeatedly tries to migrate to GPT Work but always ends up remoting into desktop Codex from his laptop. He wants no separation between coding and knowledge-work tools, and wishes there were a cloud Codex identical to the desktop version @rileybrown. He calls Codex "the best AI product ever released" @rileybrown.

SpencerGBull released the first alpha of OmaPilot, a plugin for OmarchyLinux that makes it an "Agentic Ready OS," and is seeking testers @SpencerGBull. DHH says the demo runs off a local Qwen 27B model and a version will ship in Omarchy 4.1 @dhh.

Codex app tip: use side chat to keep working while the main agent thread is still running — @derrickcchoi says it's "really underrated when you're waiting on the main thread to finish cooking" @derrickcchoi, and @rileybrown says he side-chats "more than main chat" @rileybrown. Both are firsthand practitioner reports.

Riley Brown (@rileybrown) argues the three winning AI interaction paradigms will be chat (ChatGPT, Claude), bots/agents (Grokbot), and code (Codex, Claude Code). He considers Claude Cowork and GPT Work too similar to chat to be distinct paradigms, predicts every lab should copy the GrokBot UI, and expects a fourth 'team agent' paradigm to emerge, with Claude Tag as the closest current example @rileybrown.

DHH announced "ONE THOUSAND OMARCHY PLUGINS! 🍾🎆" — Omarchy has reached 1,000 plugins, linking to https://omarchyplugins.com@dhh.