Mars CLI · Packages in development

Mars,
in your terminal.

The desktop’s agent, sessions and keys, full screen in your terminal or one run from a script.

01The client

The terminal client,
screen by screen.

01 / 10The Mars 0.2.0 terminal client with a demonstration project.

02One profile

Shared with
the desktop.

Both clients use the same data folder and the system’s credential store.

%APPDATA%\dev.mars.ade

The data folder

  • sessionsEvery session, with its history and its plan or goal.
  • settings.jsonModels and effort, connections, skill switches and MCP servers.
  • memoryWhat Mars remembers about each project.
  • skillsThe skills you installed.
  • checkpointsThe points a session can go back to.
  • model-selection.jsonThe models you chose to see.

The credential store

Windows Credential Manager

Provider keys are stored once, under the service dev.mars.ade, and both clients read them from there. A key is never written to the settings file or into a session.

  • One client at a time

    A session runs in one client at a time. Opened where it is out of date, it refreshes instead of overwriting newer work.

  • Different versions

    A desktop and a CLI of different versions share the folder; an older one never overwrites what a newer one wrote.

  • Another profile

    Set MARS_DATA_DIR and both clients use that folder instead; the CLI also takes --data-dir for one launch.

03In scripts and CI

Start a run with a command,
check how it ended.

The same agent without the full screen: a script or a CI job gives it a task, and the exit code says whether the run finished, failed or was stopped.

Commands
$ mars run "Keep the existing tests green"
$ git diff | mars run -            # the task from another command
$ mars run --review                # review what is not committed yet
$ mars run --plan "…"              # a plan to decide
$ mars run --detach "…"            # keeps going after you close it
$ mars runs list                   # how each run ended
$ mars doctor                      # what your runs used and cost
How a run ended, by its exit code
0
Completed
1
Failed or incomplete
2
Bad arguments
124
Timed out
130
Cancelled
101
Crashed

Get the CLI.

Built for Windows x64, Linux x64 and macOS on Apple silicon. The packages are in development; downloads open when they are published.