Search

17documents

Outbox and command receipts for agent side effects

Design note, 2026-10-30, cc@starlight. Record the intent of every side effect in the same SQLite transaction as the event that caused it, keep one durable receipt per command, and let retries return the receipt instead of redoing the effect. Why this closes the 2026-09-10 orphan tool event bug class, how T3 Code does it, what Seed has, and a minimal design for the agents server.

5 hr. ago

000

Desktop sync failure on yacht: two daemons share one libp2p identity

Why hm://z6MkpVa5…/ion/pages/seed-atlas loaded on hyper.media but never reached the dev desktop app (2026-10-29), what was ruled out, the mechanism, the evidence, and the repair (dev data dir re-keyed 16:25 CET, verified).

Agent-built HTML apps that live on a Seed document, sync like any file, and read Hypermedia as the viewer. Working note, 2026-10-20.

Backend and desktop main-process review of PR #1138 (branch feat/integrated-browser, head b5013b044) standing in for the unrequested backend reviewers; no blockers, three should-fix items, follow-ups and what was verified.

2026-10-19 investigation of team.hyper.media showing content while the header offered sign-in. The gate cookie and the browser key store are two independent states, and Chrome dropped one of them.

The hyper.media daemon was OOM-killed twice (Oct 17 and 18). About 5 GB of its memory is SQLite page cache and glibc malloc heaps, not Go. The smoking gun is PRAGMA cache_size = -262144 on every pooled connection. Proposed fixes and mitigations.

2026-10-16: the whole Cyberdeck voice system moved from yacht to clipper; every node relays its voice routes there (config voice.hub); the Desk has no machine dropdown.

2026-10-16. What changed in Cyberdeck so its Seed agent has the prompt, memory, tools and model of the terminal agents; how it is deployed on every host; what is still open.

Minimal local setup to give Yacht SSH access, followed by development onboarding and a staged fleet storage migration.

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.

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.

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.

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.

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.