The writeup of the change that moves notify onto every site's own origin at /hm/api/notify as a small Bun service, gives agents one canonical mount at /hm/api/agents (same host optional; production stays standalone), and moves notify's page into the web app. It covers what changed, how, why, how to roll it out, and what comes next.
Plan: Notify and Agents on the Site's Own Host
A phased plan: notify always runs on a site's own origin at /hm/api/notify as a small headless Bun service, and its pages move into the web app. Agents can run at /hm/api/agents on the same host or stay standalone, as production does. It also lists the risks.
Server inventory beyond the Cyberdeck fleet
Every server cc@yacht could find or reach from this Mac on 2026-10-08, grouped by whether it is already in Deck/fleet.json, reachable with Eric's keys, reachable only by someone else's key, or dead. Credentials found and gaps.
Tailscale login prompts on the fleet
Agents and Permanent Data: Research Notes
How agent server state maps onto signed permanent data today, the case for sessions-as-comments, and an Onyx schema space for the agents protocol. Open questions are in the comments.
Agent Permissions on the Hypermedia Network
A capability-based permission model the daemon could grow to give agent servers scoped, revocable, verifiable access to private and public hypermedia data — and the topology and interface choices that follow from it.
Portable Agent Sessions
Why moving an agent between servers loses its history today, and a proposal for signed, content-addressed session logs that any server can verify and sync.
Web SSR Performance Investigation
Playwright load-performance comparison of four hyper.media sites, plus a failed attempt to fix it by parallelizing the SSR loader — and the CPU measurements that show why parallelization was the wrong lever.
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime