Telegram via mtcute engine (the default Telegram MTProto engine)

What it is

Omniscio's Telegram integration talks to Telegram's MTProto user-account API (not the bot API), so you sign in with your real Telegram account. The client library that drives that connection is called the engine, and since the F002 go-live the mtcute engine (@mtcute/node) is the default. The legacy GramJS engine remains available as a reversible opt-out. See telegram-integration.md for the full setup, sign-in, and triage how-to — this page covers only the engine choice.

Where to find it

The engine picker is the engine <Select> under Settings → Channels → Telegram engine. It is a channel setting rather than a separate page, so it sits with the rest of the Telegram setup.

How it behaves

Choosing the engine

• Open Settings → Channels → Telegram engine (the engine <Select> in Channel settings).
• mtcute (default) — the maintained @mtcute/node engine (WASM AES-IGE). This is the actively developed, supported path.
• gramjs — the legacy, now-archived GramJS engine. Kept only as a reversible fallback if anything in your setup ever depended on it.

What switching engines means

Each engine owns its own session slot (telegramSession vs telegramMtcuteSession), so the two sessions never collide. Switching engines is therefore a one-time re-auth: you pick the engine, then sign in again under that engine. Your other engine's session slot is left untouched, so switching back is just as easy.

Note on the old feature toggle

telegram-mtcute was originally a gated preview; it is now shipped and the reveal toggle no longer gates anything. The registry entry is retained as shipped so older persisted configs parse cleanly — the engine is controlled entirely by the telegramEngine setting above.

Related

The full Telegram setup, sign-in and triage how-to is on Telegram integration. If you would rather drive Telegram as a bot than as your own user account, that is a different system entirely, covered on Telegram bot channel.