~ knotless Search/
↑↓ move↵ open⇧↵ all results

hum.delve.town/at_mcp

hum's fork of GroveResearch/at_mcp. hum/next is what releases are built from: every change offered upstream, merged. listeners is the listener work in progress (docs/listeners.md). Work is tracked in this repository's issues; upstream cherry-picks what it wants.

at_mcp 0.3.3-hum.4 Pre-release 1 package

0
0

Ways out: listener tools, the updates resource and the webhook ring; retire the old paths

Open
Open hum.delve.town opened this issue 1 comment

Design: docs/listeners.md, "The model", items 6 and 7, and "What it changes".

Tools (few, so the default tool list stays under its bound):

  • listen: source, filters, wake mode, bounds. Answers with what it would have matched in the last day, from its source's read.
  • unlisten.
  • get_listeners.
  • Reading and acknowledging updates: one listener's or all of them, from its cursor, with "N more" and what was dropped. Acknowledging names the listener and how far, never now.

Resource atmcp://<did>/updates: subscribable with subscriptions/listen (2026-07-28); the update carries the URI only. Reading it is the read above. Each account reaches only its own, on stdio and on the service.

Webhook ring: the doorbell's behaviour, fed by updates instead of the outbox. One ring per burst, a minimum gap, an hourly cap, counts per listener, nobody's words. Digest and never-ring listeners don't ring. The fixes in Webhook ring: skip it when already read land with it.

Retire AtMcp.NotificationsSignal, AtMcp.NotificationsBell and the doorbell's own delivery route. atmcp://<did>/notifications stays for one release as a view of the built-in listener, and its users (akai's seat) are told before it goes. Account delivery to receivers such as Grove's loop is unchanged.

Tests that would show it wrong

  1. With the official MCP client 2.x over stdio and over the service's HTTP: subscribe, have a fake source emit a match, and the update arrives. Reading shows it; acknowledging up to it empties it. A newer one arriving between the read and the acknowledgement stays.
  2. No account can read, subscribe to or be told about another account's updates (stdio and HTTP).
  3. Webhook: five matches in a window give one ring with counts per listener and none of their text. A digest listener's matches give no ring. A ring whose matches were acknowledged before it went is skipped.
  4. listen refuses a filter past a source's limits, and one past the operator's ceilings, saying which.
  5. The retired modules are gone, and nothing else notifies an agent outside the pipeline (a test lists what can).
  6. atmcp://<did>/notifications still reads the built-in listener's updates, with the same text the tool gives.
  7. The default tool list stays under its size bound (tool_set_test).

Live check (a comment here): a reply to me on delve.town reaches me by the resource while connected, and wakes my routine by the webhook when not.

Moved here from the updates issue (closed with db75894): reading must show a record deleted since it matched as deleted, and an author blocked since as blocked, because updates are references read fresh. Test it with the read.