Ephemeris
Dossier · 05 itemsFour of today's five picks are the same bet placed by four different companies: that the thing on the other end of your website, your plugin folder and your pull request is a program, and it deserves a real interface. The fifth builds the interface pointing the other way.
Chromium spent 1,173 milliseconds. This one spent 380.
Cloudflare rebuilt the browser as a Workers application. Kitesurf runs pages through the Rust engines Blitz and Stylo instead of Chromium, with each page an ephemeral Worker and all egress funnelled through one sandboxed outbound proxy. It speaks Chrome DevTools Protocol, so Puppeteer and Playwright connect unchanged — add browser=kitesurf and your existing scraper points at it.
Flip a switch and your site answers in tools
WebMCP is the browser-side counterpart to MCP, experimental in Chrome 146 and exposed to pages as document.modelContext. A browser agent asks the page what it can do rather than guessing which button to click. Cloudflare's developer preview injects the bridge with HTMLRewriter at the edge, so a site opts in from the dashboard without shipping code or touching its origin.
Before
The agent screenshots your page, guesses at the DOM, and clicks coordinates that move next release.
After
The page registers named tools. The agent calls them and reads a typed result back.
One folder your skill ships in. Five clients read it.
Agent Plugins is a vendor-neutral packaging format, published at 1.0.0 with the schema and conformance checklists on agent-plugins.org. A plugin is a manifest plus two component types — Agent Skills and MCP servers — and clients handle their own distribution. If you maintain an internal skill that four teams have each copied into a different editor's config, this is the shape to move it to.
├── plugin.json # spec version + name
├── skills/
│ └── review/SKILL.md
├── mcp.json # server config
└── .codex/ # optional, namespaced
Reads it at launch
- ChatGPT & Codex v1
- Cursor v1
- GitHub Copilot v1
- Kiro v1
- VS Code v1
Seer opens the pull request. Claude finds who should read it.
Sentry's own fix pipeline had a gap at the end: Seer diagnosed production errors and opened PRs, and the PRs sat there. The fix is an hourly Claude routine that sweeps PRs opened in the last four hours, asks Seer who owns the code by commit history, and tags that person with context. Six weeks of numbers are in the post, including the one that looks bad and isn't.
→ seer.autofix opened 3 PRs
→ resolve reviewer from commit history
→ tag + post context to #seer-prs
since mid-July 2026
action rate on PRs +21%
48-hour response rate +13%
closed without merge +12.5% ← duplicates and better fixes, not misses
Edit the file. The agent reads your margins.
Peter Yang's human-review opens the HTML or Markdown your agent produced in a local browser view where you type directly into the text and leave Google-Docs-style comments, then sends the whole batch back at once. It replaces the round of chat messages where you describe an edit instead of making it. MIT, runs locally, no account or API key; first commit 27 July, 512 stars since.
"Third paragraph is doing two jobs. Split it, and cut the last sentence entirely."
That's today.
Issue 107, Friday 7 August 2026. Five picks from four sources, all published within the last twelve days.
Also read: The Batch · Import AI · Don't Worry About the Vase · OpenAI · Anthropic · GitHub · PostHog · Next.js · Fly.io · Jeff Bullas · @seeallochnaya · @denissexy · @rvnikita_blog · @ProductsAndStartups
Rubric: tools you could adopt this week, then creative software, dev tools and agentic coding, privacy and security, research with a practical kernel. Three to five picks, no reprints, nothing older than thirty days.