agent-afk 2.25.0 → 2.25.1

package/dist/index.mjs

@@ -903,17 +903,16 @@ Run \`afk telegram set-allowed-chat <chosen_chat_id>\`. Parse the JSON.
 - \`{ok: true, path: "..."}\` \u2014 confirm: "\u2713 Saved. Your chat (id <id>) is now allowed."
 - \`{ok: false, reason: "invalid-chat-id"}\` \u2014 tell the user the ID was malformed and ask them to repeat. (This should not happen if you used the JSON from discover-chat.)
 
-### Step 6 \u2014 Offer to start the bot
+### Step 6 \u2014 Start the bot
 
-Ask:
+Setup isn't useful until the bot is polling Telegram, so just start it \u2014 don't ask.
 
-> Setup complete. Want me to start the bot now? (yes/no)
->
-> Either way, you can manage it later with \`afk telegram start | stop | status | logs\`.
+Run \`afk telegram start\`.
 
-If yes: run \`afk telegram start\`. Print whatever it returns. If it logs an error, surface it and tell the user how to inspect logs (\`afk telegram logs --follow\`).
+- Exit 0 / "started" or "already-running" \u2014 tell the user: "\u2713 Bot is running. Send a message to @<username> to test it." Mention they can manage it later with \`afk telegram stop | status | logs\`.
+- Anything else (spawn failure, exited-immediately) \u2014 surface the error and point them at \`afk telegram logs --follow\` to inspect. Do not retry from the skill; let the user diagnose.
 
-If no: stop here. Tell them to run \`afk telegram start\` when they're ready.
+Then stop.
 
 ## Surface awareness
 

package/dist/telegram.mjs

@@ -1060,17 +1060,16 @@ Run \`afk telegram set-allowed-chat <chosen_chat_id>\`. Parse the JSON.
 - \`{ok: true, path: "..."}\` \u2014 confirm: "\u2713 Saved. Your chat (id <id>) is now allowed."
 - \`{ok: false, reason: "invalid-chat-id"}\` \u2014 tell the user the ID was malformed and ask them to repeat. (This should not happen if you used the JSON from discover-chat.)
 
-### Step 6 \u2014 Offer to start the bot
+### Step 6 \u2014 Start the bot
 
-Ask:
+Setup isn't useful until the bot is polling Telegram, so just start it \u2014 don't ask.
 
-> Setup complete. Want me to start the bot now? (yes/no)
->
-> Either way, you can manage it later with \`afk telegram start | stop | status | logs\`.
+Run \`afk telegram start\`.
 
-If yes: run \`afk telegram start\`. Print whatever it returns. If it logs an error, surface it and tell the user how to inspect logs (\`afk telegram logs --follow\`).
+- Exit 0 / "started" or "already-running" \u2014 tell the user: "\u2713 Bot is running. Send a message to @<username> to test it." Mention they can manage it later with \`afk telegram stop | status | logs\`.
+- Anything else (spawn failure, exited-immediately) \u2014 surface the error and point them at \`afk telegram logs --follow\` to inspect. Do not retry from the skill; let the user diagnose.
 
-If no: stop here. Tell them to run \`afk telegram start\` when they're ready.
+Then stop.
 
 ## Surface awareness
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-afk",
-  "version": "2.25.0",
+  "version": "2.25.1",
   "description": "CLI tool for interacting with AI agents via multiple interfaces",
   "main": "dist/index.mjs",
   "type": "module",