Cockpit
Answering agents remotely
3 min read
The point of the Cockpit is the moment you are not at your desk and an agent stops to ask a question. Instead of the work sitting idle until you get back, you open the board in whatever browser is in front of you, answer, and the agent keeps going. This page is that flow.
Answering from another machine
Open the Cockpit
From the Director, the Cockpit button in the toolbar opens the board in your default browser - use that the first time so you know the address. It is served by your Gateway, so the address is your machine, not a devthrottle.com page.Sign in
The Cockpit is yours, so it asks you to prove it. Sign in with your DevThrottle account; the session sticks in that browser afterwards.Find the card that needs you
The board reads exactly like the desktop: cards with status squares, and a counter of how many sessions are waiting on you. Click the waiting card.Answer in the prompt bar
Type the answer (or a course correction) into the prompt bar, exactly as you would at your desk. The agent picks it up and keeps working.
Screenshot coming soonAnswering a waiting agent from the Cockpit prompt bar in a browser
Reachability: same network first
Your browser has to be able to reach the Gateway machine. On the same network - home office laptop to the desktop upstairs - that just works. From further away, the supported route today is making your machine reachable yourself, for example with a VPN or an overlay network like Tailscale; reachability is your network's job, while the Gateway handles who is allowed in. Your traffic goes to your machine either way - DevThrottle does not relay it.
Tip
If what you really want is the answer-from-anywhere experience with a ping when an agent needs you, that is the mobile app - it pairs your phone to the Gateway once and then notifies you.
Note
Anything you start from the Cockpit runs on the Gateway machine, with the same steering controls - Stop, Interrupt, and the queue - available remotely.