Live View
Watch your agents' conversations in real time and step in when needed.
Live View is Vigilator's real-time window into your agents. While interrupts capture the moments an agent stops and asks for a decision, Live View covers everything in between: the conversation itself, as it happens. Operators watch transcripts grow live, keep an eye on several agents at once, and act the moment something looks off.
Sessions
The unit of Live View is a session - one run of an agent. Your agent registers a session through the API (or the relevant SDK) when a run starts, streams its conversation messages as it goes, and ends the session when the run completes. Sessions are standalone: they are not linked to interrupts, so you can monitor agents that never raise one.
Each session has a status:
| Status | Meaning |
|---|---|
| Active | The agent is running and has sent a message recently. |
| Quiet | The session is still open but nothing has arrived for a couple of minutes - the agent may be doing slow work, or may have crashed without ending its session. |
| Ended | The run completed (or the session was disconnected). |
A session that stays quiet is force-ended automatically after your organisation's configured session timeout, so crashed agents don't linger in the queue forever. Ended sessions remain browsable for 24 hours before leaving the list.
Ending is one-way however it happens - by the agent finishing, a watcher disconnecting, or the timeout sweep - and an ended session can never be reopened. Escalated sessions are the one exception to the 24-hour rule: they stay in the escalated queue until reviewed, however long ago they ended.
The dashboard
Live View splits into a session rail and a transcript pane. The rail lists sessions with their status, time since last activity, message count, and assignee; picking a card opens its transcript. The transcript renders the conversation as chat bubbles - the human on the right, the agent on the left, with tool calls shown as chips - and follows new messages as they stream in.
The rail can be scoped to:
- Assigned to me - live sessions assigned to you (the default).
- Live sessions - every active and quiet session in the organisation.
- Ended sessions - sessions that ended in the last 24 hours.
- Escalated queue - the review queue, visible to members who hold the manager review permission.
Multi-view lets one operator watch up to four sessions side by side - useful when you're responsible for a handful of agents at once.
Acting on a session
Watching is only half the point; Live View also gives operators levers:
- Assign a session to a member, so it's clear who is responsible for watching it and it shows up in their Assigned to me scope.
- Escalate a session to the escalated queue when it needs a manager's eyes. Escalation is one-way and only adds visibility - the session keeps running, and escalated sessions stay in the queue even after they end.
- Trigger a custom action. Custom actions are buttons you define per organisation (under Integrations → Live View) that fire a
session.actionwebhook event when pressed. - Disconnect a session - force-end it from the dashboard. Tracking stops immediately, the session cannot be reopened, and the
session.endedwebhook event carriesreason: "manual"so you can tell it was cut off rather than finishing on its own.
Session lifecycle events (session.started, session.ended, session.action) are delivered through the same webhook endpoints as interrupt events.
Permissions
Each lever is grantable separately through access control, so a role can watch without being able to touch:
| Permission | What it allows |
|---|---|
liveView.view | Open Live View and watch transcripts |
liveView.intervene | Assign and disconnect sessions |
liveView.trigger | Fire custom actions |
liveView.escalate | Raise a session to the escalated queue |
review.view | See the escalated queue |
Usage
Monitored time counts towards your organisation's agent hours, recorded when each session ends. Free organisations have a fair-use monthly allowance - once it's spent, new sessions are rejected until the allowance resets (existing sessions stay visible), while Pro organisations have a far larger fair-use limit, if yu don't think this limit will suffice for your organsiation please get in contact with us.