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.

How the Cockpit is laid out

The Cockpit has two halves and a fleet-wide map:

• The session rail - the list down the left of every session in the fleet, each with a short session number, so you can find one and see which ones need you.
• Working in a session - the page on the right, with the terminal, chat, and voice views of the session and the controls to steer the agent.
• The Fleet Map - the whole fleet drawn as a map, grouped by machine, repository, or agent.

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 push notifications.