Shift+Enter adds a line, and a session says what it is before it starts

[karngyan]

Three fixes, all in web/.

Shift+Enter sends a newline instead of the message

xterm.js encodes Enter as a bare carriage return whatever Shift is doing (case 13 of its key encoder) — faithful to the hardware, and useless in front of an agent CLI. Claude Code and Codex both read a bare CR as "send this", so in a browser terminal there was no way to put a second line in a prompt.

Shift+Enter now sends ESC CR. That is not a sequence flue invented: a line editor reads it as Alt+Enter, claude /terminal-setup writes exactly those two bytes into VS Code's keybindings.json for shift+enter, and iTerm2, Ghostty, WezTerm, Kitty, Warp and Windows Terminal already send it — which is what "Shift+Enter is natively supported" means in those tools.

It lives in the emulator rather than the view because the view cannot put bytes on the wire without reaching past the seam. term.input routes them through onData, so the key bar's latched Ctrl and the replay mute gate still apply. Ctrl+Shift+Enter is left alone — the view takes that one on the way down for focus mode.

Verified against a real pty, not only in jsdom: cat -v in a live session records ^[ and then the CR.

A session row opens in a tab of its own

The sessions list is what people come back to between sessions, and opening a terminal over it made the way back the browser's back button — which drops the terminal and its scrollback with it. The rows were already real anchors, so this is a target; the router hands the click straight to the browser once one is set.

The + in a terminal no longer goes via the dashboard

It pointed at /?cwd=, which is the sessions dashboard — so a session started from a terminal came up behind the whole list, page and shell and rows, for as long as the daemon took to answer.

There is a page for it now. /new takes the request in its address, spawns, applies the name and tags the moment there is an id to apply them to, and replaces itself with the terminal — one pill on the terminal's own ground, no chrome in between.

A page rather than a click handler because starting a session takes a round trip: spawn carries no id, the daemon invents one. A screen that spawned and then called window.open from the reply would be opening a popup from a continuation, which Safari refuses outright and Chrome refuses once the gesture has aged out. A link opens on the click itself. A blocked popup falls back to the current tab rather than to nothing at all.

And every way of asking goes through one dialog

spawn carries no metadata, so a name and a tag could only ever be applied after the session existed — which meant starting it, watching a terminal come up, going back to the list and renaming the row. Nobody does that, so sessions stayed called after whatever shell they ran.

The toolbar button, its machine menu, every group heading's +, and the terminal's own + now open one form: name, directory, machine, tags — prefilled from whatever the press implied, and all of it optional. Opening it and pressing Start is the old one-click behaviour exactly.

flue open's ?cwd= handover is untouched: it still spawns from the sessions screen, which is the one caller adopt has left.

Checks

• pnpm vitest run — 67 files, 1319 tests, green
• pnpm run lint — clean
• Driven end to end in a real browser against a dev daemon: Shift+Enter's bytes at the pty, the dialog on both screens, the address it builds, and the session that comes out of it with its name and tag attached.

🤖 Generated with Claude Code