Alerts & Telegram

Current chart signals

Strategy entry alerts are opt-in for available selected research setups, following market and actual chart interval. Only research setups passing the availability screen can alert; losing/unknown IDs are rejected by both producer and delivery consumer. They require an observed transition to the immediately following candle, a qualifying completed decision candle, valid next-open levels, no overlapping simulated position, and fresh exchange data within five seconds of the new open. Forming, late/missed, historical, already-touched-barrier and startup/context-change signals do not alert. The opening reference includes assumed slippage and is not an actual fill. Show strategy levels controls drawing only; selected strategies can still alert with levels hidden.

High model agreement alerts use the qualified joint model’s one-hour horizon only. Agreement is max(directionProb, 1 − directionProb), the achieved weighted scenario mass on one side of the original input price, not trading success odds. The default threshold remains 90%, configurable from 60% to 99%; the median must agree with direction. Four-hour and 24-hour selections are exploratory and cannot trigger. Only the current five-minute input close qualifies. Startup and market/interval/threshold changes establish a baseline; later threshold crossings or reversals have a five-minute cooldown. Stale/unavailable output cannot trigger.

These signal types use in-app toasts, the session log and browser notifications only when permission was already granted. Their switches and threshold persist locally, with browser-local event-ID deduplication. They never call Telegram or another external delivery service. Checks stop with the terminal closed. Model updates can run for alerts even with forecast drawings hidden.

Rules and scope

Open the Settings dialog and select Alerts & Telegram to manage rules. Create rules for mark price, 24h change, funding (basis points), RSI14 on 15m or 1h candles. Conditions are above, below, crosses above or crosses below. Cross conditions record an initial baseline and fire only on a later transition; state conditions fire when true. A rule fires once and must be re-armed. Legacy token-bias and alignment rules remain readable, but are not offered as new signal presets.

Rules are browser-local, limited by the signed-in plan’s allowed markets. A headless engine keeps the same rules checking from the terminal. Binance is polled every 30 seconds while the terminal is mounted. Unavailable feeds cannot fire a rule. Closing the app or navigating elsewhere stops checks; there is no always-on server alert scheduler.

Delivery

In-app toasts are always available. Browser notifications require the user’s explicit browser permission. The recent trigger log lasts for the current mounted session; triggered rule state persists in this browser.

Telegram is optional. When the server operator configures a dedicated TELEGRAM_BOT_TOKEN, Settings can generate a one-use connection link that expires after ten minutes. Open it in Telegram and press Start, then verify in Settings. The server matches the unique code from a private chat; it never accepts an arbitrary destination chat ID. The verified destination is stored against the account in the existing SQLite database.

Existing manual threshold rules may forward through the server; current-chart strategy and model agreement signals remain local-only. Bot credentials never enter browser storage. Simultaneous triggers are combined in one message, limited to 1,500 characters, with at most one delivery per second per account. Delivery errors are shown as in-app messages. Disconnecting removes the destination. The connection does not make rule evaluation run while the app is closed. A dedicated bot without an active webhook is required for this pairing flow.