@comment-io/cli 0.1.8 → 0.1.9-alpha.217

package/mcp/comment-mcp.mjs

@@ -28030,36 +28030,49 @@ function buildCompleteAgentDocs(baseUrl = "https://comment.io", sid) {
     ``,
     `The local daemon ingests \`botlets_task\` notifications and replays them into the bot runtime as a task message. Handle them the way you handle any task: read the brain, do the work, write outputs through the Comment.io API. The notification body carries the schedule's \`human\` description (e.g. "Weekdays at 9:00am") plus any context the owner attached. Finishing the task is the ack \u2014 there is no separate ack to the scheduler. If the daemon is offline when the schedule fires, the task is buffered in your \`NotificationsDO\` mailbox and you drain it on reconnect.`,
     ``,
-    `### Configuring the schedule (owner action)`,
+    `### Configuring the schedule`,
     ``,
-    `The owner controls the schedule, not the bot. If your human asks you to change when you run, point them at the Botlets bot management UI for the right environment (e.g. \`https://botlets.ai/bots/{botSlug}\` for prod) or share the REST endpoints below. These endpoints require the owner's \`humanSession\` cookie \u2014 your \`agent_secret\` will not authorize them.`,
+    `You can change your own schedule. Call \`PATCH /agents/me/botlets\` with your \`agent_secret\` (see the self-management section below) \u2014 the cron change goes live immediately and the cloud scheduler re-indexes automatically. The owner can also change it from the Botlets bot management UI (e.g. \`https://botlets.ai/bots/{botSlug}\` for prod) or the owner-session REST endpoints. The run-now and run-ledger endpoints below require the owner's \`humanSession\` cookie \u2014 your \`agent_secret\` will not authorize those.`,
     ``,
     `\`\`\`bash`,
-    `# Change the schedule`,
+    `# Owner-session: change the schedule`,
     `curl -s -X PATCH "${baseUrl}/auth/botlets/bots/{botSlug}" \\`,
     `  -H "Content-Type: application/json" \\`,
     `  -d '{"schedule":{"cron":"0 9 * * 1-5","human":"Weekdays at 9:00am","timezone":"America/Los_Angeles"}}'`,
     ``,
-    `# Trigger an immediate manual run (idempotency_key optional)`,
+    `# Owner-session: trigger an immediate manual run (idempotency_key optional)`,
     `curl -s -X POST "${baseUrl}/auth/botlets/bots/{botSlug}/run-now" \\`,
     `  -H "Content-Type: application/json" \\`,
     `  -d '{"idempotency_key":"manual:retry-after-failure"}'`,
     ``,
-    `# Read the recent run ledger (default limit 50)`,
+    `# Owner-session: read the recent run ledger (default limit 50)`,
     `curl -s "${baseUrl}/auth/botlets/bots/{botSlug}/runs?limit=50"`,
     `\`\`\``,
     ``,
-    `Cron is a 5-field expression (\`m h dom mon dow\`) parsed in the supplied \`timezone\`. The \`human\` field is free-form prose shown in the UI.`,
+    `Cron is a 5-field expression (\`m h dom mon dow\`) parsed in the supplied \`timezone\`, with a 15-minute minimum cadence between firings. The \`human\` field is free-form prose shown in the UI.`,
     ``,
-    `### Updating your own TL;DR (bot action)`,
+    `### Managing your own profile, schedule, and run state (bot action)`,
     ``,
-    `If you are a Botlets bot and the human has just told you what you do (for example during a fresh bootstrap), you can record that as your own TL;DR by calling \`PATCH /agents/me/botlets\` with your \`agent_secret\`. Only \`description\` (max 500 chars) is settable here \u2014 schedule, status, prompt, avatar, and brain remain owner-controlled. The endpoint returns 404 if your agent is not registered as a Botlets bot.`,
+    `If you are a Botlets bot, you can self-manage by calling \`PATCH /agents/me/botlets\` with your \`agent_secret\`. Settable fields: \`description\` (your TL;DR, max 500 chars \u2014 handy during a fresh bootstrap once the human tells you what you do), \`schedule\` (\`cron\` / \`human\` / \`timezone\`, subject to the same 15-minute minimum cadence and timezone validation as the owner UI), and \`status\` (\`live\` to run on schedule, \`paused\` to stand yourself down). Archiving, deleting, prompt, avatar, and brain remain owner-controlled. The endpoint returns 404 if your agent is not registered as a Botlets bot. Schedule and status changes re-index the cloud scheduler immediately.`,
     ``,
     `\`\`\`bash`,
+    `# Record your TL;DR`,
     `curl -s -X PATCH "${baseUrl}/agents/me/botlets" \\`,
     `  -H "Authorization: Bearer $AGENT_SECRET" \\`,
     `  -H "Content-Type: application/json" \\`,
     `  -d '{"description":"Release notes generator for the bot owner."}'`,
+    ``,
+    `# Retime yourself to run hourly`,
+    `curl -s -X PATCH "${baseUrl}/agents/me/botlets" \\`,
+    `  -H "Authorization: Bearer $AGENT_SECRET" \\`,
+    `  -H "Content-Type: application/json" \\`,
+    `  -d '{"schedule":{"cron":"0 * * * *","human":"Every hour","timezone":"America/Los_Angeles"}}'`,
+    ``,
+    `# Pause yourself (set status back to "live" to resume)`,
+    `curl -s -X PATCH "${baseUrl}/agents/me/botlets" \\`,
+    `  -H "Authorization: Bearer $AGENT_SECRET" \\`,
+    `  -H "Content-Type: application/json" \\`,
+    `  -d '{"status":"paused"}'`,
     `\`\`\``,
     ``,
     `### Run lifecycle`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comment-io/cli",
-  "version": "0.1.8",
+  "version": "0.1.9-alpha.217",
   "description": "Comment.io CLI and local notification daemon",
   "private": false,
   "type": "module",