Repository navigation
feat(messages): cancel, edit and send now a scheduled message - #3139
Merged
Merged
Conversation
messages scheduled cancel <chat> <scheduled-id...>, messages scheduled edit <chat> <scheduled-id> [text] [--at-time] and messages scheduled send <chat> <scheduled-id...> (owner's NEED-2692 A). A scheduled message has ids of its own: messages edit on one failed with MESSAGE_ID_INVALID, and messages delete with the same number would have deleted an old, sent message. Each command checks every id against the chat's scheduled list before it writes. Cancel is journaled and asked as a delete (--allow-dangerous at ask), send as a send, edit as an edit, under messages.scheduled.cancel/.edit/.send. An edit always passes the time, the current one when only the text changes. The adapter side is the optional port group ScheduledChanges; the fake adapter implements it. The MCP search breaks a tie by the shorter command name, so "send message" still finds messages send first. cli-base 0.122.0 registers scheduled as a resource for cli-dev lint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour
force-pushed
the
feat/scheduled-actions
branch
from
November 19, 2026 04:18
3ee4e09 to
ea6cf22
Compare
This was referenced Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task
Owner's decision NEED-2692 A (2026-11-19): add cancel, edit (text and/or time) and send now for scheduled messages, released on npm.
Why
The owner had to cancel a scheduled group post by hand in the Telegram app. tg could schedule (
messages send --at-time) and list (messages scheduled <chat>), nothing else. A scheduled message has ids of its own:messages edit <chat> 3on one failed withMESSAGE_ID_INVALID, andmessages delete <chat> 3would have deleted the real, old group message #3.What
messages scheduled cancel <chat> <scheduled-id...>,messages scheduled edit <chat> <scheduled-id> [text] [--at-time <time>] [--md],messages scheduled send <chat> <scheduled-id...>, under the existingmessages scheduled <chat>(which still lists). The argument is named<scheduled-id>, and the help says the same number in the history is another message.messages deleteandmessages edithelp point to the scheduled commands.not_foundand namesmessages scheduled <chat>.schedule_dateto read the id as scheduled.--at-timealone moves it and reads no stdin; it is parsed by the samesendTimeasmessages send --at-time.messages.scheduled.cancel(journaled asdelete, in the--allow-dangerousset),messages.scheduled.edit(edit),messages.scheduled.send(message, counted per id). At most 10 ids at once, like delete.ScheduledChanges(cancelScheduled,editScheduled,sendScheduled); the kit fake implements it. max and wa get "this messenger cannot …" (wa has noscheduledgroup at all;lacksrefuses before connecting).scheduled_cancellation,scheduled_send; edit answersmessage_writewithscheduled_for.messages sendbeforemessages scheduled send.scheduledas a resource word (feat(standards): scheduled is a resource as well as a view cli-base#659), socli-dev lintpasses the group.Deviations from the brief
send-nowissend:cli-dev lintallows only vocabulary verbs (unknown-verb).messages deleteas the code has it today, not "ask +--yes":messages.deletedefaults toallow(owner, 2026-11-14) and its yes flag is--allow-dangerous. Cancel has the same: no question at the default level,--allow-dangerousatask. Agents may cancel (nobody else has seen the message); the profile levels govern.Testing
src/cli/messenger/messages-scheduled.test.ts: list still works; cancel by scheduled id, refusal of a sent message's id before any write, journal entry; ask level with--allow-dangerous, read-only refusal; edit keeps the time;--at-timeonly reads no stdin; empty edit refused; send now answers the new ids; refusal without the capability, and before connecting withlacks.🤖 Generated with Claude Code