pinecall supervise

pinecall supervise <call>

$ pinecall supervise call_daab0b5d567c49968adc52e8d44c248c
call_daab0b5d567c49968adc52e8d44c248c · the audio of a live call is the console, which has a room — `pinecall start` prints its URL; this is the transcript and the desk
> s Hello from the desk, I am taking over for a moment.
> w
not a move. w · s · t · x · e · q
> q

The call's transcript as it happens, and one line to move on it:

w <text>    whisper to the agent — the caller never hears it
s <text>    say it to the caller, in the agent's voice, verbatim
t           take the line: the agent stops speaking and you are on it
x           give it back
e [reason]  end the call
q           leave the desk; the call goes on

Every move lands in the caller's own log as its own supervisor.* entry with a seq, so what a human did to a call is read the same way as what the agent did. The audio of a live call is the console's Live screen, which has a room; this is the transcript and the desk.

A desk opens on a call that is happening: one that has ended, and an id this gateway has no log for, are refused before the prompt — what a finished call was is pinecall sessions show.

An assistant has the same desk as the MCP's supervise tool (Supervising a live call).

It takes its moves from a pipe too, one per line, which is how a script moves a call: printf 't\ns Putting you through to the front desk.\nq\n' | pinecall supervise <call>. Through a pipe there is no prompt drawn, and the desk leaves when the lines run out.