Automations & Auto-replies (auto-respond to messages) (part 2)
The second half of the Automations page: the auto-response badge taxonomy that names which automated path produced a message, the activity log's per-step breakdown, and the implementation map of the engines, stores and IPC.
On this page
What it is
This is part 2 of the Automations & Auto-replies (auto-respond to messages) page. It carries the auto-response badge taxonomy that names which automated path produced a system message, the per-step breakdown the activity log shows for v2 runs, and the implementation map of the engines, stores, watchers and IPC that execute both kinds of rule.
Where to find it
Automations and Auto-replies both live in the Automations virtual project in the Omniscio sidebar, next to Quick Replies, with each rule edited inline in its list row; Automations & Auto-replies (auto-respond to messages) walks that surface end to end, including the rule editor, the six auto-reply actions, the action chain, backtest and the sender-authentication rules. The badges and internals on this page are read from a session transcript or from the code paths named below.
How it behaves
The auto-response badge — which automated path replied
Every system-injected message — an outgoing operator message Omniscio produced on its own, rather than one you typed — carries a small auto-response badge inline. The badge names which of the eleven automated paths produced the message, so a glance at the transcript tells them apart:
| Badge label | What produced the message |
|---|---|
scheduled wake-up |
A ScheduleWakeup tool call fired after its delay elapsed |
auto-continue |
Omniscio nudged the agent to keep going after it paused mid-task |
rate-limit retry |
A rate-limit window cleared and the session auto-resumed |
auto-resume |
Omniscio recovered the session after a crash or a restart |
auto-reply |
A user-defined Away Mode / Auto-replies rule fired |
auto-approved |
The dev pipeline auto-approved a gate on your behalf |
auto re-check |
The waiting detector re-checked after the agent went quiet mid-wait |
Sent by Inbox Pilot (bot icon) |
Inbox Pilot's router chose and sent the reply |
Every label except Sent by Inbox Pilot uses the amber auto-response palette so user-driven and recovery flows read as one family; Sent by Inbox Pilot keeps its own surface-grey pill with a bot icon. Auto-response messages persisted before this taxonomy existed fall back to a bare amber auto pill. The waiting detector's other auto check-ins are registered kinds too, but render differently: the pre-inbox and inbox auto check-in show the ember ⏱ Checked in tag on the check-in message (see waiting-detector.md) instead of this badge, and the ambiguous-wait confirm probe stays hidden.
Two of these labels render as a visible user-message bubble rather than being hidden by default — auto-reply and auto-approved — because you opted into the automation that sent them, so the transcript reads like you replied yourself. (The mechanical recovery / continue / wake-up kinds stay hidden unless you turn on Show system messages.)
Hover any badge for a tooltip that explains why the system spoke. The tooltip is the kind's description plus an optional per-message reason — for example Auto-injected to continue the agent after a pause — Auto-continue 2/5 — agent stopped mid-task, or Auto-injected after a rate-limit cleared — account-switch trigger. Sent by Inbox Pilot additionally shows the decision id (— decision abc-123) so you can find the matching row in the AI Coaching decisions log. auto-reply keeps the richer rule tooltip — the matching condition and reply source, e.g. Auto-replied — keyword "subagent" — snippet "Standard reply".
Click is wired for the auto-reply badge only: it jumps straight to the rule in the Automations virtual project (under the Auto-replies category) with the editor expanded. If the rule has been deleted since it fired, the click shows an "Auto-run rule no longer exists" toast and stays on the message; if the lookup IPC fails, you get an error toast instead and no navigation happens. Every other badge is informational — a non-interactive label, not a button.
Outgoing channel replies (SMS, Slack, Telegram, Gmail) sent by Automations rules still show the bare "auto" badge with no attribution. That follow-up is tracked in 2026-04-26-automations-channel-reply-attribution-followup.md.
How it works: the eleven-kind taxonomy lives in one shared module — auto-response-metadata.ts — which exports the kind union, a descriptor table (badge label + tooltip text), and the resolveAutoResponseKind() / getAutoResponseReason() accessors. Each producer stamps its metadata as it writes to the session: { systemInjected: true, kind, reason } for the recovery / schedule / continue kinds, { source: 'ai-manager-respond', decisionId, reason } for Inbox Pilot, the richer { autoRule: { ruleId, conditionType, conditionValue (truncated to 80 chars), snippetLabel } } snapshot for auto-reply rules, or { kind: 'pipeline-approval', pipelineAutoAdvance: { gate } } for a dev-pipeline gate auto-approval — threaded through writeToStdin (or sendMessageToSession for non-Claude engines) → addOutput → SESSION_OUTPUT push event → conversation_messages.metadata. Which kinds render as a visible user bubble vs. stay hidden is decided by USER_AUTHORED_AUTO_RESPONSE_KINDS in real-conversation-turns.ts. The renderer's AutoResponseBadge.tsx resolves the kind through that module, picks the palette + label, formats the tooltip via auto-response-tooltip.ts, and — for auto-rule — calls AUTO_RUN_GET_RULES to verify the rule still exists before deep-linking through navigate-to-rule.ts (sets useSessionStore.activeProjectId = AUTOMATIONS_PROJECT_ID, switches the automations-category-store category to auto-replies, and writes pendingExpandRuleId so AutoRepliesListView.tsx expands the matching row once it mounts and rules finish loading).
What the activity log shows for v2 runs
The Activity Log & Statistics collapsible at the bottom of the Automations settings panel lists every recent automation run. Click a row to expand it. For runs produced by the v2 chain executor (rules whose engineVersion === 2), the expanded panel surfaces a per-step breakdown: each action's label (Archive / Notify / Auto Reply / …), any free-text detail the action returned (e.g. archived 3 threads), a dry-run badge when the step was rendered for backtest only, and a human-readable duration (45ms, 1.2s, 2m05s). Failed steps show a red ✗ glyph and the underlying error text is hosted in a tooltip on the row so it doesn't push the layout around. Legacy v1 runs keep the single-line outcome (Success / Error + actionError paragraph) — only v2 runs grow the per-step block.
Related
This page is the companion to Automations & Auto-replies (auto-respond to messages), which covers the feature itself: what the two systems are, where to find them, and how to configure a rule. quick-replies.md is the paired virtual project for the snippet library the reply action cites, automation-credentials.md holds the secrets the v2 actions load, dev-pipeline-panel.md can seed a starter set of workflow auto-replies, and waiting-detector.md owns the check-in tags that render instead of a badge.
Last verified 2026-09-28