v0.3.3

Security

• A client allowed to delete messages in one private chat or basic group could also delete them in your other private chats and basic groups. Now a delete only works on messages in the chat it names; otherwise nothing is deleted.
• A client allowed to send files could send a file that another client had downloaded from a chat it has no access to. Files in the downloads folder can no longer be sent; to pass one on, forward the message.
• A client reading a reply to a message in another chat no longer sees that message's id.

Fixed

• The Docker image built from this repository failed to start, with the error "socket directory /sessions is group/other-accessible". It now starts.

v0.3.2

Fixed

• Logging out of an account in setup also removes the endpoints bound to it. They used to stay in the config and the applied policy, and a later login under the same session name revived them with their old API keys and scope. The session is removed only after the endpoint removal is applied.
• Endpoints whose session no longer exists appear in Configure endpoints, marked "session '…' not found", and can be deleted there; with no account left, the setup menu offers "Remove orphaned endpoints". The final summary lists them as a warning instead of reporting "Setup complete".

Changed

• A config with no endpoints is valid and grants no client any access, so the last endpoint can now be deleted.

v0.3.1

Fixed

• setup draws its menu from the top of the screen. Started in a terminal that already had output, it began on the row where the shell left the cursor, partway down an otherwise empty screen.

v0.3.0

Added

• stop stops the running service and returns once it has exited, without asking for the PIN; it never starts one to stop it.
• --version / -v prints the CLI version, and --help / -h prints usage to stdout with exit code 0. Neither starts the service.
• start and setup show the version of the running service and warn when it is not the installed one, with the way to switch.

Changed

• A service started by 0.2.0 must be stopped by hand once. It does not understand this CLI's start or stop. End it, then start again: kill "$(cut -d: -f1 ~/.secure-telegram-mcp/sessions/.daemon-running/owner)" (adjust the path if TELEGRAM_MCP_SESSION_DIR is set).
• An unknown command names itself and points at --help instead of printing the whole usage.

v0.2.0

Changed

• A PIN file must be owner-only. TELEGRAM_MCP_SESSION_PASSPHRASE_FILE now refuses a file that group or other users can read, naming its mode, instead of using it. docs/USAGE.md always asked for 0600; it is now enforced. If an upgrade stops unlocking, run chmod 600 on the file.

Fixed

• The anti-ban circuit breaker could never trip: its long-wait threshold (10 s) was above the longest back-off any bucket can produce (8 s). It now trips after three long back-offs and pauses every quota-bearing operation on that account for the cooldown, while other accounts keep working.
• A client without elicitation support now gets CONFIRMATION_REQUIRED for a protected write, as documented, without being prompted. A confirmation request that fails in transit still reports GATEWAY_UNAVAILABLE.
• The setup review screen lists rights changes on chats that stay in scope — for example read → read + write — instead of "no changes vs. saved config".
• The server reports the published package version in initialize; it was fixed at 0.1.0.