wsp add

usage: wsp add
       [<user@host>|<ssh alias>|<folder>|<url>|<owner/repo>|<computer> --update…
       [--recipe <name>] [--later] [--on <computer>] [--into <folder>]
       [--name <name>] [--base <branch>] [--yes] [--keep <path>] [--cut <path>]
       [--no-memory] [--no-commits] [--remember] [--ssh-port <port>]
       [--ssh-key <path>] [--host-key <key>]
  a computer of yours over ssh by user@host or by an alias from your ssh config,
  or a project: a folder on this computer, a git repo or not, whose threads run
  in it, or a repo cloned into an empty folder here with --into <folder> or by a
  computer with --on <computer>; nothing prints the join line another computer
  types, a computer with --update puts this wsp's daemon on one already in, and
  a computer with --sign-in signs that agent in there once, outside every
  machine on it

  --state         the state file: this word first, else WSP_HOME's state.json,
                  else ./.wsp/state.json when the current directory is a
                  checkout of wsp, else state.json in the home the running host
                  serves
  --name          the name to call the computer by here; what its address calls
                  it without one
  --ssh-port      the port ssh dials that computer on (default 22)
  --ssh-key       the key file ssh logs in with; whatever your own ssh config
                  and agent already use without it
  --host-key      the host key of a computer this one has never dialled, as you
                  read it on that computer; without it the add shows you the key
                  that computer answers with and asks, and off a terminal it
                  refuses rather than trusting whatever answers
  --recipe        the saved recipe a computer added over ssh is set up from once
                  it joins, or with --resume the one it is set up from now; wsp
                  recipes lists them. Without it a computer joins and waits on
                  what goes on it, with the base tools going on meanwhile
  --later         go on past a sign-in that waits on you and leave it waiting,
                  rather than waiting here for it; wsp add <computer> --resume
                  follows it again, and asks for a fresh page and code only
                  where the last one ran out
  --resume        the computer named is already added, or joined and waits on
                  what goes on it: set it up, from --recipe where given, else
                  from what it holds, running only what is missing
  --update        the place named is already in this wsp: put the daemon this
                  wsp deploys on it, over the link it is holding or over the ssh
                  road it was added on, restart its agent and keep the threads
                  and machines standing on it
  --sign-in       the agent to sign in on the place named, once: the sign-in
                  runs on that computer and every thread there shares the one
                  login. Offered by the join itself; this is the same road for a
                  computer already in
  --on            the computer a project lives on, by the name wsp computers
                  lists: a repo a computer clones needs one, and a folder here
                  takes one to have that computer clone the folder's own remote,
                  with the folder seeding what git ignores; without it a folder
                  here, or a repo cloned --into a folder here, is worked where
                  it sits
  --into          the empty folder on this computer to clone a repo into, one
                  that does not exist yet or holds nothing; the project is then
                  that folder, worked where it sits
  --base          the branch a thread of the project starts on; the remote's own
                  default branch at the clone without it
  --yes           send the ticked rows of the seed menu; without it a folder
                  seeding a project on another computer prints the menu and
                  sends nothing, since what git ignores in your folder is yours
  --keep          one more path off the seed menu that travels, however the
                  catalogue ticked it; given once per path
  --cut           one path off the seed menu that does not travel; given once
                  per path
  --no-memory     leave this folder's Claude Code memory here; the project's own
                  memory on that computer then starts empty
  --no-commits    leave the commits the remote does not have here; the
                  computer's clone then starts at the remote's own tip
  --remember      keep these ticks for this folder, so the next add of it starts
                  with them rather than the catalogue's
  --json          print the raw protocol values, one JSON object per line, with
                  everything else on stderr
  --host          read to say this line runs at its own host's terminal; it
                  dials no other