The CLI

The jetsyn CLI is the Pro direct gateway: a single self-updating shell script that signs you in once, then reaches into your own cloud cell from any terminal. Nothing but the script lives on your machine. Your files, your memory, your compute, and the model credentials all stay in the cell, so the CLI is only a pipe, never a place your data or keys are stored.

Install#

The CLI is one self-contained bash script. Its only hard requirements are bash and curl; python3 is needed only for the secure 443 transport described below. Download it, make it executable, and put it on your PATH.

# bash + curl required
curl -fsSL https://jetsyn.ai/cli/jetsyn -o /usr/local/bin/jetsyn
chmod +x /usr/local/bin/jetsyn

# confirm it runs
jetsyn --version

Check your installed version with jetsyn --version, and the latest published version with curl https://jetsyn.ai/cli/version.txt. To upgrade in place, run jetsyn update: it downloads the newest script, validates it, and only then overwrites itself. A quiet once-a-day check nudges you when a newer version is out. Nothing installs automatically.

Sign in#

The first cloud command signs you in with a browser-based device-authorization grant. You approve the terminal once; a long-lived token is stored locally and every later run reuses it with no prompt.

1. 1

   Start

   Run jetsyn (or jetsyn login). The CLI requests a device code and a short user code from the sign-in service.

2. 2

   Approve

   Your browser opens to app.jetsyn.ai/cli with the code prefilled, so an already-signed-in browser just shows Authorize. On another machine, visit that URL and enter the code shown in your terminal.

3. 3

   Poll

   The CLI polls until you approve, then writes a token to ~/.jetsyn/credentials with mode 600.

4. 4

   Land

   The token names the cell your terminal lands in. Later runs show signed in as ... and connect straight through.

jetsyn login     # approve the terminal in your browser (once)
jetsyn logout    # forget the stored sign-in

Commands#

Every cloud command runs one command inside your cell and hands your terminal to it. The mediation you get, driving the model directly versus talking to an employee, is decided entirely by that in-cell command, not by the transport underneath.

`connect` versus `agent`. connect opens bare Claude Code, so you drive the model directly over the folders. This is the direct, unmediated door. agent runs a single standard employee you converse with. This is a conversational door: you talk to the employee and it does the work. Both ride the same transport; only the in-cell command differs.

The cell argument. Every cloud command takes an optional cell name. Omitted, the CLI targets the cell bound to your sign-in, then the stored workspace, then JETSYN_CELL. An explicit jetsyn connect <cell> argument always wins. Cell names are restricted to [a-z0-9_-].

`jetsyn memory`. jetsyn memory show prints your cell's Brain; jetsyn memory save "<text>" [path] writes a note, with the content base64-encoded in transit so any text is shell-safe. Both run python3 -m jetsyn.memory_cli against the same store your employee reads and writes.

jetsyn                 # sign in if needed, open Claude Code in your cell
jetsyn agent           # chat one standard employee in your cell
jetsyn shell finance   # a plain shell in the "finance" cell
jetsyn resume          # pick a saved session to resume

Flags and pass-through args#

--help, --version, and --print run on their own and exit immediately. --no-launch and any -- <args> shape the local launch (jetsyn local and the resolved local command); the cloud subcommands hand your terminal straight to your cell. jetsyn local runs a live-recommended loadout that resolves from JETSYN_RECOMMENDED_URL, falling back to a baked-in default; use jetsyn --print to see exactly what it will run.

The two transports#

Cloud commands reach your cell over one of two transports, chosen automatically. You never configure the endpoint; the CLI picks based on whether an SSH key is present.

Override the choice with JETSYN_CONNECT. An explicit value wins; otherwise the CLI uses SSH when a key exists and the 443 tunnel when it does not.

# force a transport (otherwise chosen automatically)
JETSYN_CONNECT=ssh   jetsyn connect
JETSYN_CONNECT=https jetsyn connect

Environment#

A handful of variables tune the client. Defaults are sensible; you rarely set any of these by hand.

See Configuration for the full set of environment variables and their defaults.

Where to go next#