Persistent Browser Terminal Sessions

Developers leave terminals running everywhere: a dev server on a laptop, a test watcher on a staging box, a build on a runner machine. When a laptop sleeps or an SSH connection drops, that work and its context are easy to lose, and nobody else can see what is still running. This concept imagines those terminals as persistent sessions that run under a multiplexer such as tmux on the agents you install on your own machines, so they survive reconnects and can be picked up again from any browser.

The Sessions list is designed as the fleet-wide inventory. A table shows each session's name with the command it runs, its type, its status, the agent and target it runs on, the vibe it belongs to and when it last changed. Filters narrow the list by status, type, vibe, agent and target, a Group by option organizes the results, and a search box finds sessions by name. Selecting several rows opens a bulk bar to stop, restart or terminate them together or export the list as CSV. A view switch offers terminal, grid and list layouts, with New Session and Reconnect actions beside it.

Opening a session leads to a live terminal in the browser. The illustration shows a test run streaming its results, with a status strip above the output and a Session Info panel that lists the session's type, process ID, agent, vibe, working directory, start time and whether it starts automatically. Controls to stop the running command, restart or terminate the session and adjust its settings sit beside the terminal, while a share link and an open-in-new-tab action lead on to collaboration.

Sessions tie the rest of VibeControls together: they run on registered agents, belong to vibes and are the starting point for sharing a terminal and pairing live with teammates.