Pico Engine 1.10 Is a Security Release Pico Engine 1.10, a security release from the Picolab project, lets a remote MCP client such as Claude connect to an engine through the mesh's existing OAuth ruleset io.picolabs.oauth, with a person signing in via passkey to approve the client, which then sees only the channels that person exposes. The release adds mesh:read and mesh:act scopes, gates pico_tree, pico_channels, query and raise_event channel by channel across a pico subtree, blocks spoofed Host: localhost headers and proxied requests from posing as local callers, and adds event:raw_body() plus math:timing_safe_equal() for constant-time signature comparison alongside the existing math:hmac(). The release notes cover upgrade steps, and version 1.10.1 fixes a startup bug in 1.10.0. Summary: Pico engine 1.10 is a security release. It lets a remote MCP client like Claude connect to an engine through standard OAuth, with a person approving the client using a passkey and the agent seeing only the channels that person chose to expose. Pico engine 1.8 https://www.windley.com/archives/2026/10/pico engine 18 is for builders.shtml gave agents an MCP surface, and 1.9 let picos serve their own views https://www.windley.com/archives/2026/11/giving picos a view.shtml . Both made picos easier to reach, which was the point. But reachability raises an obvious question: who is reaching in, and what are they allowed to do? Pico engine 1.10 addresses that. It's a security release built around letting a remote MCP client, like Claude, safely connect to an engine. A person signs in with a passkey and approves the client, and the client then sees only the channels that person chooses to expose. The major points: mesh:read and mesh:act . A person approves an MCP client through the mesh's existing OAuth ruleset, io.picolabs.oauth , signing in with a passkey. pico tree , pico channels , query , and raise event across a subtree of picos, still gated channel by channel. Host: localhost header or a proxied request as a local caller; internal calls need a passkey session or the engine's internal token. event:raw body hands a ruleset those original bytes on channels set to keep them. The comparison also has to take the same time whether or not the signature matches, or an attacker can recover it a byte at a time by measuring response times; math:timing safe equal does that. Together with the existing math:hmac , a pico can now safely accept signals about payments, orders, and other events from outside services. Picos are meant to be personal: your data, your rulesets, your mesh. Letting an AI agent act on them is only useful if you stay in charge of what that agent can touch. The changes in 1.10 help ensure that decision stays with the person. An agent gets in because you approved it, sees what you exposed, and does only what each channel's policies allow. Default deny matters here because forgetting to configure something should leave you safe, not exposed. The long-standing principle of use-specific channels protected by policies is now being applied to a new kind of caller. The release notes https://github.com/Picolab/pico-engine/blob/master/docs/release/1.10.0.md cover the upgrade steps, and you'll want 1.10.1 https://github.com/Picolab/pico-engine/blob/master/docs/release/1.10.1.md , which fixes a startup bug in 1.10.0. Tags: picos https://www.windley.com/tags/picos.shtml pico+engine https://www.windley.com/tags/pico+engine.shtml security https://www.windley.com/tags/security.shtml oauth https://www.windley.com/tags/oauth.shtml passkeys https://www.windley.com/tags/passkeys.shtml mcp https://www.windley.com/tags/mcp.shtml authorization https://www.windley.com/tags/authorization.shtml ai https://www.windley.com/tags/ai.shtml 1000+dollar+markets https://www.windley.com/tags/1000+dollar+markets.shtml