imuximux
AI workbench for macOS

Clavue Worktree

Worktree hosts working copies for agents — repositories, parallel trees, and code browse. It is not a forge. Source of truth is GitHub and/or Cursor Origin. clavue-worktree never becomes git origin.

What stays on the git remote

Push, fetch, PR, and CI stay on GitHub and/or Cursor Origin. The host holds a working copy you can browse and hand to agents. It is never origin.

  • github.com/{owner}/{repo} and origin.cursor.com/{owner}/{repo} are remotes
  • Dual-push is allowed
  • Public trees are listed at /worktree/explore
  • clavue-worktree is the working-copy host only

Three ways to work

Pick one per task. Mixing all three on the same dirty files is the thing this exists to avoid.

  • GitHub or Cursor Origin + one local branch — default
  • Local Worktree — git worktree on your machine
  • imux thread tree or clavue-worktree — Agent Chat already offers both

What imux already does

Agent Chat write tasks default to a thread-keyed tree under .imux/worktrees/. That stays local to the repo you opened.

Local Worktree

Use git worktree so agents share one object store and keep separate dirty trees.

cd ~/src/your-repo
git worktree add ../trees/feat-auth -b feat-auth
git -C ../trees/feat-auth push -u origin HEAD
gh pr create

Same account

Worktree does not add a login or a quota. Sign in at www.clavue.com/account. Models stay on api.clavue.com. After you finish a branch, open the pull request on GitHub or Cursor Origin.

What we don’t add

Worktree is a working-copy host. It does not become a forge, a ticket tracker, or a second membership.

  • A third git review host
  • Farm SSH or disk paths on www
  • A seventh billed product
  • A claim that agents need no prompts

Next