Documentation
¶
Overview ¶
Command approver runs one scripted run to a publication-shaped approval, serves approver/webhook over its database on a loopback port, and acts as the chat bot on the other end: it fetches the approval's text rendering, prints it as the message an operator would read, posts the decision bound to the hash it showed, and then resumes the run the way the consumer's own process would. It makes no network calls beyond loopback and needs no model.
go run ./examples/approver [-db path] [-reject]
-db defaults to a fresh file under a per-user cache directory (os.UserCacheDir()/agentrt), created 0700. -reject has the bot refuse the approval instead, which cancels the run.
Click to show internal directories.
Click to hide internal directories.