Lab Shell — the same tower in your hand
Done: You know the shell is a private frame around Agent Console, you can name the four inbox buckets, and you know the phone shows that same inbox. This page does not deploy the private shell.
What it is trying to do
Lab Shell exists so a person can run the lab without sitting at the desktop Console. It is a thin frame around the same Agent Console: same inbox, same version chip, same four buckets. It does not grow a second bus, and it does not invent a fifth work pile.
The useful features are the frame and the inbox. On a desk, the chrome is a WebView around Console. On a phone, the chrome is thinner and the buckets stay the same. If Needs Build is aging on the desktop, it is aging on the phone.
You cannot stand the shell up from this page. There is no host and no install recipe here.
The frame around Console
The shell is chrome. Agent Console is the product inside it. The desktop WebView chrome itself was not captured, so this beat has an honest hole instead of a fake window.
The version chip
The chip is the same object as on Agent Console. Pair shell and Console on that number. If they disagree, you are looking at two different cuts.
The four-bucket inbox
Needs me, Needs Build, Running, and Sticky are the Console board, not a second product. The shell does not relabel them.
- Needs me — a person confirm.
- Needs Build — waiting on Build, with age so a stuck packet is visible.
- Running — specialist already in flight.
- Sticky — already acked. Must not look like new red work.
Phone versus desktop
The inbox is the feature that survives the smaller screen. The chrome gets thinner. A phone WebView shot is not on disk. Do not expect a second product on mobile.
Next
The Agent Console demo names the same buckets, wake as a control, and usage meters without the shell chrome.