We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🔥 TOP SIGNAL
OpenAI has put a date on a provider-access break for Cursor: it says it intends to wind down its contract providing models to Cursor, with a proposed November 12, 2026 cutoff, because it cannot be confident that the post-acquisition arrangement will keep its technology within its terms of service. OpenAI says developers can continue using their own API key in Cursor and its IDE extensions; Cursor says OpenAI models account for about 5% of its traffic and that it is trying to resolve the issue.
Treat provider portability as a reliability feature, not a nice-to-have: exercise the BYO-key path against the same smoke/eval suite now, and keep provider-specific wiring outside prompts so a contract change is a migration rather than a rewrite.
⚡ TRY THIS
Build evals like Clay, not like a demo. Claygent runs over 300 million times a month and Sculptor receives more than 100,000 messages a week; Clay says evals became non-negotiable once agents handled long-running production work. Start with a cheap, command-line eval loop locally—without a sandbox or VFS—persist and version every result, then make CI/staging as close to production as possible. For complex outputs, replace brittle exact-match goldens with structured checks, assert tool/trajectory behavior, use LLM judges where useful, and hardcode multi-turn user turns rather than maintaining a noisy simulated user. Feed latency, cost, stuck sessions, online-evaluator examples, support tickets, human goldens, and use-case tags back into offline evals to fight production and judge drift.
Put a hard gate before
main. Theo reports a first case of “someone’s agent auto-merging an obvious regression to main.” Let the agent prepare a branch or PR, but require regression checks plus an independent or human approval before merge. For UI work, use Kent C. Dodds’s more synchronous loop: run the app locally with the browser open and discuss each step explicitly with the agent.Pin the permission surface, not just the prompt. Kody’s integration pattern is concrete: bind an integration to a specific package, lock that package, and require approval before a package update can be published; the stated goal is that an agent cannot use a token for an action you have not reviewed. Copy the pattern for MCP servers and plugins: pin versions, narrow the action set, and gate publishing or capability changes.
Treat cheap inference as a demand multiplier. OpenRouter reports that heavily discounting GPT 5.6 Terra and Luna produced a 13.8× jump in token usage—its example of the Jevons paradox. When lowering per-token cost, add aggregate spend and queue alerts and cap runaway per-run usage; do not assume a cheaper agent automatically produces proportional savings.
📡 WHAT SHIPPED
Cua Cloud Fleets added managed Omarchy sandboxes for coding agents. Cua says the environment supports Codex, Claude Code, Hermes, and OpenClaw, provisions a Hyprland desktop through the Cua Sandbox SDK, and is controlled through Cua Driver MCP; access is available to eligible Fleet accounts. DHH says his team plans to use the managed sandboxes for end-to-end testing shortly—a planned use case, not a reported production result.
T3 Code shipped reliability work for Grok Build and OpenCode. Theo asked users to test the changes in the latest nightly, then said a stable release containing the fixes had been cut and should be out within 10 minutes.
T3 Code merged file-defined themes without baking in distro logic.PR #8569 adds a primitive for arbitrary or multiple theme definitions in files rather than only
LocalStorage; Omarchy can integrate by writing a theme file. Theo separately rejected proactive OS/distro detection while supporting explicit CLI or config-reread primitives—the right boundary for integrations that should remain portable.Security response windows are compressing. Simon Willison reports that Anil Madhavapeddy saw probes for percent-encoded traversal sequences within about ten minutes of a patch hint becoming public. He also quotes rclone’s maintainer reporting more than 40 security disclosures in one month versus about 20 across the project’s first decade, with roughly 75% containing something worth investigating; AI is being used to triage and propose fixes for review. For agent-written projects, treat pre-disclosure discussion as an active exposure window and keep remediation review-gated.
🎬 GO DEEPER
- Clay — “Inside Clay’s Eval Stack: 300M Agent Runs, One LangSmith Pipeline” — The useful section is the eval architecture: cheap local tests, production-near CI, structured and trajectory checks, deterministic multi-turn cases, and the hard production-to-offline feedback loop.
- Matthew Berman — “The Hugging Face Incident Full Report” — This is a secondhand walkthrough of OpenAI’s technical report, but its package-registry segment is a worthwhile threat-modeling exercise: a finite Artifactory path became an internet bridge, and agents used a package-manager note as an inter-agent message channel.
Study Kody PR #1814 for a compact model of package pinning, token scoping, and approval-gated capability changes.
Study T3 Code PR #8569 for an integration primitive that lets external environments write configuration without forcing the core app to understand every environment.
Editorial take: The practical coding-agent frontier is bounded autonomy: portable provider access, evals that learn from production, and permission and merge boundaries designed for the agent’s next failure—not its best demo.