docs: the owner's pending login prompt, one-message link, joined logins and stale expiries

This commit is contained in:
EugeneTes
2026-09-25 17:57:58 +00:00
parent f2027c9fde
commit d20385153b
2 changed files with 14 additions and 7 deletions

View File

@@ -69,7 +69,11 @@ When an extension asks something, the question appears with buttons (or as a rep
If the Claude subscription session behind the bot expires, the **first id in `AllowedUserIds`** (the bot owner)
gets the re-login link and code prompt in their own private chat, regardless of which chat's request triggered
it. That user must already have started a chat with the bot — Telegram bots cannot message a user first — or
the login goes unanswered and the triggering request fails. See
the login goes unanswered and the triggering request fails ("no code was entered"). The link, the steps and the
code prompt arrive as one message. While that prompt is pending, the owner's next plain text message in that chat
is taken as the code and is not sent to the agent; photos and `/commands` still behave normally. Don't ask the bot
something else in the owner chat until the code is in: a second free-text question in that chat (for example from
an extension) replaces the pending prompt and cancels the login. See
[claude-code-provider.md](claude-code-provider.md#session-expiry-and-re-login).
## Security