Live sessions
Watch and control a running AI Workbench session from the console or the phone, who may do which, and what is audited.
A live session is a conversation, research task, Team Work run or agent that is running on a person's own workbench, or on a node working for them. From the console or the phone, that person can watch it as it happens, send the next message, answer approvals, stop the current turn or end remote control. Other people can be allowed to watch.
The work stays on the machine. The session, its files and its rules remain on the workbench; your organisation keeps only the list of sessions each machine reports, relays the calls, and audits them.
Live sessions need AI Workbench 0.81 or later. Remote control is off for every session until its person turns it on at the workbench.
Where people see Live
- Home and My tasks show Live now: the person's own sessions, on every machine they use.
- A project's History shows the live sessions its members may watch.
- An approval that waits on a session open to remote control arrives on the phone as a notification. Its Open live link goes straight to that session.
Opening a session shows the Live page, which follows the conversation as it happens.
Who can watch and who can act
| Watch | Act | |
|---|---|---|
| The person the session belongs to | Yes | Yes |
| Everyone on the project, for Team Work | Yes | No |
| People a Chat or Research conversation is shared with (the project, or them by name) | Yes | No |
| Anyone else | No | No |
Acting means sending a message, answering an approval, interrupting a turn, stopping it, or ending remote control. Only the person the session belongs to can do these.
Approvals keep the usual risk rule. A person can answer approvals at levels 1 to 3 from the console or phone. Levels 4 and 5 still need an owner of the project, and the phone says "An owner must approve this".
Remote control
- It starts off. The person turns it on, session by session, at the workbench.
- It can be ended. The person ends it from the Live page, or with the workbench's kill switch, which ends remote control for every session at once.
- The desktop says so. While someone controls a session from elsewhere, the workbench shows "Being controlled from JP's phone" (or the console), so nobody is surprised by a message they did not type.
When the workbench is asleep
A session stays in the list while its machine is switched off, asleep or offline, but it cannot be watched or controlled. The Live page says so, for example "Not reachable, last seen 10 minutes ago". When the machine wakes, the session becomes live again, and nothing is lost on the machine in between.
What is audited
Every remote action is recorded in Audit, with the person, where it came from (the phone or the web), the machine, the session or conversation, and the run id:
remote.send,remote.interrupt,remote.approve,remote.denyandremote.stopfor each action;remote.session.offwhen remote control is ended (andremote.session.onfor a node).
The text of a message is never in the audit trail. The workbench also keeps its own records of turning remote control on and off, and they arrive with its audit upload. See Audit.
What an administrator can do
- Check that workbenches run AI Workbench 0.81 or later. Older ones never list sessions.
- Review Audit for
remote.events when you need to know who acted on a session and from where. - Leave the choice to turn remote control on with the person who owns the session. An administrator cannot turn it on for them.
For developers, the Live sessions endpoints list the calls behind the page.