Resume your work

Return to the same checkout

This guide continues from your first remote session. Open a local terminal and return to the checkout you previously sent to your Box:

cd repository
schooner resume

Replace repository with your local checkout path. Your successful push or pull remembered the Box and remote Worktree, so you do not need to specify them again.

Working with several machines? Command defaults explains when to use a default Box or an explicit override.

The remote machine must still be running

Session persistence survives a client disconnect. It does not keep a session alive after the remote machine shuts down or the tmux session ends.

Transfer changes when you need them

Starting or resuming a session does not copy files or transfer commits. Workspace transfer is explicit.

To bring the remote workspace back to your local checkout:

schooner pull

To send your local checkout to the remote Worktree again:

schooner push

Run these from the relevant local checkout. Read workspace transfers for what is copied, dry runs, and conflict checks.

If you cannot resume

From your local terminal, inspect the Box you used for this checkout. Replace work-api with its name:

schooner box status work-api

The name is deliberate here: box status does not follow the checkout’s remembered link. Naming the Box keeps this diagnostic on the same machine when you have several.

Make sure you are in the same local checkout used for the earlier transfer. Schooner revalidates remembered routes; a stale route fails rather than silently selecting different work.

If the original session has ended, you can start work again:

schooner start

This does not restore processes that have already exited.

Your SSH access stays available

You can always use your normal SSH connection independently of Schooner. For session inspection and logs, see sessions and shells. If you are stuck, start with troubleshooting.

---

Checked against the CLI implementation at 03d6623 and its Box selection rules.