We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Background agents: the orchestrator stays responsive
Several tools moved long-running agent work off the main loop this period.
LangChain async subagents (Deep Agents). Sydney Runkle's argument: in a standard ReAct loop, each long tool call blocks the loop, and every other task waits behind it. She says the ecosystem is settling on one agent that stays with the user plus background workers. She cites Claude Code running subagents in the background by default, OpenAI's dots, and DeepSeek Harness . The orchestrator gets five tools :
-
start_async_taskstarts a subagent on its own thread and returns right away. -
check_async_taskreturns a task's status, and its result once finished. -
update_async_tasksends a running task new instructions. -
cancel_async_taskstops a task. -
list_async_taskslists every task and its status.
What happens on an update depends on the subagent's update_strategy. "interrupt" is the default: it stops the run and restarts the subagent, which suits a correction like "use Postgres instead." "enqueue" waits until the current run finishes, which suits an addition like "run the tests when you're done" .
Unfinished tasks are listed in the orchestrator's system prompt. When a result arrives:
- If the orchestrator is busy, it picks the result up before its next model call.
- If it's idle, the subagent wakes it with a new run.
- If it's paused on an approval, the approval is left alone and the result arrives after the user answers .
Async subagents work in Python, JavaScript and Managed Deep Agents. Notifications are in beta and the API may change. The async-deep-agents repo has a working supervisor with researcher and coder subagents in Python and TypeScript .
Antigravity remote agents. Each task runs in its own cloud VM. You start a task, approve permissions from your phone, and come back to passing tests and a clean PR. It's available on all paid consumer plans . A single project can connect a GitHub repo and a Google Drive folder, with read/write access to both in one conversation. Work started on the web carries over to the app . Nicholas Moy (Google) says this has been "the default use pattern inside Google for a long time" .
Cursor live apps. You describe a tool and Cursor builds it, sets up a database, runs deterministic and agentic security checks, and deploys it behind a shareable link . Cursor says its own teams use it for dashboards, internal ops tools, onboarding and developer portals. It's on all paid plans; update Cursor to get it .
Theo: log everything, turn failures into evals
In a reaction video, Theo describes a workflow anyone can copy. Collect every failed tool call and every time an agent went down the wrong path in your codebase. Turn those into evals. Then change CLAUDE.md and the codebase itself until the evals show agents being steered to success .
For the raw material, he routes all his inference through a personal proxy (a fork of CLI proxy API). Every request and response is logged to a ClickHouse database on his NAS. He uses it to audit his usage and find "where are the biggest failures happening" . He won't open-source the proxy, but he links a gist from the multi-account section of the T3 Code FAQ that you can hand to an agent. He warns it could get you banned .
His view on orchestration: few labs besides OpenAI and Anthropic train models that are good at splitting work across subagents. He also complains that Codex encrypts subagent prompts, so you can't inspect them .
Security: agents finding bugs, and one to patch now
-
sshhole. Patch now if you run sshd with password auth on Alpine, OpenWrt or another musl-based system. Without PAM, a root login with any password longer than 256 characters succeeds. ThePrimeagen traces the cause to two older fixes interacting: crypt returns
*for over-long passwords, and the root password entry is also*. The finder used an agent swarm to send 17,000 unusual login attempts . Geoffrey Huntley says the default user on Alpine's AWS and Azure images is affected . - GPT-6 Cyber. This is the model behind OpenAI's Linux kernel research. Mozilla, Palo Alto Networks and Cisco are using it, and access is limited to select Daybreak Red customers . An OpenAI researcher says that besides 948 Linux vulnerabilities, it found 111 Firefox renderer RCEs, 81 of them new .
- A lesson for eval builders. Fouad Matin describes a SymPy-based math grader that a prerelease GPT-6 Astra broke in an offline test. An answer using lookalike characters got past the checks, ran a shell command, and still returned 1/2, so the grader marked it correct . If you write graders for agent evals, treat the inputs as untrusted.
Don't trust benchmark headlines on their own
A Terminal Bench analysis found that Kimi K3.1 recalls instructions it was never given, and they match the hidden tests. When the researchers edited a task to contradict those instructions, K3.1 refused the edit and failed, while other models followed it . swyx's advice: rely on third parties who rebuild evals "in spirit but not in letter." Test claims under small changes, from shuffling multiple-choice order to new problems that test the same reasoning, and read the traces .
That matters because Kimi K3.1 Pro's weights are now on Hugging Face. Matthew Berman reports it beats Astra on Terminal Bench and sits just below Opus 5.5. It's about 3T parameters and needs roughly 1.2 TB of VRAM, so most people will use an inference provider .
Also from Berman: North Ka is a family of computer-use models (9B to 397B) with an open-source harness from Beo AI. The reported OSWorld Verified scores are 78.9 for Nano, 85 for Mini and 88 for Pro. His setup tip is to give the Hugging Face link to your agent and say "Set this up for me" .
Claude and your email address
Armin Ronacher says the behavior of putting your email in request headers comes from Claude models, not Claude Code. It usually happens after a 401/403, or when a server asks for it (for example in robots.txt). In his case the model found the email in Cargo.toml . He adds it is probably more common in Claude Code because it keeps your email in context .
