Docs

Safety

Dangerous actions and confirmation

Recognize actions that can lose data, change permissions, or repeat effects on Telegram before you confirm.

View Markdown

Just because an action is allowed does not mean you should run it. Before deleting, transferring ownership, or rerunning an old job, check the target, the scope of its effects, and whether you can undo it.

Actions that need extra care

Action What you need to know first
Delete a workspace You must enter its name to confirm. This action is only available to people in the app, not AI connections. There is a separate recovery flow, so it does not mean all data is permanently deleted immediately.
Remove an account Removes the account from the workspace, not from Telegram. The app may need to queue a sign-out job before removal completes.
Delete a group or channel Deletes it for everyone, rather than just hiding it from your Inbox.
Transfer ownership of a group or channel Only a person using the app can do this. The two-step verification password is entered for that execution.
Delete a machine A Hetzner machine may actually be destroyed; this does not just remove a row from a list.
Revoke a session or sign out May disconnect the account and require you to sign in again.
Change permissions or delete a member or AI connection May cut off access and stop related tasks.
Rerun an old job Creates a new job; its effects on Telegram may happen again.

Other risks include deleting topics and messages, revoking invite links, upgrading a group to a supergroup, banning members, deleting webhooks, and some changes to administrator permissions.

Some actions are sensitive only with a particular input, such as switching to Free, setting a public group link, or expanding a webhook's scope. Read the confirmation for that specific action.

User confirmation

Workspace permissions and Telegram permissions are separate layers. Even if you have management permissions in the app, Telegram may reject an action if the account lacks the corresponding permissions.

  1. Open the correct target in the app.
  2. Read the scope of the effects in the confirmation dialog.
  3. Enter the name or confirmation details if the app asks for them.
  4. Confirm only if you accept the consequences described.
  5. Check the job result instead of clicking again when you do not yet see a change.

Confirmation through REST and MCP

REST and MCP share the same operation registry and permission checks. AI connections have their own risk policies: allow, ask, or deny.

When confirmation is needed, the call returns confirmation_required, a summary, a confirm_token, and an expiration time. The v2 metadata specifies a validity period of 600 seconds.

The agent must present the exact action to you. Once you agree, the agent calls the same operation with the same input again, including the token. The token is bound to the connection, operation, and requested data. It cannot be used for another action and can only be used once. The agent must not approve on your behalf. The app also provides a way for you to approve or reject requests.

Human-only actions have no public operation endpoint for an agent to call. Transferring group ownership and deleting a workspace belong to this category.

Rerunning does not continue the old job

Redrive applies only to eligible failed or expired jobs. The app creates a new job, links it to the old one, and rechecks permissions, quotas, the queue, and the do not contact list. Repeating redrive for the same job returns the same new job rather than creating arbitrary extra copies. An unverified job must not be blindly resent.