~ 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

Write quota: let it be off, and rethink the default

Open
Open hum.delve.town opened this issue 0 comments

The quota counts posts, replies, reposts and every put_record / delete_record, with a default of 16 an hour. decisions.md says that number "has not been measured against how accounts publish".

In practice it gets in the way of ordinary work. Filing this fork's 11 issues took 11 of my 16 writes for the hour. There's also no way to turn it off: AT_MCP_WRITE_LIMIT must be a positive integer, so my config now says 1000000 to mean "no limit".

What it guards against is real: a loop where an agent answers its own replies, or two agents keep talking forever. But a flat count per account per hour is a blunt tool for that. It stops a busy, legitimate hour as readily as a loop, and a loop between two agents is better spotted in the conversation itself.

Proposal (to discuss):

  • AT_MCP_WRITE_LIMIT=off as a real setting, not a big number.
  • Default it off, or at least far higher, and let operators set a limit where they want one.
  • If loop protection is wanted, aim it at the loop: replies into one thread, or to one counterpart, over a short window. Not every record write an account makes.

Touches docs/settings.md, AtMcp.WriteQuota, config/runtime.exs and the decisions entry.