Telegram Toolset is a privacy-first, browser-only workspace for advanced Telegram operations. The repository started as a deleted-messages manager and is now being productionized into a broader modular tool platform built around a shared multi-account auth pipeline.
The app runs entirely on-device. There is no backend, no tracking, and no server-side storage of Telegram data.
| Module | Description | Account Type |
|---|---|---|
| Account Info | View account details, capabilities, and session state | Any |
| Export Deleted Messages | Export deleted messages from chats where the user has the required rights | User |
| Backups | Manage saved exports, archived local backups, and recovery lifecycle actions | User |
| Resend Messages | Re-send exported content with formatting and batching controls | User |
| Scheduled Messages | View and manage scheduled messages across chats | User |
| LLM Context Export | Export chat history in assistant-friendly formats for external tools | User |
Account Info, Export Deleted Messages, Resend Messages, Scheduled Messages, and LLM Context Export are currently surfaced from the module registry in src/modules/index.ts. Backups is already part of the supported product surface, but today it is exposed as its own authenticated route/workspace rather than as a landing-page module card.
- Keep a single modular app shell rather than separate one-off apps.
- Keep the shared auth/session pipeline as reusable platform infrastructure.
- Keep
Scheduled MessagesandLLM Context Exportas first-class modules. - Keep the app client-side and privacy-first.
- Productionize the architecture instead of layering more logic onto oversized views and services.
The detailed roadmap lives in TODO.md.
Vue 3 + Vite + TypeScriptPiniafor shared stateVue Routerfor lazy-loaded module routesGramJSfor user MTProto flows- Telegram Bot HTTP API for bot validation flows
IndexedDBfor backups, media, export caches, encrypted account secrets, and recoverable account-owned archives with explicit claim/delete lifecycle actionsvue-i18nfor localizationVitest+Playwright+ GitHub Actions for quality gates
npm ci
npm run dev
npm run lint
npm run check:i18n
npm run type-check
npm run test:unit
npm run test:component
npm run test:e2e
npm run buildRead these files before making substantial changes:
- TODO.md for roadmap, priorities, and restart guidance
- AGENTS.md for design system rules, architecture notes, critical Telegram/browser lessons, and agent-facing repo guidance
Key contribution rules:
- Reuse the shared auth/session platform instead of duplicating login flows inside modules.
- Treat the module registry in
src/modules/index.tsas a first-class product surface. - Preserve the privacy model: no backend, no silent data export, no tracking.
- Keep UI changes aligned with the design system in
AGENTS.md.
- User accounts: API credentials from my.telegram.org
- Bots: Token from @BotFather
MIT