Skip to content

refactor: rename /stop command to /cancel for clarity#145

Merged
royosherove merged 1 commit into
mainfrom
feat/rename-stop-to-cancel
May 16, 2026
Merged

refactor: rename /stop command to /cancel for clarity#145
royosherove merged 1 commit into
mainfrom
feat/rename-stop-to-cancel

Conversation

@royosherove
Copy link
Copy Markdown
Member

What

Renamed /stop/cancel across all codebase to clarify intent: abort in-flight agent work (not shutdown).

Changes

  • Commands: handleStophandleCancel, StopContextCancelContext
  • Gateway: Updated command registry trigger from '/stop' to '/cancel'
  • Telegram: Updated bot command menu registration (bot-commands.ts)
  • UI: Message text '⏹️ Stopped.' → '⏹️ Cancelled.'
  • Docs: Updated README, CHANGELOG, architecture.md, command-registry comments

Why

'/cancel' is semantically clearer:

  • 'stop' is ambiguous (could mean shutdown, pause, terminate, etc.)
  • 'cancel' explicitly means "abort in-flight work" (standard UX terminology)
  • Aligns with Telegram/web UI conventions

Test

  • ✅ All 591 tests passing
  • ✅ No regressions
  • ✅ Automated + architect reviews: all green

- Renamed `handleStop` → `handleCancel`, `StopContext` → `CancelContext`
- Updated command registry trigger from '/stop' to '/cancel'
- Updated UI feedback: '⏹️ Stopped.' → '⏹️ Cancelled.'
- Updated all references in gateway.ts, commands.ts, tests
- Updated README, CHANGELOG, and architecture docs
- Fixed stale /stop references in command-registry.ts and architecture.md doc comments

**Why:** 'cancel' is clearer intent (abort in-flight work) vs 'stop' (ambiguous, might imply shutdown).

All 591 tests passing.
@royosherove royosherove merged commit 7a05892 into main May 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant