Skip to content

Workspace Remote

Available

The Git Remote tab in Workspace Settings configures remote sync for your workspace. This is where you connect to a GitHub repository, set authentication, and configure your git identity.

Enter the HTTPS or SSH URL of your GitHub repository:

https://github.com/your-username/your-workspace.git

Click Test Connection to verify CutReady can reach the remote with your chosen authentication method.

Choose how CutReady authenticates with your remote:

If you have the GitHub CLI installed and authenticated (gh auth login), CutReady automatically uses your credentials. This is the simplest option — no tokens or keys to manage.

Generate a fine-grained token with Contents: Read and write permission for your repository. Paste it into the token field. The token is stored in the encrypted Stronghold vault.

CutReady uses your system SSH keys via gix. Make sure your SSH key is added to your GitHub account and available in your system’s SSH agent.

Set the name and email that appear on your snapshots. This is especially useful when collaborating — your identity shows on the snapshots you create.

If you don’t set an identity in Settings, CutReady resolves it automatically using a priority chain — the first source that provides a name and email wins:

  1. Workspace settings — the name and email saved in this Settings panel (stored in .cutready/settings.json).
  2. Local git config — if a previous resolution already wrote to the workspace’s .git/config, that’s reused.
  3. Global git config — if you’ve run git config --global user.name and git config --global user.email, those are used.
  4. GitHub CLI — if you’re signed in via gh auth login, CutReady queries your GitHub profile (gh api user) for your name and email. If your GitHub email is private, the username@users.noreply.github.com address is used.
  5. Identity prompt — if none of the above sources have your identity, CutReady shows a one-time dialog asking for your name and email before your first snapshot.
  6. Fallback — as a last resort, “CutReady” / “app@cutready.local” is used so snapshots are never blocked.

Once resolved, the identity is persisted to both the workspace’s local git config and workspace settings, so subsequent saves are instant — you’re never asked again.

You only need remote settings if you want to:

  • Back up your workspace to GitHub
  • Sync across multiple devices
  • Collaborate with others on the same workspace
  • Open pull requests from timelines

If you’re working solo on a single machine, you can skip this entirely — CutReady’s snapshot and timeline features work fully offline.