The Cockpit

The Cockpit is your Gateway's fleet interface: the same sessions the Director drives on each of your machines - every session card, every terminal, every control - in a browser tab you can open from any machine. There is nothing to install: it is a web address, you sign in, and you are looking at your control room.

The same fleet, not a status page

The Cockpit is not a stripped-down dashboard. You can start new sessions, answer an agent that is waiting on you, redirect one that wandered, and stop one that should not be running - the controls you have at your desk, in a tab. If you can do it on the Director, the Cockpit is meant to let you do it from anywhere.

One place for every machine

If you run agents on more than one computer, the Cockpit is where they meet: every session on every machine you own shows up in one place, so you stop remoting into each box to check on it.

Signing in

Signing in does more than unlock the page: it enrols this browser as a device on your account. Every real screen needs that enrolment, and a browser that does not have it is sent to the sign-in screen and then back to whatever it was trying to open. A device you no longer use can be revoked later - see your devices.

How the Cockpit is laid out

Down the left is a rail of destinations, and it is the whole product: everything the Cockpit can do is one click down that list. The Cockpit opens on the Fleet Map, so the first thing you see is the whole fleet rather than an empty prompt.

Three of them are where the work happens, and they have pages of their own here:

• Sessions - the rail of every session in the fleet, each with a short session number, and the page for the one you pick. See also working in a session.
• Fleet Map - the whole fleet drawn as a map, with eight ways to group it.
• Assistant - a conversation with the whole fleet, tied to no session.

The rest of the rail is one entry per capability, and each is documented where that capability lives rather than twice:

• History - what was worked on over a range you pick, grouped by repository and day. The walkthrough is what did I get done this week.
• Directors - the registry of the Directors in the fleet, and one Director in detail. See machines and Directors.
• Schedule - work that runs on a timetable. See scheduled work.
• Workflows - the shapes of work your fleet knows how to run. See workflows.
• Skills - the capabilities your agents reach for, held on the Gateway. See skills.
• Dictionary - the words you want heard your way. See your dictionary.
• Voice Recorder and Transcription - recording and transcribing, and the health of it over time. See Voice.
• Network - how well this Gateway and its machines are reaching each other. See network and diagnostics.

Pinned to the bottom are the entries about you and this app rather than about the fleet: Account, Phone (the code and address for pairing a phone), Your Throttle, Settings, About, and Help - which is the one item that leaves the app, and lands here.

Where things actually run

The Cockpit is served by your Gateway - the hosted Gateway at its public web address, or a self-hosted one on your own machine. The sessions themselves run in the Director on each of your machines; the Gateway brings them together, and views - browser and phone - connect through it. Start a session from the Cockpit and it runs on whichever machine you picked, not in the browser and not on the Gateway.

Where to go next

• Answering agents remotely - the away-from-your-desk flow, step by step.
• DevThrottle on mobile - the same idea, in your pocket, with a silent dot on the app icon when a session needs you once you have turned notifications on.