bot-process-control
Bot Process Control
Where the Gmail Commander bot and scheduled digest run, how to tell whether they are healthy, and what must never be started on a workstation.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Where the processes live
Neither process runs on a workstation. Both run in a private Restate tenant on an always-on Mac mini, deployed from a private repository:
| Service | Role |
|---|---|
GmailBot |
Owns the Telegram getUpdates chain (one durable, self-re-arming poll) and dispatches each update |
GmailBotChat |
Runs one update through the grammY bot built by this plugin's buildBot(), in per-chat order |
GmailDigest |
Scheduled email digest to Telegram, several times a day (its own implementation, not this plugin's) |
GmailAuth |
Mints Gmail access tokens on demand from a refresh token held in the deployment's secret store |
Starting, stopping, restarting, deploying, reading logs, rotating secrets and OAuth re-consent are all done through that repository's runbook. This public skill intentionally carries no host names, deploy commands or credential paths for it. If you do not have access to that repository, stop and ask the operator.