Public: anyone can read this; the crew can change it.

Sessions you can see, resume and stop; idle ones stop themselves; a nice environment from the first keystroke #10457

Closed trevatoowner opened this 1d ago

trevatoowner opened this 1d ago

Sessions are things you can see, resume and stop, and nothing runs for no reason. The owner tried a machine and the sandbox game's terminal (its tty). He left one session without exiting, and it still says it's running: "I should be able to manage these or resume them or something. Right now I feel like I'm consuming resources for no reason." He also said: "the environment could be configured better for the user to make the experience nice."

The code: src/web/pages/machines.ts, the app tty in src/apps/manifest.ts and src/apps/contain.ts.

Done when:

One list of his sessions. Machines, app terminals and shells, on his account (and in the command palette). One line each: what it is, where, started, last input, CPU and memory now. Actions are Resume (reattach exactly where it was, with its scrollback), Stop, and Stop all idle.
Idle stops itself. A session with no input and no output for a set time (default 30 min, one knob) is stopped. Its scrollback and working directory are kept, so Resume brings it back. A session that's actually running something (a build, a test) isn't idle.
Leaving is not losing. Closing the tab detaches; it doesn't kill. The page says "detached, stops at 00:47 unless you come back", and coming back to the same page reattaches.
A nice environment from the first keystroke.

- The repo is checked out and its tools are installed (bun, git, the app's own tty command). - The prompt shows the repo and branch, history persists, and there are sensible shell defaults. - His dotfiles from a repo he names are applied if he's set one. - A one-line greeting says what this session is and how to leave.

Tests. Idle stop and resume, detach on tab close, and the list showing real usage.

the crew's run was interrupted: restart, resumes on the next pass — cancelled 1d ago

trevatoowner commented 1d ago

Parked by the crew: the check stayed red through 2 automatic tries (pull #10462 closed; its branch mason/10457-sessions-you-can-see-resume-and-stop-idl at 766b7057196a keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

trevatoowner commented 1d ago

Parked by the crew: the check stayed red through 2 automatic tries (pull #10490 closed; its branch scout/10457-sessions-you-can-see-resume-and-stop-idl at 307ac88f036a keeps the work so far).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

the check stayed red through 2 automatic tries (pull #10462 closed; its branch mason/10457-sessions-you-can-see-resume-and-stop-idl at 766b7057196a keeps the work so far)
the check stayed red through 2 automatic tries (pull #10490 closed; its branch scout/10457-sessions-you-can-see-resume-and-stop-idl at 307ac88f036a keeps the work so far)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

atlascrew commented 1d ago

Split by the planner. Both tries tried to land the whole ask in one pull, and both checks stayed red. Machine shells already stop after 30 minutes with no keystroke and rejoin on reload (src/machines/shell.ts), so what is left is split into one-pull pieces:

#10543: output counts as activity, and the idle stop is a setting
#10544: the Shells list on your account and in MCP
#10545: Stop, and Stop all idle (after #10544)
#10546: a detached shell shows its stop time and resumes (after #10543)
#10547: greeting, prompt with repository and branch, history that persists
#10548: dotfiles from a repository you name (after #10547)
#10549: app terminals in the same list, stoppable (after #10545)

The parked branches mason/10457-… and scout/10457-… hold earlier work that builders may reuse.