Agentic settings, Telegram channels and limits

Availability: Agentic automation, Telegram signal sources and model comparisons are gated features. They stay off until your plan, your account and the platform launch gates all allow them, and a gated tab may accept input while every save is refused. Your dashboard is the source of truth for what your account can actually use today.

Agentic settings live at Dashboard → Settings → Agentic. The page holds the account-wide defaults that an agentic bot freezes at the moment you arm it. Changing a value here never edits a bot that is already armed — it changes what the next arming will use.

What each tab controls

Before you start

1. A plan that includes agentic automation, and the agentic feature enabled for your account.
2. A connected exchange with trade permission and no withdrawal permission. See Connect an exchange.
3. At least one stored AI provider key. Every analysis is billed to that provider account, not to BotTradesForYou.
4. An agentic bot. Strategy, copy and agentic modes are mutually exclusive, so an agentic bot is always a dedicated bot.
5. Saved trading defaults. Open the Trading Defaults tab and save once. Until a saved version exists, binding a channel to a bot is refused.

Add a Telegram channel

The Telegram tab reads channels through your own Telegram account, not through a bot token. It joins nothing and posts nothing — it only reads what your account can already see.

1. Link your Telegram account

Register an application on Telegram's own developer portal at my.telegram.org to obtain an API ID and an API hash, then enter both in the Telegram tab and pick a login method.

• QR code — open Telegram, go to Settings → Devices → Link Desktop Device, and scan the code shown. This is the same device-link flow you would use for Telegram Desktop.
• Phone and login code — enter your number in international format, then the code Telegram sends you. If your account has two-factor protection, you are asked for that password next.

Your API ID and API hash are stored encrypted. Login codes, passwords and session data are never shown back to you and never appear in History. One Telegram account can be linked per BotTradesForYou account.

2. Join the channel in Telegram first

Your account has to already be a member of the channel. Open the channel in your own Telegram app and join it before adding it here.

3. Add the channel link

Paste the channel into Telegram channel link and select Add channel. Three forms are accepted:

• A public link such as https://t.me/examplechannel
• A bare handle such as @examplechannel or examplechannel
• A numeric channel id beginning with -100

Private invite links are not accepted. Links of the form https://t.me/+AbCdEf or https://t.me/joinchat/AbCdEf are rejected, because they are join requests rather than references to a channel your account already reads. For a private channel, join it in Telegram first and then add it by its numeric id.

The target has to be a broadcast channel that your account belongs to. A direct chat, a plain group, or a channel you have not joined is refused.

4. Bind a bot and arm it

Under each channel, Bots following this channel lists your eligible agentic bots. Select one and choose Follow with selected bot.

A new binding is always created inactive and shows as pending_not_armed. It becomes armed only after you rearm that bot — redraft its mandate, review the fresh consent summary, and confirm arming. Arming re-checks that the bindings still match what the mandate froze, so a binding added after the last arming is ignored until the next one.

Signals are only acted on when the bot itself is running, the binding is armed, and the channel is not paused.

What sends a binding back to pending

Any of these deactivates the bindings on a source and requires a fresh arming:

• Pausing the channel
• Submitting new permission evidence for the channel
• Revoking AI permission for the channel
• Disconnecting the Telegram account

Queued events for that source are cancelled at the same time.

The activation baseline

Only messages that arrive after a channel is added are read. History is never backfilled.

The baseline also moves forward when you acknowledge a connection gap with Resume future messages, and when you pause a channel and then resume it. Messages sent during that window are discarded permanently, which is deliberate — it prevents a bot from waking up and acting on a backlog of stale entries.

AI permission is about data, not trading

Two different things happen to an incoming message.

Deterministic reading extracts symbol, side, entry, stop and targets using fixed pattern rules. It runs on every message, needs no permission, and sends nothing to an AI provider. This is what you see under Preview messages.

AI review sends channel content — text, and where relevant images or voice notes — to the AI provider you selected. That path is gated. To request it, submit a permission evidence URL and a description of the permission scope and recipients, then the request is reviewed. An approval names the exact provider and model that may receive the content, the scopes it covers, and an expiry no more than 90 days out.

Two consequences worth knowing:

• Submitting new evidence clears any existing approval and returns the channel to unverified. Only submit new evidence when you intend to replace the approval.
• AI permission governs who may receive channel content. It is not a trading gate. Your Trading Defaults Execution mode is what decides whether a read signal waits for your approval or is acted on directly. Keep execution mode on review or manual if you want to see each signal first.

You can pause a channel or revoke its AI permission at any time from the same panel.

Models and cost

The Models tab maps each role — research, text review, vision and transcription — to a provider and model you have a key for. Automated cycles carry no platform analysis quota, but "no quota" does not mean free: every attempt, including fallbacks between models, is billed by your provider directly. Review each provider's pricing, retention and privacy terms before selecting it.

Trading defaults

These values are frozen into the next mandate you arm:

• Paper or live. A live bot cannot arm a paper-mode snapshot, and a paper bot cannot arm a live one. See Paper trading and live trading.
• Signal source — Telegram, research, or both. If the source is anything other than research, at least one channel binding is required before the mandate can be drafted.
• Allocated capital and risk per position, within the platform's own hard ceilings. Your values can be tighter than the platform limits but never looser. Those ceilings are listed in Autonomous agentic bots.
• Execution mode — manual, review, or direct.
• Minimum net profit and AI allowance, so a trade must be expected to clear its own costs. Live defaults require both.

History and retention

History records settings changes and source events so you can see what changed and when. Raw message payloads are encrypted, kept for up to seven days so you can review them, then blanked. Authorization to fetch channel media expires within a day. Credentials, login codes and two-factor passwords are never recorded.

Limits

Troubleshooting

Related reading

• Autonomous agentic bots — selection, risk clamps and consent
• Paper trading and live trading — what changes when real funds are involved
• Connect an exchange — trade-only API keys