Clavue · Worktree
Clavue can now host your working copies.
Built for agent scale: repositories, parallel trees, code browse, and sync. Push goes to GitHub and/or Cursor Origin. Clavue Worktree is the working-copy host, never git origin.
Early beta · same Clavue membership · not a seventh billed product.
One job
Host the working copy. Leave git origin on GitHub or Origin.
01
Open a public tree
Browse the hosted copy. Farm addresses and private paths stay off this site.
02
Bind your tree
Sign in with the same Clavue account. One tree per member per repo today.
03
Push to a real remote
GitHub, Cursor Origin, or both. Worktree is never added as origin.
Public
Everyone’s public trees, in one place.
Open any public repository or member tree on the host. Search by repo, branch, or file name. Private paths and farm addresses stay off this site.
Loading public catalog…
Worktree repositories
The host keeps a live working copy of each public repo. Sign in, then create your tree — it is bound to your Clavue account. Clone and push still point at GitHub or Cursor Origin.
- Hosted copy for browse, search, and agent file tools
- One tree per member per repo on the host today
- URL shape: clavue.com/worktree/r/<repo>
Signed-in members bind one public tree to their account. The host token never enters the browser.
GitHub and Cursor Origin
Both are first-class git remotes. GitHub is github.com/{owner}/{repo}. Origin is origin.cursor.com/{owner}/{repo}. You can keep both and dual-push. Clavue Worktree sits beside them as the working copy.
- GitHub: gh pr create / Actions stay there
- Cursor Origin: clone from origin.cursor.com; PRs live on Origin
- Dual-push is allowed; the farm is never added as origin
Pull requests
PRs stay on the git host you chose — GitHub or Cursor Origin. Worktree does not open a third review host. Finish the branch here, then open or merge the pull request on that remote.
Agents on every tree
Your code, PRs, and agents sit together. Ask Clavue Chat, GUI, CLI, or imux about the tree you are browsing. They can answer, patch, and push a branch — then the PR lands on GitHub or Origin.
The rest of the family
Worktree is a working-copy layer, not a new login. Chat, Bot, GUI, CLI, models, and imux share /account and api.clavue.com. Connect the surface you already use; do not fork quota.
Settings
Each tree follows host policy: one tree per member, a planned size cap, idle prune. Hard quota is not cutting writes yet. Check capacity on this site after you sign in.
Host capacity
Planned for trees —. Bound — · repos —.
- One tree per member. Planned cap —. Hard quota is not cutting writes yet.
- Idle trees prune after 14 days. GitHub history stays off this volume.
Every other host vs this one
A third git remote that also wants to own PRs
Working copies only. PRs stay on GitHub or Origin.
A new login and a new quota
Same /account and api.clavue.com as Chat, GUI, CLI, and imux.
Public farm IPs on the marketing page
Catalog and docs. Operator hosts stay operator-only.
What we don’t add
- A seventh billed product
- A Meet bot or a second ticket tracker
- A claim that agents need no prompts
- Farm SSH or disk paths on www
Name your tree. Start from public code.
Browse what others already published, or sign in and bind a tree to your account. Push still goes to GitHub or Origin.