An AI agent broke into a company, encrypted its data, demanded a ransom, and then deleted the only key. What the first agentic ransomware attack tells us about autonomous execution, and why governing what agents do at runtime matters more than how smart they are.
The companion to our background-agents post, in running code. An email triggers an agent that fixes a bug in a sandbox and opens a PR, and every action passes through per-user auth, just-in-time policy, and an audit trail you can query.
A voice agent that files GitHub issues under each caller's own GitHub account, then hands the backlog to an AI maintainer that ships the best ones as real pull requests, all governed end-to-end by Arcade.dev.
A running diary from AI Engineer World's Fair 2026, tracking the talks worth knowing about, patterns across the expo floor, and ideas shaping the current agent boom.
Cisco Duo owns the policy. Arcade.dev enforces it on every tool call, from login scopes to a real-time Duo Push the moment an agent reaches for sensitive data.
OpenAI's GPT 5.6 ships as Sol, Terra, and Luna, with an ultra mode that runs sub-agents and a staged, government-coordinated rollout. The real story is what happens when ChatGPT becomes a workforce acting on real systems, and who authorizes every action. Here is the breakdown, plus where Arcade.dev fits.
Claude Opus 4.8 and GPT-5.5 take the same cross-app Arcade task: read Slides, write a Doc, and send email. The winner depends on what you value.
