Skip to main content
Open Automations in the Cosmos sidebar to see every automation — an Expert and its triggers — in one table. The Event Log and Run History views live as sub-items under the same Automations group in the sidebar. This is home base for everything below.

​
Viewing Events

The events log is where you watch automations actually fire. Open Event Log under the Automations group in the sidebar. The table shows every event Cosmos has received across all sources, with the most recent first. From here you can:
  • Filter by source (GitHub, GitLab, Linear, Slack, Webhook, PagerDuty) using the source dropdown.
  • Open the Advanced Filter dialog to filter by event type (e.g. pull_request, Issue, app_mention).
  • Apply a JSONLogic payload filter (and a header filter) in the same dialog to narrow the list to matching events — a good way to sanity-check a filter against payloads Cosmos has already captured before pasting it into a trigger.
  • Click any row to open a details panel showing the source, event type, timestamp, and the full JSON payload that Cosmos received — plus any captured request headers.
This is the same surface backend triggers see, so what passes your filter here is what will fire your automation in production.

​
Per-Expert Run History

When you want to see what an individual Expert actually did in response to its events — not just what events arrived — open the automation row’s ⋯ menu on the Automations page and choose Run history. (Run History in the sidebar shows the same view across all automations; expanding an automation’s row shows its triggers, not its sessions.) The run-history table is locked to a single Expert and lists the sessions that a trigger started for it — the runs that actually fired, not sessions you launched by hand. Each row links into the session itself, where the worker tree (if any) is visible in the right sidebar.

​
Pausing and Removing Triggers

Trigger changes happen on the Automations page — expand the automation’s row to see its triggers:
  • Pause — to stop an automation without losing its configuration, disable the trigger with its enable toggle. Disabled triggers keep their type, event type, and filter, and can be re-enabled any time.
  • Remove — delete the trigger. The Expert keeps its capabilities and tools; it just no longer wakes up on that event.
  • Auto-archive — each trigger has an Auto-archive sessions created by this trigger toggle. Leave it on for fire-and-forget automations; turn it off when you want trigger-launched sessions to stay visible after they go idle.
Scheduled triggers run in singleton mode: if the next fire arrives while the previous run is still executing, that fire is skipped — runs are not queued, and missed fires are not backfilled. See Schedules.

​
See Also