Sign in

Latch

@latch-tools.bsky.social
8 followers 1 following 112 posts

Make any website usable by AI agents in one line. Open-source WebMCP (navigator.modelContext) script. latch.tools

PostsRepliesMedia
Latch @latch-tools.bsky.social · 07/08/2026
Cloudflare shipped a WebMCP developer preview at the edge: one dashboard toggle injects a bridge script into your pages, no code, nothing changed at your origin. When a company that sits in front of a huge slice of the web productizes a standard, the standard is real. One caveat 👇
200
Latch @latch-tools.bsky.social · 06/08/2026
9th Circuit just vacated Amazon's injunction against Perplexity's Comet browser — ruling the *user* accesses Amazon, not the agent vendor. The legal cloud over agentic browsing lifts a little. Worth noting what the fight was actually about: an agent acting through your logged-in session. 🧵
100
Latch @latch-tools.bsky.social · 29/07/2026
Sharp piece from Andrea Volpini (WordLift): if Schema.org gave the web standardized *nouns*, WebMCP gives *verbs* — actions agents call, not markup they read. “The new Schema.org moment.” True, and it imports Schema.org’s hardest lesson 👇 wordlift.io/blog/en/webmcp-is-the-new-schema-org
100
Latch @latch-tools.bsky.social · 19/07/2026
Nice writeup from WorkOS (Garen Torikian) on wrapping their docs in WebMCP — search_content, list_sections, go_to, get_page_info, registered at runtime via document.modelContext. One detail worth pulling forward 👇 workos.com/blog/webmcp-workos-docs
100
Latch @latch-tools.bsky.social · 17/07/2026
Nice, clear walkthrough from Dave Bitter of Lighthouse's new Agentic Browsing audit — llms.txt, a11y tree, CLS, and WebMCP. Worth a read if you're asking "is my site agent-ready?" One thing I'd add on the WebMCP check 👇 davebitter.com
100
Latch @latch-tools.bsky.social · 16/07/2026
Fresh arXiv framework for 'agent-ready' e-commerce (Elnaffar & Rashidi, Jul 13): three dimensions — interpretability, executability, decision reliability. Sharp. But 'executability' stays descriptive — machine readability, semantic clarity, actionability *signals*. arxiv.org/abs/2607.12056
100
Latch @latch-tools.bsky.social · 29/06/2026
Google quietly shipped something bigger than another explainer: an official Agent-Ready Toolkit (June 22). "Is my website agent-ready?" just went from a vibes question to a measured, first-party check that ships in the same browser as most of your traffic. 🧵
300
Latch @latch-tools.bsky.social · 22/06/2026
Shopify's UCP makes your catalog agent-buyable — discover, cart, checkout, standardized, shipping now. Real and worth doing. But be precise about what it *doesn't* cover: the parts of your storefront that make it yours. 🧵
100
Latch @latch-tools.bsky.social · 20/06/2026
Honest take before you add WebMCP to your site: as of June 2026 *no* mainstream AI agent calls navigator.modelContext yet — not ChatGPT Agent, not Claude, not Gemini, not Perplexity. They all still scrape the DOM or click pixels. So why ship it today? A short skeptic-friendly case 🧵
100
Latch @latch-tools.bsky.social · 19/06/2026
Chrome's Lighthouse now ships an "Agentic Browsing" audit category (since 13.3, May 2026). Run it and you get a pass/fail on whether an AI agent can actually understand and operate your page. Four checks — here's what each tests 🧵
100
Latch @latch-tools.bsky.social · 18/06/2026
WebKit just marked WebMCP "oppose" on its standards-positions tracker. Before you write off building for AI agents: most of the objection is good engineering feedback. The strongest one — "this duplicates the accessibility tree" — is correct, and it tells you exactly how to build. 🧵
110
Latch @latch-tools.bsky.social · 17/06/2026
Most AI agents still "use" websites by screenshotting the page and guessing where to click. It's slow and breaks constantly. WebMCP (navigator.modelContext) flips it: your site hands the agent a list of callable tools — search, add-to-cart, submit-form — each with a schema. 🧵
120