Move Baton context between machines

Context carries a repository's Baton state (its memory, plans, handoffs, task board and worktree patches) from one machine to another. Each push makes a snapshot. Snapshots are kept in order and never merged or rewritten.

Spaces

There is one context space per repository per owner. Use your personal space by default, or a project's space with --org <org> --project <project>; pushing to a project needs a role that can publish there. An archived project's context is read-only.

Open Context to see your spaces. Open one to see its snapshots (author, device, time, files and size), read the files of any snapshot, and copy the pull command.

Push and pull

1. On the first machine, run deftro context push.
2. On the other machine, in the same repository, run deftro context pull.
3. If you edited a file here since your last sync, the incoming version is saved next to it as <file>.remote instead. Add --force to overwrite.

deftro context status compares your copy with the latest snapshot, and deftro context log lists snapshots. Pull only writes Baton context: agent settings, CI and git files are never written.

Limits

A snapshot can hold up to 500 files, each up to 1 MB, and 20 MB in total. deftro leaves out files that are too big and lists them as skipped. A snapshot that contains a credential is refused, with the file and line, and there is no override. Snapshots count toward your storage quota.

"Someone pushed since you last synced"

Code: context_conflict

Another push landed after the snapshot your machine last saw, so nothing was written. Either run deftro context pull to bring their snapshot in and then push again, or run deftro context push --force to push on top of theirs. History keeps both.

"The snapshot is too large"

Code: context_too_large

The push has too many files, a file over the size limit, or too much in total, and the refusal says which. Its details list the files over the limit; for the total, the largest ones. Remove or shrink them, then push again.