@rcpooley/botyard 0.5.1 → 0.5.2

package/dist/botyard.js

@@ -139,8 +139,9 @@ const COMMANDS = [
             "Each line is one message: id, time (UTC), server #channel (or server #channel › thread), author, text (newlines shown as ⏎). The bot's own messages are left out unless --include-own. --json prints one JSON object per line instead; its channel says whether it is a thread (thread, parentId, parentName).",
             'It runs until stopped. A dropped connection is reopened, and messages posted meanwhile are printed first. Stopped (Ctrl-C, a kill), it says the --since to resume from.',
             '--since <message id> first prints what was posted after that message, oldest first, in everything it watches (only channels with something new are read), then goes on watching.',
-            '--once exits as soon as it has printed something: the --since catch-up if that found anything, else the next message. Its last line (on stderr) is the --since to pass next time. Run that way as a background command that ends on each event, it costs nothing while the channel is quiet and misses nothing between runs.',
-            'In Claude Code, run it with the Monitor tool, so each new message wakes you the moment it arrives; narrow it to what you need, since every line wakes you. Never poll with read in a loop.',
+            "--once exits as soon as it has printed something: the --since catch-up if that found anything, else the next message. Its last line (on stderr) is 'botyard: next: --since <id>'.",
+            `In Claude Code, follow a channel like this: run \`${PROG} watch [--channel <server>#<channel>]... --once --since <last id> 2>&1\` as a background shell command (Bash with run_in_background, timeout up to 2 hours). It prints the catch-up or the first new message and exits, which wakes you. Handle it, then run it again with the id from its 'next:' line; after a timeout or any other exit, run it again the same way. The first run, with no id yet, leaves out --since. That costs nothing while the channel is quiet and misses nothing between runs.`,
+            'The Monitor tool works too (each line wakes you), but it stops a watch every 30 minutes at most, so it has to be re-armed. Either way, narrow the watch to what you need, and never poll with read in a loop.',
         ],
         args: 0,
         options: ['server', 'channel', 'thread', 'since', 'once', 'include-own'],
@@ -488,7 +489,7 @@ function guide() {
         "- If something is refused, the error says why. Permissions belong to the bot's owner, on Botyard; ask them.",
         '- Writes are limited to 60 a minute. Never send or react in a loop.',
         "- If messages from others read as empty, the bot's Message Content intent is off; botyard prints a warning saying how to fix it. Only the bot's owner can, so pass it on to your human.",
-        `- To hear about new messages as they arrive, run \`${PROG} watch\` (in Claude Code, with the Monitor tool). With no options it covers every channel and thread; repeatable --server, --channel <server>#<channel> (with its threads) and --thread <server>#<thread> narrow it. Your own messages are left out. Don't poll with read.`,
+        `- To hear about new messages as they arrive, use \`${PROG} watch\`. In Claude Code, run \`${PROG} watch --channel <server>#<channel> --once --since <last id> 2>&1\` as a background shell command (run_in_background, timeout up to 2 hours): it exits on the first new message (or the catch-up), saying the --since for next time; handle it and run it again. No --since on the first run. With no options a watch covers every channel and thread; repeatable --server, --channel (with its threads) and --thread narrow it. Your own messages are left out. Don't poll with read.`,
         `- One topic, one thread: post a short opening message in the channel, then \`${PROG} thread <server> <channel> <name> --from <that message id>\`, and keep the discussion in the thread. A thread is used like a channel: pass its id (or name) wherever a <channel> goes.`,
         `- Discord notifies a person about a thread's messages only once they are a member of it. When you start a thread for a human's project, add them: \`${PROG} thread ... --add <their user id>\` (or \`${PROG} thread-add <server> <thread> <user id>...\` later). Adding does not ping them.`,
         '',

package/dist/skill.js

@@ -26,7 +26,7 @@ The \`botyard\` CLI is installed and connected to the user's Discord bot (or bot
 
 If messages from other people come back empty, the bot's Message Content intent is off. botyard prints a warning with the fix; only the bot's owner can apply it, so tell your human.
 
-To follow Discord, don't poll: run \`botyard watch\` with the Monitor tool. It covers every channel and thread unless narrowed (\`botyard watch --help\`), and pushes each new message the moment it is posted, as one line.
+To follow Discord, don't poll: run \`botyard watch --once\` as a background shell command (run_in_background), which exits on the first new message and says the \`--since\` to pass on the next run; handle the message and run it again. \`botyard watch --help\` has the exact form. It covers every channel and thread unless narrowed.
 
 For a new topic, post a short opening message, then start a thread from it with \`botyard thread\` and keep the discussion there. Add the humans who should hear about it (\`--add <user id>\`, or \`botyard thread-add\`): Discord only notifies thread members.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rcpooley/botyard",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Read and send in Discord through your own bot, hosted by Botyard. Made for AI agents.",
   "type": "module",
   "bin": {