Layout
Split pane. The sidebar on the left holds filters and the main pane scrolls the event stream. Each row shows a single role badge (User, Assistant, Tool, Search, System) and the event text. Scheduled fires get a small secondary tag so you can distinguish automation runs from user-initiated work. The feed pulls from every active instance at once. New events arrive in near real time without a refresh.Filters
- Time
- Verbose toggle
- Role
- Instances
A single dropdown picks the window. Presets: 5m, 15m, 30m, 1h, 6h, 24h, 7d, 30d, or All. A Custom range option reveals two date-time inputs for exact bounds.
What each row means
| Role | What fires it |
|---|---|
| User | Your messages from chat, channel messages, and automation prompts |
| Assistant | Replies from an agent (from Operator or from the instance’s agent) |
| Tool | Agent tool calls and their results |
| Search | Web search queries the agent issued |
| System | Runtime events: config sync, startup, cron fire, errors |
cron or hook tag alongside the User badge so it’s obvious the user wasn’t at the keyboard.
Using activity while you work
The feed is useful in a few concrete moments:- An automation fired overnight. Open Activity, filter to that agent, pick the last 24 hours, and scroll the run.
- A long chat is taking too long. Flip the verbose toggle on to watch the tool calls land in real time.
- Something’s broken. Filter to System and look for recent config sync or container errors.
- You want to audit. Pick a custom time range and export what you see.
Related docs
Automations
Events tagged
cron come from hereAgents
Whose messages you’re watching
Channels
Telegram and Discord messages land in the feed too