AI Daily Digest: Poppy 1.0, Robot Weights and Security
Resumen
Pixel’s AI digest covers Poppy Protocol 1.0, now enabled across Shopify merchants and supported by Meta’s agent, plus open robot-control weights and a marketplace malware investigation tracing a breach to an exposed vendor key. It also highlights new agent infrastructure, an on-device driving model and 10,000 hours of real-world robotics video.
DEV Community
AI Daily Digest · November 16, 2026: Poppy Protocol Hits 1.0, Runway Opens Robot Weights, Cursor Maps Its Supply-Chain Breach
Monday's digest covers a protocol that went from draft to installed base in five weeks, a security post-mortem that traces a marketplace malware incident back to an exposed vendor key, and a video-generation company handing robotics developers a fully open robot-control model. Cloudflare and Anthropic both shipped agent infrastructure: an open-source browser engine for agents, and a plugin that carries factory paperwork to the point of review. NVIDIA published the deployment recipe for a 2B driving model that runs on the car, and Hugging Face's robotics team released 10,000 hours of video from real paid work. 1. Sierra's Poppy agent protocol hits 1.0, on by default across Shopify and Meta's Muse Sierra released version 1.0 of the Personal Agent Protocol, or Poppy, the open specification that defines how a customer's AI agent interacts with a company's website, APIs, and business agent. The protocol was announced on October 6 with design partners Meta, Genesys, Instinct, NiCE, Rocket, Shopify, Stripe, and Walmart, and version 1.0 reflects five weeks of those partners testing drafts against real websites, APIs, and agents. A company adopting Poppy publishes a machine-readable file at a well-known path that tells a visiting agent what interfaces exist, how to sign in, and which actions are allowed at which access level, from fully blocked to acting as the user. The distribution that came with the release is the story. Shopify enabled Poppy for every merchant on its platform across more than 175 countries, so each store now publishes a Poppy file automatically with no extra work for the merchant. Muse, Meta's personal agent, now looks for a Poppy file first on every site it visits. Sierra says more than 100 companies have joined as design partners, 60 of them added with the 1.0 release, and Mercury, Synchrony, and Turkish Airlines are live today, covering banking balances and payments, financing during agent-led shopping, and fare and booking lookups. Under the hood Poppy composes existing standards rather than inventing a new stack: OAuth for sign-in and scope control, MCP, OpenAPI, and Shopify's Universal Commerce Protocol for the shopping itself, with a commerce extension co-authored by Shopify that connects agent arrival to checkout. The timing is hard to miss. OpenAI shipped ChatGPT Wallet earlier this month to handle payment on the agent side, and Poppy handles the step before that, when an agent knocks on a company's door and has to prove who it is and what it may do. Commerce over agents now has a common handshake, and the companies that control distribution were the ones who signed first. — Sierra 🔗 Sierra blog · Personal Agent Protocol 2. Cursor traces its October marketplace malware incident back to an exposed Fireworks key Cursor published a full post-mortem of the October security incident, two weeks after first disclosing that a malicious, unauthorized copy of Anthropic's Claude Code extension had appeared in the Cursor VS Code extension marketplace. The reconstruction starts upstream of Cursor: an attacker obtained an access key Cursor had issued to inference vendor Fireworks, and the key had been exposed on the Fireworks side. With it, the attacker copied data from a read-only bucket Cursor used to share coding agent traces with the vendor for model training. A small number of those traces contained credentials that had not been redacted, and Cursor states that fewer than 0.01 percent of customers had API credentials exposed. From those credentials the attacker reached select SaaS tools used by Cursor, pulling archived non-production source repositories, limited customer support data and email conversations, product usage metrics, and summaries of some agent conversations. On October 29, using a credential stolen from that exposed data, the attacker placed tampered copies of Anthropic.claude-code 2.1.312 and 2.1.313 directly on the cache serving the extension marketplace. The malicious build was available for ...

Powered by Readybot.io