Deploy to Telegram Serverless
A deploy is an atomic, revision-checked push of the project folder to Telegram Serverless - not a container build, a server provision, or a DNS change.
The platform mirrors the folder exactly: new modules appear, edited modules update, and local deletions remove the corresponding cloud modules. What you reviewed is what runs.
Code and schema changes are separate operations. `push` never applies migrations; `migrate` reviews them and asks for confirmation on anything destructive. Deployment credentials live in a trusted service, outside the agent's context.
Atomic pushes
One revision-checked operation mirrors the project folder.
No servers
Telegram Serverless provides the bot runtime and Mini App hosting.
Credential boundary
The agent requests a deploy; the deployment service owns the token.
Explore more
Describe your next change.
The agent plans, writes, validates, and deploys it to Telegram.