Skip to content

remote-sessions 0.3.0

Choose a tag to compare

@ramene ramene released this 11 Nov 23:53
03ad3a5
  • Open source: the control room (control) and attach --tui are now open, MIT, like the rest of this repo. There is no gate and no paid tier for them; the README has a new "Control room" section with the commands, the keys and four frames (docs/images), and crates/sessions-tui/examples/mock_frames.rs prints those frames from the real code.
  • sessions-tui: a small panel interface (RoomPanel, PanelSpec, PanelRow, PanelSnapshot). The room draws Remote Control and Cloud, plus any panels the host program gives it; a panel is shown only after its first read answers. Sel::Panel(index, id) and RoomMsg::Panel(index, snapshot) carry them; RoomBackend::panels() / panel(k) read them. The public build gives none.
  • /remote-room (open-room): inside cmux it splits with cmux new-split right --command (detected by CMUX_SURFACE_ID / CMUX_WORKSPACE_ID and a cmux on PATH), else inside tmux with tmux split-window -h, else it prints the command. The JSON line names the mux. README: "Attach from tmux or cmux". Tests: tests/open_room.rs (stub cmux and tmux, no real split).
  • Docs: docs/getting-started.md: install (Homebrew or the plugin), login, first steps, the control room, tmux and cmux, and cloud-sessions, with a picture for each step (docs/images/install-*.svg, plugin-list.svg, remote-room-split.svg). README and README.zh-CN have a short "Getting started" section that links it.
  • Versions: remote-sessions-cli, remote-sessions-core and sessions-tui are 0.3.0 (sessions-tui was 0.1.0; its room API changed).
  • New: control is a styled, clickable, interactive control room over Remote Control sessions and cloud sessions: two bordered panels (Remote Control with a pause badge on sessions that wait on a permission prompt, and Cloud with title, repo, state, last activity and age), a panel for the selected session, a status line and a footer of actions. Arrow keys or a click select a row, Enter or a second click drops in (attach <id> --tui, or cloud-sessions watch <id>, in the same terminal), a / d approve or deny a waiting prompt after a y (never Enter), s sends a follow-up to a cloud session (the text goes on stdin), r refreshes, q, Esc, Ctrl-C or a click on the close button in the header leave. The wheel scrolls the panel under the pointer. Remote Control refreshes every 3 s and cloud every 10 s, each a single call; the newest event of a cloud session is read for the selected row only, one at a time. The terminal is restored on every exit path, NO_COLOR / --no-color / --ascii give a colorless ASCII look, narrow terminals drop columns, and below 30x9 it says so. control --once [--size WxH] prints one frame and exits; control --demo uses placeholder sessions. Cloud sessions raise no permission prompts, so there is no approve for them.
  • New: attach <session> --tui opens a full-screen terminal UI (new crate sessions-tui, MIT, ratatui + crossterm, threads and std::sync::mpsc, no async runtime). Transcript with message, tool-call and folded tool-result blocks, a prompt box, a one-row footer (session, host, mode, link, hints), and a permission modal (allow once, deny, deny with a reason). Keys: Enter sends, Shift/Alt-Enter newline, Esc interrupts the running turn, Tab cycles manual / accept-edits / plan (/mode reaches the rest), Ctrl-O folds and unfolds results, PgUp/PgDn scroll, Ctrl-C leaves WITHOUT stopping the session. Slash commands: /approve, /deny, /mode, /read, /interrupt, /mouse, /log, /help, /quit. NO_COLOR, --no-color and --ascii give a colorless ASCII look; narrow terminals drop footer segments. Plain attach is unchanged, and --tui without a terminal falls back to it.
  • Core: events::blocks(payload) returns tool_use, tool_result, thinking and control_request/response/cancel as structured items (parse_event is untouched); control::user_payload_as and Client::say_as send a user turn with a caller-chosen event uuid, so a UI can match the server's echo.