Repository navigation
Releases
mars-ram 0.1.10
Released together with Android build 14 of the app. Build 14 still works with mars-ram 0.1.6 through 0.1.9 (MINIMUM_HOST_VERSION stays 0.1.6): its changes (agents first in the terminal switcher, workspace cards, the Home subagents mode and its preview, the reorganized Settings) read nothing new from the computer, so nothing about the host is required for them. Host 0.1.10 also works with build 13 and older builds, which see no difference.
Update in the computer's terminal (Linux, macOS or Windows), from 0.1.7:
mars-ram update
mars-ram doctor
From 0.1.8 on, mars-ram update runs mars-ram doctor itself; the second line does no harm. From 0.1.6 or older, in a normal (not administrator) terminal, one command per line:
pnpm add -g mars-ram@0.1.10
mars-ram install
The session bridge still speaks protocol 1.8, so Pi sessions that are already running need no /reload.
Fixed
- On Windows, the «Siempre atento» link server now starts without a console window. Before, it opened a terminal window that came back after you closed it: closing it stopped the server, and the phone started it again. A link server that an older host already started keeps its window until it stops; the next time it starts, 0.1.10 starts it without one.
mars-ram 0.1.9
Released together with Android build 13 of the app. Build 13 still works with mars-ram 0.1.6, 0.1.7 and 0.1.8 (MINIMUM_HOST_VERSION stays 0.1.6): the only app change that reads something new from the computer is the subagents counter on Inicio, and it uses an optional subagents field of the session state that older hosts simply do not send, so the counter does not show and everything else works as before. Host 0.1.9 also works with build 12, which ignores that field.
Update in the computer's terminal (Linux, macOS or Windows), from 0.1.7:
mars-ram update
mars-ram doctor
From 0.1.8 on, mars-ram update runs mars-ram doctor itself; the second line does no harm. From 0.1.6 or older, in a normal (not administrator) terminal, one command per line:
pnpm add -g mars-ram@0.1.9
mars-ram install
The session bridge now speaks protocol 1.8. Pi sessions that are already running keep working with build 13, but report their subagents only after /reload (or a restart of the session).
New
- The session bridge reports the session's running Gentle Shell subagents (queued, running or waiting, and whether one is asking a question) in an optional
subagentsfield of the session state, at most 8 per session. It reads them from Gentle Agents in the same Pi process over Pi's event bus; finished subagents drop out. Only with Gentle Shell: a plain Pi session leaves the field out and behaves exactly as before. App build 13 shows them on Inicio as a counter on each session that opens the list.
mars-ram 0.1.8
Released together with Android build 12 of the app. Build 12 still works with mars-ram 0.1.6 and 0.1.7 (MINIMUM_HOST_VERSION stays 0.1.6): the only app change that reads something new from the computer is the switcher line for Herdr saved machines, and it uses an optional machines field of mars-ram herdr list that older hosts simply do not send, so the line does not show and everything else works as before. Host 0.1.8 also works with build 11, which ignores that field.
Update in the computer's terminal (Linux, macOS or Windows), from 0.1.7:
mars-ram update
mars-ram doctor
From 0.1.6 or older, in a normal (not administrator) terminal, one command per line:
pnpm add -g mars-ram@0.1.8
mars-ram install
The session bridge still speaks protocol 1.7, so Pi sessions that are already running need no /reload.
New
mars-ram updateends, after a successfulmars-ram installof the new version, by running that version'smars-ram doctorand printing one line that it ran (on Windows, in the new window where the update continues). Doctor warnings or problems never turn a successful update into a failure, and a failed update or install does not run it. The update runs the code of the version that starts it, so this shows from the update after 0.1.8: going from 0.1.7 to 0.1.8 withmars-ram updatedoes not run doctor, so runmars-ram doctoryourself afterwards.- Herdr saved machines: when the computer's Herdr has enabled saved SSH machines (
herdr machine list), every Herdr client there, including the one the phone's terminal starts, also shows those machines' workspaces. mars-ram explains it without changing Herdr's configuration:mars-ram doctorprints a warning naming the enabled machines and how to hide them (herdr machine disable <name>), andmars-ram herdr listadds an optionalmachinesfield with their names, which app build 12 shows in the workspace switcher as «Este Herdr también muestra: …» / «This Herdr also shows: …». A missing Herdr or a failingherdr machine listnever fails doctor or the list. - App build 12: a link from outside the app that opens a session's terminal asks «¿Abrir la terminal?» first, naming the computer; nothing opens a terminal or moves Herdr's focus on the computer before «Abrir», and «Cancelar» goes to Inicio. The app's own notification taps open directly as before. The network choice when adding a computer shows Tailscale and ZeroTier on equal footing, without «(recomendado)».
Fixes
- Windows without administrator:
mars-ram doctorsays thatadministrators_authorized_keysandsshd_configare readable only by administrators and asks to run doctor as administrator to check them, instead of «Paired SSH keys: unreadable; forwarding unknown» and a bare «Could not determine SSH TCP forwarding»;mars-ram pairsays that only administrators can read the SSH server's identity and to run it again in an administrator terminal, instead of «Is the SSH server installed?». A missing host key still means no SSH server.
mars-ram 0.1.7
Released together with Android build 11 of the app. Build 11 still works with mars-ram 0.1.6 (MINIMUM_HOST_VERSION stays 0.1.6), but only build 11 or later can scan the compact QR that 0.1.7 prints: update the app before or together with the computer.
Update in the computer's terminal (Linux, macOS or Windows), from 0.1.6 or older:
pnpm add -g mars-ram@0.1.7
mars-ram install
From 0.1.7 on, mars-ram update does it. The session bridge still speaks protocol 1.7, so Pi sessions that are already running need no /reload.
New
mars-ram updateupdates the computer side in one command: it updates the package with the package manager mars-ram was installed with (pnpm, npm or Bun) and runsmars-ram installof the new version, reporting the version it went from and to. It explains the usual failures instead of the raw error: pnpm's global bin directory not in PATH (pnpm setup, then a new terminal), the package manager not found; an administrator terminal on Windows is refused, and on Windows the update continues in a new window so the runningmars-ram.cmdis never replaced under cmd.exe. Installations from the curl or PowerShell script or a clone get the way to update them instead. The app's update notice showsmars-ram updatefor computers with 0.1.7 or later.mars-ram pairfinds the connected network on its own: Tailscale or ZeroTier. When both are connected it asks in the terminal which one the phone uses;--network tailscale|zerotierchooses without asking.mars-ram pair-ztstill works and meanspair --network zerotier. The QR offers do not change.mars-ram pairprints a much smaller QR: a compact version 3 offer carries the same information (address, MagicDNS name, SSH user and port, the full host key fingerprint and the full one-time code, expiry) as bytes instead of JSON. A typical Tailscale QR goes from 65×65 to 45×45 modules (69 columns × 35 lines to 49 × 25 in the terminal); a ZeroTier one to 41×41. The link keeps itsmars-ram://pair?p=…form, so the phone's camera still opens the app. Rollout: only an app build that reads version 3 can pair with it; an older app shows its invalid-code message («Este QR no es un código de vinculación válido para esta app. Mostrá uno nuevo en la computadora o actualizá la app.»), so release that app build before or with this host.
mars-ram 0.1.6
Released together with Android build 10 of the app. That app build needs mars-ram 0.1.6 (MINIMUM_HOST_VERSION) and asks older computers to update.
Update in the computer's terminal (Linux, macOS or Windows):
pnpm add -g mars-ram@0.1.6
mars-ram install
The session bridge still speaks protocol 1.7, so Pi sessions that are already running need no /reload.
New
- Private links and Siempre atento work over ZeroTier. The link commands take
--network zerotier --address <ipv4>(the ZeroTier address the phone paired with); the link server then runs a separate listener bound only to that ZeroTier address, on the same port 47811, next to the Tailscale one.mars-ram notify registeraccepts a phone that connects over ZeroTier from inside that ZeroTier subnet, andmars-ram doctorwarns per network, Tailscale and ZeroTier. - Limitation: a computer paired with the same phone over both Tailscale and ZeroTier keeps one Siempre atento registration, the last one, so its notices go over that network.
Fixes
- Security: the project browser refuses hard links in
file,diffandstage-link, and a working-tree diff takes only a single file, never a folder. Reported in #1.
mars-ram 0.1.5
mars-ram 0.1.5
Released together with Android build 9 of the app. That app build needs mars-ram 0.1.5 (MINIMUM_HOST_VERSION) and asks older computers to update.
Update in the computer's terminal (Linux, macOS or Windows):
pnpm add -g mars-ram@0.1.5
mars-ram install
Then type /reload in each Pi session that is already running: the session bridge now speaks protocol 1.7, a compatible minor bump.
New
mars-ram pair-zt [--ssh-port <port>] [--address <ZeroTier ipv4>]pairs the phone over ZeroTier, as an alternative to Tailscale. It shows a version 2 QR offer; Tailscale offers stay version 1. Over ZeroTier the phone gets sessions, the terminal and files; private links and Siempre atento still need Tailscale.- On Linux,
pair-ztandmars-ram doctorwarn when ufw or firewalld is on and may block ZeroTier, with the exact command to allow the interface. They never run sudo or change the firewall. mars-ram uploads-dir --jsonnames (and creates) the private per-user folder for phone attachments,/tmp/mars-ram-<uid>/uploadson Linux and macOS,%TEMP%\mars-ram\uploadson Windows. The system clears it; the app's retention setting still removes older files.
Fixes
- macOS: finds the Tailscale CLI inside
Tailscale.appwhentailscaleis not onPATH, sopair,doctorand private links work with the App Store and standalone Tailscale apps.pairalso says why Tailscale failed: not found, timed out, or its own error.
mars-ram 0.1.4
Computer side of Mars-RAM 0.1.4.
Install or update (Node.js 24+):
pnpm add -g mars-ram@0.1.4 # recommended
# or: npm i -g mars-ram
mars-ram installThen run /reload in open Pi and Gentle Shell sessions so they load the new bridge.
mars-ram version [--json]reports the installed release; the phone app uses it to tell you when this computer needs an update.- Session notices for the phone's «Siempre atento» mode:
mars-ram notify register|status|unregister(run by the app over SSH; the secret is read from stdin, the phone address must be a Tailscale address). The link server watches every local session and sends a short signed notice (project and state only) to registered phones inside your tailnet. - The bridge reports how a run ended (
agent_settled.outcome: completed / failed / aborted; protocol 1.6). Older apps ignore it.
SHA-256 of mars-ram-0.1.4.tar.gz (also embedded in install.sh and in the npm launcher): 0dea49aa4f621333c04280d6b25bce57668a74086ca42ac2e8bda2313513ed3d
mars-ram 0.1.3
Computer side of Mars-RAM 0.1.3.
Install or update (Node.js 24+):
pnpm add -g mars-ram # recommended
# or: npm i -g mars-ram
mars-ram installThen run /reload in open Pi and Gentle Shell sessions so they load the new bridge.
- The phone's chat handle now follows the focused Herdr pane: a terminal opened from Computers shows the chat of the Pi or Gentle Shell session in front, switches with focus, and hides on panes without a session.
mars-ram herdr listlists each tab's panes (optionalpanesfield); the bridge reports its pane in/state(terminalPane, protocol 1.5). Older apps ignore both; older bridges keep today's behaviour.
SHA-256 of mars-ram-0.1.3.tar.gz (also embedded in install.sh and in the npm launcher): 7f0bf65fad1a5c2398c8d8bb7047c7c7de91867d81671ef4771d34f78809836e
mars-ram 0.1.2
Computer side of Mars-RAM, now on npm.
Install or update (Node.js 24+):
pnpm add -g mars-ram # recommended
# or: npm i -g mars-ram
mars-ram install
mars-ram pairOn Linux and macOS, curl -fsSL https://marssall.github.io/mars-ram/install.sh | sh also works. See the install guide.
- npm package
mars-ram(no install scripts or dependencies); the Windowsirm | iexone-liner is retired (Windows Defender blocks that pattern). mars-ram doctorreports the command on PATH instead of guessing what it is.
SHA-256 of mars-ram-0.1.2.tar.gz (also embedded in install.sh and in the npm launcher): ac1d4fe944e803f57a71b1bd626b756198ceafb8a67e0cfa232886f025fde6d6
mars-ram 0.1.1
Computer side of Mars-RAM.
mars-ram installandmars-ram doctorno longer print Node's ExperimentalWarning.
Install or update: curl -fsSL https://marssall.github.io/mars-ram/install.sh | sh (Linux, macOS) or, in a normal PowerShell window, powershell -ExecutionPolicy Bypass -c "irm https://marssall.github.io/mars-ram/install.ps1 | iex" (Windows). See the install guide.
SHA-256 (also embedded in both installers): 787c5efb47e5f3518a7dbc6270f49136d992af9df46f1cd4a3300c51789fed50