Architecture

From one message to saved local work

Esha runs on your own laptop and keeps a plain, inspectable path from your Telegram chat down to every step and file on disk.

Pipeline

The six-part flow

Each stage has one clear job so work can pause, restart, or ask permission cleanly.

Telegram User chat Gateway Auth & queue Planner Small plan Steps Saved state Tools Local runners Result Files or approval
Stages highlight sequentially from left to right

1. Telegram

Takes your plain message in English, Hinglish, or Gujarati and sends back step progress, approval prompts, and finished files.

2. Gateway

Runs locally on your laptop, checks sender identity, redacts secrets, and places incoming work safely into the queue.

3. Planner

Breaks larger requests into concrete small steps with inputs, outputs, and safety levels before any tool runs.

4. Steps

Stores every completed checkpoint inside local SQLite storage so a restart or dropped connection picks up without losing work.

5. Tools

Runs focused adapters for Word, Excel, PowerPoint, PDF conversion, and workspace folders under timeouts and memory guards.

6. Result

Returns completed files to your chat and pauses on Telegram whenever an action asks to post externally or change existing files.