AgentCue’s architecture follows patterns deliberately borrowed from systems we audited in July 2026:
POST /api/flows/preview carries the full definition — borrowed from Windmill’s preview API).flow_snapshot.json (the exact definition), steps.json (per-node status/args/result/duration), and events.jsonl (append-only log). Retry offers n8n’s dual semantics: original snapshot (reproducible) vs current saved version (with lineage: retry_of).approvals): pending → approved/denied/expired. Default is undecided; timeout is deny; first response wins across web and Telegram; responded_via + comment = audit trail.claude -p --resume sessions; the rescue tab relaunches them after a reboot.writefile is contained to an allowlisted root via resolve().relative_to(); fetch blocks loopback/private/link-local targets and refuses redirects; shell nodes refuse `` interpolation (upstream data must flow through files, not command strings).Known limits (by design, for now): single user, localhost only, polling not websockets, vanilla JS single-file frontend. The multi-user path (OIDC, RBAC, actor context, per-workspace secrets) is documented but deliberately not built until there is a second human user.