The human-in-the-loop, where you already are
Autonomous workflows still need a human at a few key moments — an ambiguous decision, a risky merge, a gate that genuinely needs judgment. The question is where that moment happens. Forge brings it to chat.
When a run escalates, you get a Telegram message with an inline keyboard: Retry the step, Resume the run, Approve and advance, or Terminate. Press a button and the workflow moves — no context switch, no dashboard, no waiting until you’re back at your desk. This is what keeps the operator’s attention scarce instead of constant.
Safe by construction
Acting on a workflow from a chat button is a real privileged action, so it’s locked down:
- Single-use action tokens. Each button is a TTL-bounded row, atomically consumed on press — idempotent, so a double-tap or a forwarded message can’t fire twice.
- A full auth chain. Telegram’s secret token header → an org-scoped service JWT → a server-side org-match check. Five gates before a press touches a run.
- Authorization per press. Every button validates that the presser is allowed to move this run.
Always current
Notifications don’t go stale. A scheduled reconciliation updates prior messages for a run when its state changes — dropping buttons that no longer apply and appending the outcome — so the controls in your chat always reflect reality. Manage channels, subscriptions, and the audit trail from the operator notification center.