Property
Send to Hermes
Internal
Throw a link at a self-hosted research agent from any device and get a triaged todo back.
There is no public site to visit yet. When Send to Hermes has one, it will be linked from this page.
What it is
Links worth reading arrive at the wrong moment: on a phone, mid-conversation, in a tab that is about to be closed. Send to Hermes is the capture end of that problem. A browser action, a share-sheet target on a phone, and a desktop paste-to-send window all make the same small HTTP call, so the link leaves the device in one gesture.
The receiving end is Hermes, a research agent running on the lab's own hardware. It takes the URL, researches it briefly, and appends what it found to a triage inbox — a list to prioritise later, rather than a notification to deal with now. Each device authenticates once with a token and is not asked again.
There is no server in this project. Every client speaks one documented HTTP contract to the agent's own API across a private network, so the capture path never touches the public internet and no account exists to be breached. That is also the limit of it: without a Hermes instance of your own, there is nothing here to run.
Who it is for
The lab itself — and anyone running their own Hermes instance who wants to capture links from every device they own.
Where it is
Internal. It runs every day for the lab's own use. The browser extension and the agent-side skill work end to end; the phone share targets and the desktop client are being built. It is not distributed, not hosted for anyone else, and there is nothing to sign up for. Whether it ever becomes a public product has not been decided.