Source sync
Worktrees send tracked and nonignored untracked source inputs to/workspace on the remote machine. Safe explicit includes can add ignored inputs. Sync excludes raw Git data, secret paths, control files, and build-output directories.
The remote workspace has files and an initialized Git repository, without the laptop’s Git history. Guest-only caches and build outputs can survive later syncs. Exact managed source deletes propagate.
The CLI also keeps private frozen source bytes in its local source cache. Removing a remote machine does not remove that local cache.
Guest files and command output
Uploaded files and command-generated files live in the machine’s disk and memory. Artifact pulls write into a new private local cache directory outside authored source. Worktree execution output can be recovered by execution ID. Its spool is bounded to 64 MiB and remains until the next managed command or machine deletion. See Recover execution and clean up.Environment values and profiles
Worktree laptop env values enter remote process environments. Imported project values are stored in the encrypted project vault and delivered according to project and service scope.bead env ls lists names only.
Credential profiles and human subscription sign-ins use their own vault and delivery paths. See AI credentials and vault.