feat: Add /stop and /start commands for telegram bot (Issue #1081) #1111

konard · 2026-01-11T04:24:05Z

Summary

Add /stop and /start commands for the Telegram bot that allow chat owners to control whether the bot accepts new tasks in their chat.

Key features:

/stop command puts the bot in read-only mode for the chat (owner only)
/stop <reason> - Optional reason text that will be shown in rejection messages
/start command resumes accepting tasks (owner only)
Only the chat creator can use these commands (not admins)
When stopped: /solve and /hive are rejected with a clear message (including reason if provided)
Read-only commands (/help, /limits, /version) remain available
Existing queue items continue to process (graceful stop)
State is per-chat and resets on bot restart

Implementation Details

New module: src/telegram-start-stop-command.lib.mjs
- Per-chat stop state management using Map<chatId, StopInfo>
- StopInfo includes: stoppedAt, stoppedBy, and optional reason
- Exports: isChatStopped(), setChatStopped(), getChatStopInfo(), getStoppedChats()
- Owner-only access control following the pattern from /top command
Changes to telegram-bot.mjs:
- Import and use isChatStopped check in /solve and /hive handlers
- Register /start and /stop commands from the new module
- Update /help to show stopped status (with reason) and document new commands
- Update rejection messages to include reason if provided
Test script: experiments/test-start-stop-command.mjs
- Tests all state management functions
- Tests for reason support (tests 10-13)

Test Plan

Fixes #1081

🤖 Generated with Claude Code

Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #1081

Create telegram-start-stop-command.lib.mjs module with: - Per-chat stop state management using Map - isChatStopped() and setChatStopped() for state control - getChatStopInfo() and getStoppedChats() for status queries - Owner-only access control (creator, not admins) - Graceful stop: existing queue items continue to process This is the core module for issue #1081. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Changes to telegram-bot.mjs: - Import isChatStopped and getChatStopInfo from new module - Add stop check to /solve command (rejects if chat stopped) - Add stop check to /hive command (rejects if chat stopped) - Register start/stop commands from new module - Update /help to show stopped status when applicable - Add /stop and /start to help command list Fixes #1081 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add test-start-stop-command.mjs to experiments folder with tests for: - Initial state (no chats stopped) - Stopping a chat - Getting stop info - Per-chat isolation - Getting all stopped chats - Starting (un-stopping) a chat - Multiple chats can be stopped independently Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Format telegram-start-stop-command.lib.mjs with prettier - Compact command registration in telegram-bot.mjs to stay under 1500 lines - telegram-bot.mjs now at 1487 lines (was 1502) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

This reverts commit 543d74e.

konard · 2026-01-11T04:42:08Z

⚠️ Solution Draft Finished with Errors

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Public pricing estimate: $7.231747 USD
Calculated by Anthropic: $0.000000 USD
Difference: $-7.231747 (-100.00%)

Note: The session encountered errors during execution, but some work may have been completed. Please review the changes carefully.

📎 Log file uploaded as Gist (1505KB)
🔗 View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-01-19T22:16:22Z

Resolve conflicts, and add optional reason support for /stop command (any text after the command /stop ). So all other write commands will show this reason, if it is provided.

konard · 2026-01-19T22:17:38Z

🤖 AI Work Session Started

Starting automated work session at 2026-01-19T22:17:36.170Z

The PR has been converted to draft mode while work is in progress.

This comment marks the beginning of an AI work session. Please wait working session to finish, and provide your feedback.

- Add reason parameter to setChatStopped() function - Parse reason text from /stop command (text after "/stop ") - Display reason in /solve and /hive rejection messages - Display reason in /help stopped status section - Display reason when /stop is called on already-stopped chat - Add tests for reason functionality (tests 10-13) Resolves conflict with main branch by merging accept_invites command. Fixes #1081 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

…count - Add getStoppedChatRejectMessage() helper to start-stop module - Use helper in /solve and /hive handlers to reduce code duplication - Simplify verbose logging with VERBOSE && console.log() pattern - Reduce telegram-bot.mjs from 1534 to 1488 lines (under 1500 limit) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

konard · 2026-01-19T22:31:19Z

✅ Resolved

I've addressed all the feedback from the latest comments:

Merge conflicts resolved

Merged the latest main branch changes (including the /accept_invites command from PR feat: Prevent duplicate URLs in /solve queue #1110)
Updated /help command to include both new commands

Optional reason support for `/stop` command

/stop now accepts an optional reason: /stop Maintenance in progress
The reason is stored in the stop info and displayed in:
- /stop confirmation message
- /solve and /hive rejection messages when the bot is stopped
- /help stopped status section
- "Already stopped" message when /stop is called again

Code quality

Extracted getStoppedChatRejectMessage() helper to reduce code duplication
Reduced telegram-bot.mjs from 1534 to 1488 lines (under the 1500 limit)
All local tests pass (npm run test + experiments/test-start-stop-command.mjs)
All CI checks are passing

Example usage

/stop                           → Stops bot with no reason
/stop Maintenance in progress   → Stops bot with reason "Maintenance in progress"

When stopped with a reason, rejection messages will show:

❌ This bot is currently stopped in this chat and not accepting new tasks.

*Reason:* Maintenance in progress

Use /start to resume (chat owner only).

🤖 Generated with Claude Code

konard · 2026-01-19T22:31:52Z

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Public pricing estimate: $7.365753 USD
Calculated by Anthropic: $5.103654 USD
Difference: $-2.262099 (-30.71%)
📎 Log file uploaded as Gist (1390KB)
🔗 View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

Initial commit with task details

543d74e

Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #1081

konard self-assigned this Jan 11, 2026

konard and others added 4 commits January 11, 2026 05:29

chore: Add changeset for /stop and /start commands (minor release)

5aa82f5

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

konard changed the title ~~[WIP] /stop command~~ feat: Add /stop and /start commands for telegram bot (Issue #1081) Jan 11, 2026

konard marked this pull request as ready for review January 11, 2026 04:30

konard and others added 3 commits January 11, 2026 05:33

fix: Format changeset file with prettier

e8fb890

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Revert "Initial commit with task details"

3ffbaa5

This reverts commit 543d74e.

konard marked this pull request as draft January 19, 2026 22:17

konard and others added 2 commits January 19, 2026 23:21

konard marked this pull request as ready for review January 19, 2026 22:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: Add /stop and /start commands for telegram bot (Issue #1081) #1111

feat: Add /stop and /start commands for telegram bot (Issue #1081) #1111

Uh oh!

konard commented Jan 11, 2026 •

edited

Loading

Uh oh!

konard commented Jan 11, 2026

Uh oh!

konard commented Jan 19, 2026

Uh oh!

konard commented Jan 19, 2026

Uh oh!

konard commented Jan 19, 2026

Uh oh!

konard commented Jan 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

feat: Add /stop and /start commands for telegram bot (Issue #1081) #1111

Are you sure you want to change the base?

feat: Add /stop and /start commands for telegram bot (Issue #1081) #1111

Uh oh!

Conversation

konard commented Jan 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Implementation Details

Test Plan

Uh oh!

konard commented Jan 11, 2026

⚠️ Solution Draft Finished with Errors

📎 Log file uploaded as Gist (1505KB) 🔗 View complete solution draft log

Uh oh!

konard commented Jan 19, 2026

Uh oh!

konard commented Jan 19, 2026

Uh oh!

konard commented Jan 19, 2026

✅ Resolved

Merge conflicts resolved

Optional reason support for /stop command

Code quality

Example usage

Uh oh!

konard commented Jan 19, 2026

🤖 Solution Draft Log

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

konard commented Jan 11, 2026 •

edited

Loading

📎 Log file uploaded as Gist (1505KB)
🔗 View complete solution draft log

Optional reason support for `/stop` command