An app terminal you have open is in your sessions list and stops like a shell #10643

An open app terminal now shows up in your sessions list next to the machine shells, and you can stop it from the account page or MCP. I ran its new test file and the shell, TUI and MCP-size tests; all 21 pass, and the type check and gate are clean. I did not run runAppTty end to end. The new test drives the same registry with a real pty process, because standing up an app runtime in a test was too heavy.

• Registry: src/apps/tty_registry.ts holds each open app terminal with app, environment (preview or production), holder, start, last input and last output. runAppTty in src/apps/tty.ts registers a terminal once it starts and updates input and output times as bytes pass. SSH and the forge's UI both go through it.
• Listing: myShells now returns app terminals as rows with kind: "app" beside the machine rows, which every consumer reads.

- On the account page an app row's title is owner/name · slug · env and its meta line reads "App terminal · Started …". - In the sessions tool with kind: "shells" the rows carry kind: "app". - In the TUI screen an app row reads "app terminal, running".

• Stopping: stopShell and stopIdleShells now cover app terminals. Stop sends SIGHUP to the pty and its process group. Stop all idle ends the ones past half the idle limit, as it does for machine shells.
• Idle: a terminal with no input and no output for the existing shell idle setting stops itself. This applies to guest terminals too, though guests are listed to no one.
• Tests: test/app-tty-sessions.test.ts covers listing, Stop ending the process, Stop all idle, self-idle, and a guest's terminal. docs/features/my-shells.md has a short note.
• Not done: ended app terminals leave no row, since they aren't persisted (machine shells are, in machine_sessions). I added no new MCP tool, only kind: "app" on the existing rows and a short doc edit, and the MCP size test passes.
• Process: the pre-push hook wanted a "Try:" commit, so there is an empty one on the branch. I couldn't call keep_plan; it wasn't available to me.

To try it, run ssh into an app that has a tty, open /settings/shells, and press Stop on the "App terminal" row.

🤖 Generated with Claude Code

Closes #10549

An open app terminal now shows up in your sessions list next to the machine shells, and you can stop it from the account page or MCP. I ran its new test file and the shell, TUI and MCP-size tests; all 21 pass, and the type check and gate are clean. I did not run runAppTty end to end. The new test drives the same registry with a real pty process, because standing up an app runtime in a test was too heavy.

• Registry: src/apps/tty_registry.ts holds each open app terminal with app, environment (preview or production), holder, start, last input and last output. runAppTty in src/apps/tty.ts registers a terminal once it starts and updates input and output times as bytes pass. SSH and the forge's UI both go through it.
• Listing: myShells now returns app terminals as rows with kind: "app" beside the machine rows, which every consumer reads.

- On the account page an app row's title is owner/name · slug · env and its meta line reads "App terminal · Started …". - In the sessions tool with kind: "shells" the rows carry kind: "app". - In the TUI screen an app row reads "app terminal, running".

• Stopping: stopShell and stopIdleShells now cover app terminals. Stop sends SIGHUP to the pty and its process group. Stop all idle ends the ones past half the idle limit, as it does for machine shells.
• Idle: a terminal with no input and no output for the existing shell idle setting stops itself. This applies to guest terminals too, though guests are listed to no one.
• Tests: test/app-tty-sessions.test.ts covers listing, Stop ending the process, Stop all idle, self-idle, and a guest's terminal. docs/features/my-shells.md has a short note.
• Not done: ended app terminals leave no row, since they aren't persisted (machine shells are, in machine_sessions). I added no new MCP tool, only kind: "app" on the existing rows and a short doc edit, and the MCP size test passes.
• Process: the pre-push hook wanted a "Try:" commit, so there is an empty one on the branch. I couldn't call keep_plan; it wasn't available to me.

To try it, run ssh into an app that has a tty, open /settings/shells, and press Stop on the "App terminal" row.

🤖 Generated with Claude Code

The failing test was "Stop hangs up the pty and its process ends". I've fixed the cause and pushed. I haven't seen the forge's check on the new push yet.

Cause. An app terminal started without a cell runs under setsid -c, which only becomes the leader of its own process group a moment after the spawn. A Stop that arrived in that moment sent SIGHUP to a group that didn't exist yet. signalGroup swallows that error, so the hangup was lost and the process ran on until the test timed out at 60 s. The test opens a terminal and stops it straight away, which is why it hit this. It only happens sometimes.

Fix. In startTerminal (src/apps/tty.ts), the hangup for a terminal without a cell now also signals the program itself, not just its group. Terminals in a cell behave as before.

Checks. bun x tsc --noEmit is clean, and test/app-tty-sessions.test.ts passed three runs in a row (5 of 5 each). I didn't reproduce the original failure here, so the race is my reading of the log and the code, not something I saw fail.

I've fixed all five of @sentinel's points and pushed. tsc, gate.ts, design-lint.ts and the 65 tty and shell tests pass here, and the new tests passed three runs in a row. The forge's full check hasn't run on this push yet.

1. The real wiring is now tested. I moved the pty bridge out of runAppTty into serveTerminal in src/apps/tty.ts. It covers the pty, the host, the input and output stamps, the hangup when the host goes away, and held.close() in finally. runAppTty calls it with a register callback that opens the registry entry. The tests call the same serveTerminal with a fake host instead of rebuilding the wiring. Three of the new tests cover it:

- input and output stamps, then forgetting the terminal when the host hangs up; - the program exiting by itself; - a hangup straight after the start.

1. peers is gone from AppTtyEntry. App rows now report peers: 0, and the account page hides the Attached, CPU and Memory facts for them, since none apply to an app terminal.
2. The idle tests no longer depend on timing. "Stop all idle" and self-idle age the registry entries instead of sleeping, with a 10-minute limit. The guest test uses a 50 ms limit and only waits for the terminal to end, so there is no margin to lose.
3. Row tests added. In test/my-shells.test.ts, one test covers the shellLine app row and the account page row. It checks the "App terminal · Started" meta, the Stop form, and that no Attached fact appears.
4. Hangup race test added. It starts a terminal and hangs up at once, five times, and checks the process is gone each time.