Mission Control for Your Terminal

One tool for editing code in the terminal, running shells, and keeping sessions alive across SSH — with a command bar made for humans. Press Ctrl + Space to get a taste.

▸
Type what you want to do…
Ctrl · Space
cmdNew terminal pane
!
cmdSplit right
C-t |
aiAsk the agent…
?
cmdNavigator: open file
C-x C-f

Batteries included: Mars comes with ROVER, AI-assisted coding in your browser. Meet Rover ↓

New here·60-second tour

Learn MARS by using it. Six steps, one keybinding at a time.

MARS · session 0 · 80×24
pressmars
$mars
███╗   ███╗ █████╗ ██████╗ ███████╗
████╗ ████║██╔══██╗██╔══██╗██╔════╝
██╔████╔██║███████║██████╔╝███████╗
██║╚██╔╝██║██╔══██║██╔══██╗╚════██║
██║ ╚═╝ ██║██║  ██║██║  ██║███████║
╚═╝     ╚═╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝
session 0 · attached · press any key to dismiss
$

Step 01 / 06 · Bare `mars` opens an auto-numbered session in your cwd. Sessions are the default — they survive closing the window.

tip · ← / → on your keyboard advance the tour
Five keys

Five keys carry you everywhere. Every menu row shows its real binding — the fast path teaches itself.

A real session, replayed: Ctrl+Space, type “split r”, and the row shows its key (C-x 3); then ! runs a shell command in a pane. Long pauses are shortened.
Palette
Ctrl+Space

Mission control. Search every command; type to filter, Enter to run. Works inside terminal panes too.

Shell
!

Inside the palette — run a shell command in a terminal pane.

Agent
?

Ask the built-in agent anything. Sees your buffers and panes.

Files
C-x C-f

Navigator: browse and jump to any project file with fuzzy filter.

Panes
C-t

Space warp: tabs, panes, splits — with an on-screen cheat panel.

Sessions

Replaces emacs and tmux — actually makes sense.

One editor, one multiplexer, one set of keys. No modal cliff, no 40-page cheat sheet, no juggling two tools that don't know about each other. Sessions keep buffers, panes, and running shells alive when the window closes, the SSH connection drops, or you just walk away. Come back to exactly where you were — plus a one-line while away 3h20m briefing, failures first.

  • Auto-numbered on first launch. Survive detach.
  • Autosave every 30s and on every disconnect.
  • One client per session — attaching from a second window takes over cleanly.
  • C-x g opens the full Away Digest whenever you want it.
A real session, replayed: start build, leave a test run going, detach, then reopen it from mars ls and get the briefing. Long pauses are shortened.
Agent · SSH

The agent works on every box. Your key never leaves home.

Set your API key once, on your own machine. mars ssh gpubox forwards the auth socket and starts a local key broker on demand. The remote proxies its LLM calls home through the tunnel — the key never lands in the remote's env, shell history, or disk.

[ your laptop ]
API key · mars keyd
never transmitted
▼
[ ssh tunnel ]
forwarded auth socket
LLM proxy round-trips home
▼
[ remote box ]
mars — agent just works
no key on disk
$ mars ssh gpubox
· forwarding auth socket · starting mars keyd (inherits this shell's key)
· agent ready on gpubox — proxying via tunnel
Launch window · open

One tool. One set of keys. Every box.

then run mars — press any key to dismiss the banner.
Rover · AI-assisted coding · beta

Your coding agents, in any browser.

Coding agents like Claude Code work for hours in a terminal, then stop and wait: to approve a command, pick an option, or answer a question. Rover watches every session on your machines and puts what needs you first, on your phone or your laptop, so a five-second answer doesn't wait until you're back at your desk.

No account needed. Rover runs on Mars, and the install above includes its bridge: pair your own computer and use Rover free, without signing in.

Claude asks before it deletes a build directory. Tap Yes, and the next question is already there.
Rover in use

Open a session, and take the terminal.

Read what the agent did, raise its live terminal, and answer it there.

Both clips are recorded from Rover itself, on its demo host: the sessions are examples, the screens and taps are real.

How Rover works

Your agents keep working. You step in only when they need you.

  1. 1

    Your agents run on a machine

    Your own computer, running Mars, or a machine Rover starts for you in the cloud. Rover connects to the terminal sessions there. Nothing about how your agents work changes.

  2. 2

    Rover shows you what needs you

    Every session on every machine in one list, the ones waiting on you first: the question, the command it wants to run, and the agent's own choices.

  3. 3

    Answer, or take the wheel

    Tap one of the agent's choices, write your own answer, or open the live terminal and type into it, as if you were at the keyboard.

Rover on a laptop

The same Rover, as a desk.

Open Rover in a laptop's browser and you get every host down the side, a board of what needs you, and each session's terminal, timeline and files a key away. Here: J and K to move, Y and Enter to answer, then ⌘⌘ L for what the agent did.

What you can do with Rover

Everything you'd walk back to your desk for.

What happened while you were away

Come back to a short account of what finished, what failed and what's still waiting on you.

Ask about your machines

Ask Rover in plain words what a session is doing or why something stopped.

Wake on a schedule

Wake one of our machines at 8 on weekdays to pull and run the tests. It sleeps when you say.

Install it like an app

Add Rover to your phone's home screen and it opens full screen, like any other app.

How to run Rover

On a computer you have.

Your own computer
Free · no account

Rover connects to a computer you already have, through Mars. Pairing gives your browser a key to that machine and nothing else.

  1. 1. Install Mars, with Rover's bridge
  2. 2. Pair: it prints a QR code and a link
  3. 3. Scan the code with your phone, or open the link. Paste a link instead
Start to finish: the link opens your computer's own terminal.

Needs Rust 1.85 or newer for the install. mars pair --check says what's missing, with the fix for each. Your computer has to be on for Rover to reach it.

Your work stays yours

Rover shows you your machines. It doesn't keep them.

  • Pairing needs no account. The link carries the key to your machine in the part of the address that browsers never send to a server.
  • What you see and type in a terminal goes between your browser and your machine. Rover's server doesn't keep it.
  • Your agents use your own Claude account. Rover doesn't sell or pay for Claude.
  • The part that runs on your computer is open source: Mars's bridge, which Rover talks to, is src/serve.rs in Mars's public repository.
Questions about Rover

Before you start

Do I need an account?
No. Pair a computer of your own and use Rover without one.
Do I need Mars?
Yes, Rover reads the sessions of machines running Mars. Ours come with it; on your own computer, use the install command above.
Which agents does it work with?
Claude Code, whose questions become buttons. It also recognises pi, Codex, Copilot, OpenCode, Goose, Aider, Cursor Agent and Gemini.
What does it cost?
Nothing with your own computer.
What if my computer is asleep?
Rover can only reach a computer that's on.
Is it finished?
Rover is in beta, so expect some rough edges, and tell us about them.

Pair your own computer. No account needed.