Revision-safe deploys
Every push is revision-checked. If the cloud moved ahead - a teammate or another client deployed - GramCode resolves the gap safely instead of forcing over it.
A rejected push means the cloud and local project disagree. `tgcloud fetch` and `tgcloud pull` inspect and merge the remote revision; `--force` is reserved for the case where you are certain the local folder should win.
`tgcloud diff` shows what changed before you decide. The same loop applies when another client edited a handler from the phone through BotFather parity.
Revision checks
A stale local project cannot silently overwrite a newer deploy.
Fetch and pull
Merge another client's changes before pushing again.
Diff first
Inspect the gap, then decide whether force is actually warranted.
Explore more
Describe your next change.
The agent plans, writes, validates, and deploys it to Telegram.