Syncing Across Machines

Your workspace, including your project register, lives in a git repository. When you work on more than one computer, git carries the changes between them. PRIMA Project Management uses three commands for this, and the two that push, /sync and /night, check the workspace identity first.

Command	What it does with git
/day	Pulls from main on origin at the start of the day
/sync	Commits every change and pushes the current branch to its remote, at any point in the day
/night	Commits every change with a session summary and pushes to main on origin

Run a Sync

1. Type /sync in Claude Code whenever you want your changes saved to the remote repository.
2. Wait while Claude checks the workspace, commits your changes and pushes them.
3. Read the confirmation, which gives the commit, the files changed and the branch updated.

/sync takes no arguments, and Claude writes the commit message from the staged changes. When the working tree has no changes, Claude reports Nothing to sync — working tree clean. and stops.

Caution

/sync stages every change in the workspace with git add -A. Move or ignore any file you do not want committed before you run it.

The Workspace Identity Check

Your register records the repository that belongs to this workspace, in workspace.githubRepo. Before every push, Claude compares that value with the address of the remote named origin. When they differ, Claude stops and pushes nothing.

WORKSPACE MISMATCH
   Expected repo: example-consulting/example-consulting-biz-os
   Actual remote: [the address git reports]
   Aborting. Verify you are in the correct workspace.

The check protects you when you keep several workspaces, such as one per client. To fix a mismatch, run git remote get-url origin and check that the address names the repository recorded in workspace.githubRepo. Correct whichever is wrong. When workspace.githubRepo is empty, Claude skips the check and says so in the confirmation.

Working on Two Computers

1. Run /day on the first computer, so it pulls the latest changes before you start.
2. Close the session there with /night, or run /sync, so your changes reach the remote.
3. Run /day on the second computer, so it pulls those changes before you begin work.

What Does Not Travel

• Checkpoint files: they live in ~/Documents/Agent Outputs/, outside the workspace, so each computer keeps its own.
• State backups: the AI Business OS .gitignore excludes .claude/state/backups/, so each computer keeps its own backups.
• Calendar and meeting connections: each computer needs its own connectors set up in Claude Code.

Related Pages

• Closing the Day covers the commit and push at the end of a session.
• Rules It Installs describes the workspace identity rule behind the check.
• /sync in AI Business OS describes the base version this command replaces.