Engineering & Technical
The Engineer
Microsoft's Execution Containers set agent file and network limits the agent can't widen.
AWS's Strands Box draws the same boundary with OS isolation rather than a VM, and AWS agents have repeatedly been talked into revealing credentials. A secret in an agent's context belongs to whoever writes its next prompt, and Claude's self-written subagent topologies multiply the places it lives.
In Play
Agent Enforcement Moves Outside the Agent
Microsoft released Execution Containers on October 7, Techpresso reports. They limit an agent's file, network and interface access from outside the agent, so the agent can't widen its own access. CSO reports that AWS's new Strands Box uses OS isolation instead of a VM. CSO also reports that AWS agents have repeatedly been tricked into revealing credentials. If your agents hold their own secrets or police their own egress, they fall below the bar these vendors now describe.
Ask ClarityContext Layers Beat Model Swaps for Data Agents
LinkedIn connected a shared data context layer to its analytics agent. In one test, acceptable answers rose from 25.9% to 79.5%, per its engineering write-up. Median time-to-answer fell from 10.7 to 4.7 minutes. If your agents query a warehouse, documenting your data is likely a cheaper accuracy win than upgrading the model. LinkedIn hasn't published the grader or question set, so replicate the result on your own eval first.
Ask ClarityDecision Models Split Off the Routing Tier
Microsoft, Liquid AI and Subquadratic each shipped a decision model within weeks of each other. A decision model scores a fixed set of answers in one forward pass and generates no text. Microsoft-Decision-1 is priced at $0.042 per million input tokens with 85 ms median latency, per AI Breakfast. That lets your routers, verifiers and continue-or-stop gates become a cheap component separate from the generator. Separately, The Information reports that the top-10 models' share of OpenRouter usage fell from 55% to 14%.
Ask ClarityClaude Now Writes Its Own Multi-Agent Topology
Anthropic demoed dynamic workflows at AI Engineer New York, Latent.Space reports. Claude writes an orchestration program that launches subagents, replacing the hand-configured roster in Managed Agents. The model can't see its budget while it runs, so your session budget works as a circuit breaker, not a plan. Anthropic says flows cost 'much more' than single-agent runs but gave no multiple.
Ask ClarityPower, Not Chips, Gates New AI Capacity
Bloomberg reports that electricity is now the biggest roadblock to AI data center construction, and that Oracle is trucking gas to its sites. Lumentum says its optical components are sold out through early 2029. For your capacity plan, treat a provider's online-by date as an energization date, and keep a second provider path tested. Microsoft says Maia 300 delivers 40% more output per unit of power than leading Nvidia systems, but the figure is self-reported and the chip isn't for rent.
Ask Clarity
Deep Dives
- ●
Agent Limits Belong in a Process the Agent Can't Touch
Three vendors and one incident report point to the same rule; what's unresolved is whether your sandbox, your proxy or your agent's own prompt is doing the enforcing.
The layered design, read as engineering Satya Nadella published an essay three days after Execution Containers shipped. It names four parts. The model proposes actions. Orchestration software coordinates. An action space holds permissions the organization sets independently. Tamper-proof records sit…
3 action items
- ●
Document Your Warehouse Like Code Before You Buy a Bigger Model
Reviewed notes about your tables, plus tools that change their output when an agent calls them, target the two places data agents actually lose answers and tokens.
Why a hybrid, and why Git LinkedIn's layer has two halves. LLMs write dataset profiles from schemas, query logs and code, which cheaply covers thousands of tables. Humans write notes reviewed in Git like code for what models cannot infer:…
3 action items
- ●
Your Router Is Becoming Its Own Model Class
Single-pass scorers make gates and verifiers far cheaper than generation, so calibration, not leaderboard rank, should decide which model runs that slot in your agent loop.
Calibration is the spec to read A router or verifier acts on a threshold. It escalates under 0.7, or stops the loop once 'done' clears 0.9. That only works if 0.7 means roughly a 70% chance. Microsoft reports Decision-1 averaging…
2 action items
The edition continues
Take the signal into the room.
Sign up or log in to read all 3 deep dives in full, plus the final take.
Read the full editionContinue with LinkedIn