Quickstart
Go from an empty terminal to a live Claude Code session in your own cloud cell in a few minutes: install the CLI, sign in once, then connect.
Install one script, sign in once in your browser, and you are inside Claude Code running in your own cloud cell. Nothing to configure, no API key to manage, and the work runs in the cloud, not on your laptop. It takes a few minutes.
Requirements
You need a Mac or Linux machine, curl to run the installer, and a browser for the one-time sign-in. The CLI is a single self-contained script: no Claude, no SDK, and no API key ever lives on your machine.
From zero to a live session#
Two commands, and most of that is one-time setup. Install the CLI, then run jetsyn. The first run signs you in and drops you into your cell; every run after that goes straight to the cell.
curl -fsSL https://jetsyn.ai/install | sh- 1
Install the CLI
Run the one-liner above. It downloads a single self-contained script, installs it onto a directory already on your PATH, marks it executable, and verifies it with
jetsyn --version. If the install directory is not on your PATH, the installer prints a one-lineexport PATH=...to run first. - 2
Sign in once
Run
jetsyn. The first run opens your browser to approve this terminal. Approve with your Jetsyn account, or create one. The sign-in is saved locally with restricted permissions, so you never sign in again on this machine. Your account also decides which cloud cell the terminal lands in. - 3
You are in your cell
After approval,
jetsynopens Claude Code running inside your cloud cell at/workspace, with your folders, memory, and compute. Later runs skip the browser and land here directly.
Reach your cell three ways#
The same cloud cell has more than one door. Which one you use depends on how you want to work: drive the model yourself, or talk to your AI employee and let it do the work. The connection is identical; only the command that runs inside the cell changes.
| Command | What it opens | When to use |
|---|---|---|
jetsyn or jetsyn connect | Claude Code, live in your cell's folders | Drive the model yourself, directly over your files |
jetsyn agent | One Jetsyn employee you converse with | Talk to your AI employee; it does the work and fans out to its own sub-agents |
jetsyn shell | A plain shell in the cell | Move around the filesystem or run a quick command |
jetsyn resume | A saved session, resumed | Pick up a Claude Code session where you left off |
Each of these takes an optional cell name, for example jetsyn connect my-cell. With no name, the terminal lands in the cell bound to your account. Name a cell to open a specific one you belong to.
connect vs agent
jetsyn puts you directly in the folders: you drive Claude Code yourself. jetsyn agent is conversational: you talk to your AI employee and it does the work. Same cell, same files, different depth of reach.
Tip
Inside jetsyn agent, Ctrl-C stops the current turn without ending the conversation. Ctrl-D, exit, or quit ends the session.
The commands you'll use first#
| Command | What it does |
|---|---|
jetsyn --help | List every command and flag |
jetsyn --version | Print the installed CLI version |
jetsyn login / jetsyn logout | Re-verify your sign-in, or forget the stored sign-in |
jetsyn update | Update the CLI to the latest version |
jetsyn --print | Print the resolved launch command without running it |
jetsyn --no-launch | Preview the intro and resolved command, then stop |
jetsyn -- <args> | Append your own arguments to the underlying agent |
jetsyn local | Launch the recommended agent on this machine instead of the cloud cell |
Where your session runs#
Everything you do through the CLI happens inside your cloud cell: a private container holding one brain and one AI employee, with your data as folders on its volume. Your laptop only ever holds the jetsyn script, and no key sits on your machine. To understand the cell and the model it is built on, read What Jetsyn is.
Next steps#
What Jetsyn is
An AI employee plus an AI workspace, the cell, and how every surface works over the same files.
Read →The CLI
The full command reference, the transports, and how the CLI reaches your cell.
Read →Build an AI employee
Author a new employee as plain Claude Code files, with a minimal working example.
Read →Architecture
How a cell is built: the spawn-per-event employee, durable resume, and credential isolation.
Read →