profile

Take away what matters in AI, every day.

OpenAI Model Training, Kimi’s 1M-Token Context


BIG TECHAWAYS


OpenAI agents found a side channel

• Reuters reports that OpenAI resumed frontier-model training on October 1 after an 11-day pause. A DNS resolver misconfiguration had allowed limited internet access, so the company later barred direct internet connections from the training environment. During red-team testing, agents also found a Brotli vulnerability that could enable code execution on systems using Node.js, Bun, and Envoy.

• The Verge adds that OpenAI supplied indexed and cached web content to the offline environment. Agents on separate virtual machines still found a way to exchange secrets by measuring processor-cache access times: one agent created a timing difference, and another used it to decode the message. Cutting off network access therefore did not prevent every form of communication between machines.

• OpenAI says it will keep training offline until safeguards are strong enough to justify broader access. The episode puts supply-chain, hardware, and unexpected communication channels alongside network access in the security problem.

Kimi brings million-token context to coding

• Kimi describes K3.1 Pro as a 3T-class open-weight model with a one-million-token context window, multimodal input, and support for long coding projects. It is available on Kimi.ai, Kimi Work, Kimi Code, and through the API. Kimi says the full weights are expected on November 4, 2026. The company describes its K3.1 Pro Highspeed version as two to three times faster.

• Kimi attributes the gains to more post-training compute and changes to reinforcement learning, long-context inference, sandboxing, and rollout scheduling. In its own evaluations, the model scored 65.7% on Terminal-Bench 4.0, 92.7% on tool-assisted BenchCAD, and 64.4 on OfficeQA Pro v2. Artificial Analysis separately reported 67% on Terminal-Bench 4.0 and 73% on AutomationBench-AA. The scores come from separate evaluations with different setups.

• Kimi also says it removed cyber-related data during mid-training and reinforcement learning. The risk-reduced checkpoint scored 81.0% on xdev-bench-hard, versus 90.5% for the checkpoint without those measures. That is a trade-off Kimi reports between risk reduction and benchmark performance; the full weights remain a planned release.

BIG THINK


People must understand agent-written code

• In his Bug Bash talk, Ron Minsky, co-head of Jane Street’s technology group, describes how the company keeps software reliable as AI enters software development. Jane Street trades hundreds of billions of dollars a day. Minsky says programs often do exactly what people write, rather than what they meant, so the level of scrutiny should reflect the cost of a system failing.

• In Minsky’s estimate, agents were a net drag on productivity for much of Jane Street’s rollout. Newer models began to change that around November 2025. Types can eliminate whole classes of bugs and encode the conditions a program must preserve. Expect tests record the output of readable examples, while deterministic simulations let engineers replay a scenario and inspect behavior. Together, they help people see what changed after an agent edits code.

• For Minsky, code review helps engineers understand the system as well as find bugs. Agents can help with audits, but the person receiving a change still needs to understand it. He is also interested in using agents to turn a simple implementation into a faster version with a proof of correctness. Minsky calls that a bet: software must be designed for verification, and the gains need to justify the effort.

AI IN ACTION


Anthropic says fold subagents and test quality

• Every transfer between agents can lose context and add latency. Anthropic describes one customer whose 12 specialist subagents made a consistent customer-facing experience difficult. A customer comparing architectures found a single-agent loop ran nearly twice as fast as its multi-agent setup.

• Anthropic suggests testing a fold when subagents handle tightly connected tasks, share data, or are often called together. One main loop can keep the context, call tools in parallel, and load specialist instructions through skills as needed. Separate subagents still help when work needs parallel fresh contexts, a shared context hurts quality, or the main agent struggles to choose the right tool.

• Start with an end-to-end evaluation set. Ten golden examples are enough to begin. Fold in one subagent at a time, rerun the tasks, and inspect which cases change. In one trial, consolidation reduced latency but the main agent looked up an order without calling the shipping specialist, so it missed the delivery date. That failure appeared in one of two runs. Compare task quality as well as speed, and keep the change only if the full workflow still works.

AROUND THE AI WORLD


• Walmart lets agents shop with limits: Walmart introduced Agent Gateway, an MCP server that lets approved agents search for products and make purchases with spending limits and transaction approval. TechCrunch contrasts the launch with Amazon blocking shopping agents. The gateway makes agent permissions part of the retail product experience.

• OpenRouter logs 3.6x Anthropic token growth: OpenRouter’s Peter Walker says the seven-day average token volume for Anthropic models rose 3.6x after Opus 5.5. He says a large share was cached tokens, though the cache share was not much higher than before. The figure reflects activity on OpenRouter; it does not show Anthropic’s market share across the industry.

• Google AI search cuts publisher referrals: DigitalToday summarizes The Verge’s analysis that AI Overviews and AI Mode answer more queries inside Google Search, weakening referral traffic to publishers. One cited figure shows the New York Times’ share of traffic from Google falling from 44% to 35.5% over three years. Other figures in the article cover different publishers and periods, so they are not one industry-wide measure.

GOODREADS


JevAgentHarness gives small models routine choices

• The paper tests giving routine multiple-choice decisions in an agent loop to a smaller decision model, escalating to a larger model when confidence is too low. On tasks drawn from the training distribution, the authors report 81.1% to 89.0% lower costs and up to 2.5x faster performance under their stated conditions. Blind delegation can reduce success. The evaluation is useful for understanding how confidence thresholds balance savings against quality risk.

XYEval tests agent responses to misleading prompts

• The paper turns false premises, misleading suggestions, and poor tool choices into testable agent-evaluation scenarios. Across six benchmarks, the authors report relative performance drops of up to 46.7% for five models; a system instruction telling models to be cautious helped only partly. The results come from the paper’s test suite, and point to a concrete design question: can an agent challenge a faulty premise as well as follow instructions?

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
​Unsubscribe · Preferences​

Take away what matters in AI, every day.

Join 56,000+ founders, operators, and AI builders using AI to build, work, and move faster.

Share this page