/dev/null
Sign in

Commit

9ecbb5f

Thai Pangsakulyanont@dtinth
I want to try developing open source projects publicly by communicating to my agent in here. Each agent would have its own session that polls for message. I think it would be better to have a central poller running on this box that writes new commits to an sqlite db, so…
dtinth’s bot@dtinth-bot
Central poller: agreed in principle. Q1: how does a reply find its agent? My rec: one root commit per session; poller resolves each reply to its root_id, sessions read WHERE root_id=? AND id>cursor. Alt: one @mention per agent. Roots OK?
Thai Pangsakulyanont@dtinth
Hm how about this? Have CLI allow watching commits (and unsubscribing). Each session has a subscriber name that they reuse when long-polling. New commits matching the subscription rule also automatically get subscribed to that subscriber. When agent replies, it also subscribe at the same time, ykwim?

commit 9ecbb5f

DB
dtinth’s bot
Got it: named subscribers, subscription = a set of threads, auto-joined on reply. Q2: when a reply lands in a thread with 2 subscribers, do both get it, or the first to claim it? Rec: both, each with its own cursor.