Skip to content

Releases

remote-sessions 0.3.3

Choose a tag to compare

@ramene ramene released this 17 Nov 11:42
e4feb27
  • Fix: the Claude Code CLI upgrade stopped exporting $TMUX to plugin command subshells, which broke pane docking; detect the attached tmux client instead. /remote-room (open-room) found no $TMUX, said split:false inside tmux, and printed the command. The tmux branch now asks tmux list-clients and docks beside the most recently active attached client (not the first one, which may be a worker or deploy pane). The cmux branch is unchanged and still first; the final fallback is unchanged.
  • The tmux split is 45% of the window width (it was 50%).
  • Fix (s576): inside a tmux pane ($TMUX_PANE set) the room splits beside THAT pane, the one it was started from. The 0.3.3 first cut ignored $TMUX_PANE and split beside the most recently active attached client's session, which could be another window. Without $TMUX_PANE the attached-client rule above still applies.
  • Fix (s576): when a right column already holds a pane (the operator deck, or an earlier room), the room stacks under its top pane, so two panes stack on the right and no third column is added.
  • Already on main, now in this release: the s554 clean-start commits (crates/remote-sessions-cli/tests/clean_env.rs: a clean start lists every tool with all four hints) and the s554 Dockerfile and server.json entry for MCP registries.
  • New (s576 addendum): the MCP registry image. server.json moves to the 2025-12-11 schema (registryType; the obsolete package version is dropped), its image is ghcr.io/ramene/remote-sessions:0.3.3. The Dockerfile copies the CA bundle from its build stage (no apt step in the runtime image) and carries the labels io.modelcontextprotocol.server.name and org.opencontainers.image.source. New .github/workflows/ghcr.yml publishes that image (:0.3.3 and :latest) when a remote-sessions-v* tag is pushed. server.json validates against the 2025-12-11 schema with 0 errors.

remote-sessions 0.3.2

Choose a tag to compare

@ramene ramene released this 12 Nov 01:04
43778fc
  • Fix: the control room shows every account session and the Routines by default (the 0.3.0/0.3.1 /remote-room showed only tracked sessions). Fixes #1. /remote-room and remote-sessions control now need no flag: when cloud-sessions can read your account, the Cloud panel shows every session of your claude.ai account (name, repo, state, age) and the Routines with their newest runs. If the account list fails, the panel shows the sessions tracked on this machine and ONE line that says why and how to fix it (cloud-sessions auth use-claude-login). New: --tracked (or REMOTE_SESSIONS_CLOUD_ALL=0) for the old tracked-only view, --no-routines (or REMOTE_SESSIONS_ROUTINES=0) to hide the Routines. --all and --routines are still accepted.
  • Fix: a session that is tracked here and is also in the account list is one row with the account's title; the same session tracked twice (cse_ and session_ forms) is one row. A session without a title shows the short form of its id (session_01AbCdEf…), not "(untitled)".
  • New: the first run guides you. Each panel says what is missing, in one line with the exact command: cloud-sessions not installed (brew install ramene/tap/cloud-sessions), the Claude Code login not allowed yet (cloud-sessions auth use-claude-login, typed yes at a terminal), an account with no session (claude.ai/code or cloud-sessions start), no Remote Control session here (claude remote-control --name box, remote-sessions serve --name box, --host a,b or ~/.config/remote-sessions/hosts). With nothing to read, the room needs no login to say so. README "First run".
  • New: your account's Remote Control sessions that are connected on other machines (environment_kind bridge, connection_status connected, not archived, in the account list) are rows of the Remote Control panel with the host account, without ssh. The account list does not name the machine. Drop-in, approve and deny work by session id. One account list serves both panels.
  • cloud-sessions 0.2.2 (list --unofficial) and a cloud-sessions whose list carries the account list (no --unofficial) both work. --tracked ignores an account list in list.
  • Fix: /sessions ran remote-sessions sessions, a command that does not exist. It now prints one frame of the control room (control --once).
  • Fix: the room said Enter "watch" (cloud) and "attach" (Remote Control), but Enter opens the live, two-way chat with the session. One term in both panels now: the footer says Enter/click open chat, the Selected panel says Enter open the chat (two-way: type and press Enter to send, Esc back), and the cloud chat screen says live chat. cloud-sessions watch <id> is only the fallback in an error line, labeled read only: cloud-sessions watch <id>.
  • Fix: a long Cloud list no longer squeezes the Remote Control panel to one row: a list that fits in half the height gets all its rows (test a_long_cloud_list_leaves_every_remote_control_row_visible).
  • Fix: when this machine's process list cannot be read and the account has Remote Control sessions elsewhere, the panel shows one error row for this machine and the account rows under it (before: only the error).
  • cloud-sessions 0.2.3 reads every page of the account in plain list. When a reply shows 0.2.3 or later (it has view), the room's tracked lookups (the --tracked view, the fallback, the chat header) use list --tracked, so one lookup does not fetch every page. With 0.2.2 they use plain list.
  • Tests: control_room.rs (default = account list + routines, --tracked, the fallback line and the login line, one row with the account title, an empty account, the account Remote Control rows, the first run in both panels, cloud-sessions without --unofficial, list --tracked with 0.2.3, the open-chat wording in both panels, the account rows when ps fails); sessions-tui snapshot room_empty_cloud_absent_80x16.
  • Versions: remote-sessions-cli, remote-sessions-core and sessions-tui are 0.3.2; the plugin is 0.3.2.

remote-sessions 0.3.1

Choose a tag to compare

@ramene ramene released this 12 Nov 00:27
1b2f4da
  • Fix: <command> --help and <command> -h work for every command. Before, control --help printed {"error":"Unknown option --help.","ok":false} and exited 1, and control -h started the room. Now the help of a command shows its usage lines (from the top-level help), its options and, for control and attach, its keys, and exits 0. The command does not run.
  • New: help <command> shows the same text. help, --help and -h show the top-level help, which now has a help line. help <name> for a name that is not a command is an error (exit 1).
  • Unchanged: an unknown option still fails with Unknown option --<name>. (exit 1). A --help or -h that is the value of an option (send <session> --message --help) is text, not a help request.
  • Tests: tests/help.rs has one test per command (--help, -h and help <command>: exit 0, the same text, the command name in it), the options and keys of control, unknown options, and a check that each option in the usage has a help text.
  • Security: through MCP, remote_approve and remote_deny now do nothing by default. They return the exact command for the user to run (remote-sessions approve <session> --request <id>, /remote-approve, or a / d in control). A model cannot change the environment of the MCP server that already runs, so it cannot answer a permission prompt by itself. To let the MCP tools act, set REMOTE_SESSIONS_MCP_APPROVE=1 in the environment that starts Claude Code. The CLI approve and deny, /remote-approve and the control room are unchanged. Tests: tests/mcp_tools.rs (off for unset, 0, true, yes and empty, with no token read; on only with 1).
  • Security: the login token goes only to https://api.anthropic.com. REMOTE_SESSIONS_API now accepts only that address, or plain http to a loopback test server; before, any https address was accepted. Test: the_token_goes_only_to_api_anthropic_com (remote-sessions-core, src/api.rs).
  • New: several machines in the control room and in list. The Remote Control panel lists this machine (always, labeled with its short host name) and the machines of --host a,b (comma list, repeatable), REMOTE_SESSIONS_HOSTS and ~/.config/remote-sessions/hosts (one ssh host per line, # comments), merged in that order, each once. Each machine is listed with the list --host call (ssh -n -o BatchMode=yes -o ConnectTimeout=5), one thread per machine, stopped after 8 s; a machine that fails gets its own row (vm-1 ssh timed out) and never hides the others. Rows get a host column, and the panel title counts the sessions of each machine. Drop-in, approve, deny, read and say use the session API by claude.ai id, so they work for any machine; stop still needs --host (a signal over ssh). list (CLI and MCP remote_list) takes the same sources and gives each worker a host (one --host keeps the old output). /remote-room passes REMOTE_SESSIONS_HOSTS into a tmux split.
  • Security: an ssh host name is an ssh config name or a host name (letters, digits, ., _, -; user@ allowed); a leading - (-oProxyCommand=...), spaces and other characters are refused before ssh runs. Before, : and [] were also accepted. Tests: tests/hosts.rs (a stub ssh on PATH with two machines that answer and one that times out; the three sources and their order; the room rows, host column and counts; the refusals), rc.rs (host_names_refuse_options_and_odd_characters, a_slow_command_is_stopped_at_the_limit), sessions-tui/tests/room.rs (several_hosts_get_a_host_column_counts_and_a_row_for_a_host_that_failed).
  • Docs: README "Security and trust": your login, the hosts in the code, the risks, and how to report a security problem. README.zh-CN has a short version.
  • Versions: remote-sessions-cli, remote-sessions-core and sessions-tui are 0.3.1; the plugin is 0.3.1.

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.

remote-sessions 0.2.3

Choose a tag to compare

@ramene ramene released this 11 Nov 23:19
d0c7058

remote-sessions 0.2.3

  • Linux: use the Claude Code login from ~/.claude/.credentials.json. Token order for events, read, pending, approve, deny, say, interrupt, mode, stream and attach: REMOTE_SESSIONS_TOKEN, then ~/.config/remote-sessions/token, then the macOS keychain login (macOS only), then claudeAiOauth.accessToken from $CLAUDE_CONFIG_DIR/.credentials.json (when CLAUDE_CONFIG_DIR is set) or ~/.claude/.credentials.json (all platforms). Before, Linux found no token although claude auth status said loggedIn: true (s461). The file is only read: an expired login (expiresAt in the past) is an error ("the Claude Code login has expired: run claude once to refresh it"), not a stale request. Bad JSON or a missing accessToken key gives a clear error. No error text carries a token.
  • Tests: tests/token.rs (valid, expired, missing key, bad JSON, missing file, file mode 0644 accepted, CLAUDE_CONFIG_DIR, and the precedence order).
  • MCP: every tool now declares a title and all four tool annotation hints as booleans (readOnlyHint, destructiveHint, idempotentHint, openWorldHint; MCP spec 2025-06-18). Changed values: remote_approve and remote_deny are destructive (an approved tool can change or delete files; a denied tool call cannot be redone); remote_list and remote_stop are open-world (with host they run over ssh).
  • Tests: tests/mcp_tools.rs has one test per MCP tool, by name: its hints and its argument checks (no network, no ssh, no signal).

remote-sessions 0.2.2

Choose a tag to compare

@ramene ramene released this 07 Nov 23:25
8a091be
  • 0.2.2: privacy: examples and defaults no longer name the authors machines or sessions; default recording host is localhost