aether setup installs it). The command asks the bridge for the session’s chat and forks that chat, signed in as you (Fork a chat). The new task exists at once, and its start shows how the move goes.
The machine bridge then waits for the session’s turn to end, ships the session to Aether, and pushes the checkout’s HEAD with its tracked changes and what is staged to a new branch. Untracked files stay on your computer: git add a new file the task needs first. A push that would publish files named like credentials is refused, naming them.
With --computer, the session moves onto one of your computers instead: this one, in a new work tree, or another, your desktop when you are on your laptop. Aether starts a task there, in a work tree on the pushed branch, whose chat is that computer’s own Claude Code forking the session: claude --resume <session> --fork-session, under a new session id Aether chose.
--session; the command follows the new task’s start and prints each thing it waits on. It ends when the task runs, when the start fails, when the start waits on a destination computer that cannot be reached (it starts once that computer is back), or after 40 minutes; aether task watch follows it from there.
Flags
The new task’s first prompt: where the work stands and what comes next. Defaults to a prompt that asks the agent to continue.
The Claude Code session to move, by its id. Defaults to the session the command runs in (
CLAUDE_CODE_SESSION_ID).One of your computers, by its name or its id, that the session moves onto instead of a sandbox. A name that matches none of yours, or several, is answered with where the chat can be forked on your computers and why not.
The model the new task runs on, one its destination lists. Defaults to the session’s own where the destination lists it.
--json the command prints the new task’s main chat, as the fork answers it, and returns at once.
Exit status and refusals
The command exits 0 once the move is asked for, and, when it follows the start, once the task runs or still waits. It exits 1 when Aether refuses the move or the start fails, and 4 when the account has too few credits. A refusal or a failed start prints Aether’s code and sentence, such ascomputer_unreachable (the session’s computer has no connection to Aether), fork_in_progress (the chat is already being forked), credential_named_file (naming the files), too_large or session_file_missing. When the machine bridge is not running, the command says to run aether setup.