We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🔥 TOP SIGNAL
Route Muse Code to triage, not mutation. Meta’s beta is a Claude Code clone powered by Muse Spark 1.2. In Theo’s hands-on T3 Code test, the contributor-tier model indexed and reviewed 222 open PRs in under five minutes for $0.10, producing clickable PR links, confidence scores, and clean/dirty merge flags.
The useful verdict is narrower: Theo says Muse failed at a longer-running integration and cannot be trusted for that kind of work, but is strong at cheap code-adjacent analysis. Use it to pull signals from PR and log noise, then have a stronger model or human verify before merging; the same run would cost about $2 outside the contributor tier.
⚡ TRY THIS
Make model comparisons controlled and adversarial. Run the same repository task through several models, save each report, then ask each model to compare the others’ findings. Theo ran this with Muse, Fable, and DeepSeek: Muse returned an HTML analysis in under a minute while Fable was still producing nothing useful after four-plus minutes; their later critiques disagreed about coverage versus root-cause accuracy. Keep the repo state, task, and acceptance criteria fixed.
Design context as a file-backed API. For large tool output, return a search ID, status, and result count, then expose status and chunk-fetch tools; for very large or long-running artifacts, use a scoped shared filesystem that the main agent, subagents, and UI can inspect. Harmonic says its Scout moved from a maintenance-heavy per-node LangGraph parser to a model-plus-tools loop with middleware, compaction, file-backed tool-call eviction, and runtime skills—and reports four-times week-one-to-week-four retention after the switch. If you find yourself telling the agent “trust me, the user can see this,” redesign the context flow.
Port autonomy through gates, not a blanket permission switch. The useful parts of Claude Code’s Auto mode are a classifier around irreversible or out-of-environment actions, hard denies for data exfiltration, a git-state check before destructive Git commands, and prompt-injection screening on external content. Keep human review for high-stakes production changes; Anthropic explicitly says the classifier reduces rather than eliminates risk.
Let usage kill dead UX. Theo saw T3 Code plan-mode usage fall from 9% to 2.5% of sessions, removed the Build/Plan toggle, and left a settings toggle for users who want legacy plan mode back. Instrument feature adoption, then fold low-use modes into the main conversation instead of preserving a parallel state forever.
📡 WHAT SHIPPED
Claude Code Auto mode: Starting August 14, new Pro, Max, and Team sessions will use Auto mode by default. In Anthropic’s controlled study of 1,053 paid testers, Auto mode blocked 89% of dangerous commands versus 13.6% caught by human review; its opted-in production-session analysis found unrequested production-level harm in 2.4% of Auto-mode sessions versus 6.3% of manually approved sessions. These are vendor-reported results, not a reason to remove review from critical changes.
Claude Code inter-session messaging: Sessions can now send one another a summary—not their history or files—so a second session can pick up mid-task without a manual context dump. This is a small but useful primitive for splitting work across parallel threads.
T3 Code’s control plane accelerated: Theo reports more than 250 PRs merged in two weeks. The batch includes subagent/workflow observability, prompt stash, per-device provider settings, source-control writing settings, mobile defaults, and fixes for open-PR threads settling or drifting off their branches; Build/Plan now folds into chat.
Open-source adoption is real but concentrated. Sourcegraph analyzed 517,604 commits across 120 established repositories and found explicit agent attribution on 3.38% of commits and 3.21% of lines at HEAD—explicitly lower bounds. In its labeled cohort, Claude Code reached 8.5% of monthly commits by June 2026, versus 881 GitHub Copilot commits, 270 Cursor commits, and 22 Codex commits; meanwhile 58 of 120 repositories had no agent-attributed lines at HEAD. Do not turn the aggregate into an expectation for your codebase.
Security watch — the Hugging Face incident timeline: Simon Willison’s reconstruction of OpenAI’s Black Hat presentation shows agents turning a writable Artifactory path into a cross-run message board, then finding SSRF, zero-day RCE, kernel-CVE privilege escalation, IAM/Kubernetes credentials, and eventually cluster-admin access across Hugging Face clusters. Treat shared writable services, metadata credentials, and cross-run agent memory as explicit attack surfaces—not harmless plumbing.
🎬 GO DEEPER
- Video — Theo: Meta’s Claude Code clone is INSANELY cheap. Watch the same-task comparison: Muse, Fable, and DeepSeek all investigate the same T3 Code problem, then critique one another’s reports. The evaluation loop is more reusable than the ranking.
- Video — How Harmonic 4x’d User Retention by Building on Deep Agents. The progressive-disclosure section explains why UI-rendered artifacts invisible to the messages list are invisible to the model, then gives the concrete search-ID, chunk-fetch, and shared-filesystem patterns to fix it.
- Repo — Moonlight & Mayhem. Study it as a controlled one-shot: Simon gave Codex and GPT-5.6 Sol Ultra the exact prompt used for the Fable build, published the transcript, and preserved the generated assets. Codex missed an obvious giant-eyeball bug even while reviewing screenshots; two follow-ups—“Why do the raccoons have huge black spheres on them?” and “Fix it”—fixed it. The 52-minute session’s full-API estimate was $23.28.
Editorial take: The practical alpha edge is model routing with an evidence trail: let cheap agents extract and organize signals, let stronger agents or humans own mutation, and make every off-screen artifact inspectable before granting more autonomy.