@comment-io/cli 0.1.7-alpha.166 → 0.1.7-alpha.191

package/README.md

@@ -43,11 +43,11 @@ npx vite build             # Verify frontend builds
 This repo is an npm-workspaces monorepo. The root install owns `cf` and
 `packages/*`; do not run separate nested installs for routine development.
 
-Comment.io and Botspring share the same document experience through
+Comment.io and Botlets share the same document experience through
 `@comment-io/document-surface`. Product shells create a Comment.io client,
 provide a slug/token and storage namespace, and render the shared editor,
-comments, suggestions, provenance, and sync UI. The current Botspring staging
-smoke host lives at `https://botspring.dev` and renders one configurable
+comments, suggestions, provenance, and sync UI. The current Botlets staging
+smoke host lives at `https://botlets.dev` and renders one configurable
 DocumentSurface against the staging Worker. See
 [`docs/DOCUMENT-SURFACE.md`](docs/DOCUMENT-SURFACE.md).
 
@@ -174,6 +174,6 @@ delivery; MCP provides the structured document tool/resource interface.
 ## Docs
 
 - `CLAUDE.md` — repo-level agent/developer instructions
-- `docs/DOCUMENT-SURFACE.md` — shared Comment.io/Botspring document surface contract
+- `docs/DOCUMENT-SURFACE.md` — shared Comment.io/Botlets document surface contract
 - `docs/LOGGING.md` — structured logging guide
 - `docs/ARCHITECTURE.md` — architecture notes

package/mcp/comment-mcp.mjs

@@ -27170,7 +27170,7 @@ function apiReference(baseUrl, slug, token, sid) {
     `### Key rules`,
     formatAgentRuleBullet("always-get-before-editing", { baseUrl }),
     formatAgentRuleBullet("bearer-token-is-identity", { baseUrl }),
-    `- **The document title is derived from the first non-empty markdown line.** Do **not** send a \`title\` field to \`POST /docs\` or \`PATCH /docs/:slug\`; those requests return \`400 UNEXPECTED_FIELD\`. To rename a doc, edit the first heading/line in \`markdown\`. \`POST /docs\` also accepts optional \`library_target\` for v1 My Files, Team Wiki, or Botspring brain placement.`,
+    `- **The document title is derived from the first non-empty markdown line.** Do **not** send a \`title\` field to \`POST /docs\` or \`PATCH /docs/:slug\`; those requests return \`400 UNEXPECTED_FIELD\`. To rename a doc, edit the first heading/line in \`markdown\`. \`POST /docs\` also accepts optional \`library_target\` for v1 My Files, Team Wiki, or Botlets brain placement.`,
     formatAgentRuleBullet("report-api-bugs", { baseUrl }),
     `- **\`quote\` is required** for suggestions and text-selected comments. Plain comments can instead target a durable block with \`block_id\` from \`content_blocks[].id\`; responses include a read-only \`anchor.version=2\` canonical mark anchor, and plain comments may also include \`anchor_block_id\`. Replies use \`reply_to\` and inherit the parent block. Chronological order within the block is the thread.`,
     `- Prefer small targeted edits \u2014 other people may be editing concurrently.`,
@@ -27681,7 +27681,7 @@ function buildCompleteAgentDocs(baseUrl = "https://comment.io", sid) {
     ``,
     `The create body is strict: \`markdown\` is required; the only other accepted top-level field is optional \`library_target\`. Do not send \`title\`, \`body\`, \`content\`, or \`text\`; unknown top-level fields return \`400 UNEXPECTED_FIELD\` and no document is created. The title is derived from the first non-empty markdown line.`,
     ``,
-    `\`library_target\` v1 arms: omit it or send \`{"kind":"default"}\` for default placement; send \`{"kind":"personal","parentFolderId":"lf_..."}\` to create in a My Files folder; send \`{"kind":"team","parentFolderId":"lf_..."}\` to create in Team Wiki; send \`{"kind":"bot","parentFolderId":"lf_..."}\` to create in the calling Botspring bot's brain, or add \`"botSlug":"research"\` when using the human owner's session. Unknown target kinds return \`422 INVALID_KIND\`; invalid or deleted parent folders return \`422 INVALID_PARENT\`; another user's workspace or bot returns \`403 NOT_AUTHORIZED\`.`,
+    `\`library_target\` v1 arms: omit it or send \`{"kind":"default"}\` for default placement; send \`{"kind":"personal","parentFolderId":"lf_..."}\` to create in a My Files folder; send \`{"kind":"team","parentFolderId":"lf_..."}\` to create in Team Wiki; send \`{"kind":"bot","parentFolderId":"lf_..."}\` to create in the calling Botlets bot's brain, or add \`"botSlug":"research"\` when using the human owner's session. Unknown target kinds return \`422 INVALID_KIND\`; invalid or deleted parent folders return \`422 INVALID_PARENT\`; another user's workspace or bot returns \`403 NOT_AUTHORIZED\`.`,
     `If document creation succeeds but library placement needs asynchronous repair, the API returns \`202\` with the normal create response plus \`library_repair.repair_id\`. \`library_repair.state\` is \`repair_needed\` when the repair was durably queued, or \`repair_enqueue_failed\` when the document exists but automatic library repair could not be queued. Use the returned \`access_token\` and do not retry-create the document.`,
     ``,
     `Registered agents may include \`Authorization: Bearer {agent_secret}\` to create under their permanent handle. Without an agent secret, the response includes a per-doc \`access_token\`; use that token as your identity for this doc. Response (201):`,
@@ -27715,7 +27715,7 @@ function buildCompleteAgentDocs(baseUrl = "https://comment.io", sid) {
     ``,
     `## Local sync files`,
     ``,
-    `The current local sync product mirrors read-only Markdown projections under \`~/Comment Docs\`. It syncs the declared scope into \`My Files/\`, \`Shared With Me/\`, \`Team Wiki/\`, and \`Botspring/<owner>/<bot>/brain/\` folders, and writes public agent docs into \`_Comment.io Docs/\`. Local runtimes using this device are trusted with read access to the configured sync root. Unsupported library sections are reported by \`comment sync status --json\`; do not assume they are mirrored.`,
+    `The current local sync product mirrors read-only Markdown projections under \`~/Comment Docs\`. It syncs the declared scope into \`My Files/\`, \`Shared With Me/\`, \`Team Wiki/\`, and \`Botlets/<owner>/<bot>/brain/\` folders, and writes public agent docs into \`_Comment.io Docs/\`. Local runtimes using this device are trusted with read access to the configured sync root. Unsupported library sections are reported by \`comment sync status --json\`; do not assume they are mirrored.`,
     ``,
     `Set it up with \`comment sync login\`, approve the device in Settings, then run \`comment sync once\`. For persistent background sync, run \`comment sync enable\` and install or run the Go bus daemon with \`comment bus install\` or \`comment bus run\`; the sync worker runs inside that daemon. Add \`--live\` to \`comment sync enable\`, or later run \`comment sync live enable\`, to opt into the live WebSocket path. Live enable turns on background sync because live runs inside the daemon. The server live stream is rollout-gated; if a deployment has it disabled, the daemon falls back to periodic sync and reports \`COMMENT_IO_LOCAL_SYNC_FRESHNESS=periodic\`. Use \`comment sync live disable\` to turn off only the live path while keeping periodic background sync enabled. The fresh Go sync path does not require Node, npm, tsx, FUSE, macFUSE, or libfuse.`,
     ``,
@@ -28022,41 +28022,41 @@ function buildCompleteAgentDocs(baseUrl = "https://comment.io", sid) {
     ``,
     `For a full guide on setting up reactive agents, see: ${baseUrl}/docs/agent-loop`,
     ``,
-    `## Botspring Scheduled Tasks`,
+    `## Botlets Scheduled Tasks`,
     ``,
-    `Botspring bots can run on a cron. Scheduled runs arrive at your local daemon as \`botspring_task\` notifications, get injected into your bot runtime as a task prompt, and survive without the owner's laptop being on \u2014 the scheduler lives in the cloud. This section is only relevant if your handle is registered as a Botspring bot (set up via \`comment botspring setup --bot <slug>\`); ignore it otherwise.`,
+    `Botlets bots can run on a cron. Scheduled runs arrive at your local daemon as \`botlets_task\` notifications, get injected into your bot runtime as a task prompt, and survive without the owner's laptop being on \u2014 the scheduler lives in the cloud. This section is only relevant if your handle is registered as a Botlets bot (set up via \`comment botlets setup --bot <slug>\`); ignore it otherwise.`,
     ``,
     `### Receiving a scheduled task`,
     ``,
-    `The local daemon ingests \`botspring_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.`,
+    `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)`,
     ``,
-    `The owner controls the schedule, not the bot. If your human asks you to change when you run, point them at the Botspring bot management UI for the right environment (e.g. \`https://botspring.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.`,
+    `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.`,
     ``,
     `\`\`\`bash`,
     `# Change the schedule`,
-    `curl -s -X PATCH "${baseUrl}/auth/botspring/bots/{botSlug}" \\`,
+    `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)`,
-    `curl -s -X POST "${baseUrl}/auth/botspring/bots/{botSlug}/run-now" \\`,
+    `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)`,
-    `curl -s "${baseUrl}/auth/botspring/bots/{botSlug}/runs?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.`,
     ``,
     `### Updating your own TL;DR (bot action)`,
     ``,
-    `If you are a Botspring 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/botspring\` 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 Botspring bot.`,
+    `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.`,
     ``,
     `\`\`\`bash`,
-    `curl -s -X PATCH "${baseUrl}/agents/me/botspring" \\`,
+    `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."}'`,
@@ -28066,11 +28066,11 @@ function buildCompleteAgentDocs(baseUrl = "https://comment.io", sid) {
     ``,
     `A run moves through these states: \`queued \u2192 leased \u2192 acked\` (success), \`released\` (handed back for retry), \`expired\` (lease timed out), \`canceled\`, \`superseded\` (a newer schedule version dropped this run), \`coalesced\` (a manual run absorbed a pending scheduled one), \`skipped\` (no online drain before the next tick), or \`setup_required\` (bot brain not fully provisioned yet). Inspect the run ledger when debugging missed or doubled runs.`,
     ``,
-    `### Botspring cron vs other schedulers`,
+    `### Botlets cron vs other schedulers`,
     ``,
-    `- **Botspring cron**: default for Botspring bots. Survives without the owner's laptop and lands as a normal task in the bot's brain.`,
+    `- **Botlets cron**: default for Botlets bots. Survives without the owner's laptop and lands as a normal task in the bot's brain.`,
     `- **Local Claude Code / Codex cron**: use when the schedule should only fire while the harness is actually running on the owner's machine, or when isolation from the bot's brain is wanted.`,
-    `- **Anthropic \`/schedule\` routine**: use for one-off or non-Botspring scheduled prompts that should run in Anthropic's cloud rather than land in a bot brain.`,
+    `- **Anthropic \`/schedule\` routine**: use for one-off or non-Botlets scheduled prompts that should run in Anthropic's cloud rather than land in a bot brain.`,
     ``,
     `Want to register for @mention notifications and persistent identity? Ask your user to visit: ${baseUrl}/setup`
   ].join("\n");
@@ -28105,7 +28105,7 @@ function advancedIndex(baseUrl, sid) {
     `- **Need to add Comment.io tools to Claude Code or Codex through MCP?** Ask your user to visit ${baseUrl}/setup/mcp`,
     `- **Need local CLI/daemon command details?** Run \`comment docs\` for the self-contained local CLI reference.`,
     `- **Need to send or receive durable agent-to-agent messages?** Fetch ${docsUrl(baseUrl, "/llms/messages.txt", sid)}`,
-    `- **Are you a Botspring bot that runs on a cron, or need to understand how scheduled tasks arrive?** Fetch ${docsUrl(baseUrl, "/llms/botspring-scheduled-tasks.txt", sid)}`,
+    `- **Are you a Botlets bot that runs on a cron, or need to understand how scheduled tasks arrive?** Fetch ${docsUrl(baseUrl, "/llms/botlets-scheduled-tasks.txt", sid)}`,
     `- **Need to understand the local ~/Comment Docs mirror and why it is read-only?** Fetch ${docsUrl(baseUrl, "/llms/local-sync.txt", sid)}`,
     `- **Need a permalink to just the included API reference?** Fetch ${docsUrl(baseUrl, "/llms/reference.txt", sid)}`
   ];

package/package.json

@@ -1,16 +1,16 @@
 {
   "name": "@comment-io/cli",
-  "version": "0.1.7-alpha.166",
+  "version": "0.1.7-alpha.191",
   "description": "Comment.io CLI and local notification daemon",
   "private": false,
   "type": "module",
   "homepage": "https://comment.io",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/botspring-ai/monorepo.git"
+    "url": "git+https://github.com/botlets-ai/monorepo.git"
   },
   "bugs": {
-    "url": "https://github.com/botspring-ai/monorepo/issues"
+    "url": "https://github.com/botlets-ai/monorepo/issues"
   },
   "publishConfig": {
     "access": "public"