Console/Worktree

Clavue Worktree

Parallel AI working copies. GitHub stays the remote. Not a second forge, and not a seventh billed product line.

Clavue · Worktree

Public addressesgpu-cn-01ai-dev-1

How to reach the host

Addresses are public. Passwords and API tokens are not on this page. Sign in with an SSH key as worktrunk.

Use	Address
This site	https://www.clavue.com/worktree
LAN SSH	ssh worktrunk@192.168.2.150
WAN SSH	ssh -p 2210 worktrunk@180.97.200.66
Worktree API	http://192.168.2.150:7433
API health	http://180.97.200.66:7433/health
Clavue Agent LAN	http://192.168.2.150:443
Clavue Agent WAN	http://180.97.200.66:4430
Repos / trees	/srv/worktrunk/repos · /srv/worktrunk/trees

# LAN
ssh [email protected]

# WAN
ssh -p 2210 [email protected]

# WAN → local API tunnel
ssh -p 2210 -L 7433:127.0.0.1:7433 [email protected]

curl -sS http://180.97.200.66:7433/health
curl -sS https://www.clavue.com/worktree-access.json

Public API: http://180.97.200.66:7433. One tree per user via POST /v1/users/worktree. 443 / 4430 stay clavue-agent.

Default

GitHub + one local branch

Keep working as you do today. No new tool, no remote change.

Local speed

Local Worktrunk

wt switch -c feat creates the branch, directory, and cwd in one step. For several Claude / Codex processes on your machine.

Already in imux

Agent Chat thread trees

Write tasks default to .imux/worktrees/thread-*. Isolation stays inside the repo you opened.

Optional host

Clavue Worktree host

Clone from GitHub onto the farm. Agents write in isolated trees, then push the branch back to origin for a PR.

How this sits next to GitHub

Layer	Owner	Leave alone
Source of truth	GitHub origin	remote URL, PRs, Actions, protection
Working copies	wt / imux / Clavue host	do not invent a second host for the repo
Account & models	/account · api.clavue.com	no second login, no second quota

The fast path

Clone from GitHub (or wt-host clone). origin still points at GitHub.
One tree per agent: wt switch -c feat-a, then feat-b.
wt list shows dirty and ahead. When done, push and gh pr create.

brew install worktrunk && wt config shell install
wt switch -c feat-auth
wt list
git push -u origin HEAD && gh pr create

Next: cloud development and larger storage

Use the addresses and farm first. Cloud development and large storage come in phases. Do not steal origin from GitHub, and do not put git trees on object storage.

now
Addresses + farm
Host is up. /worktree and /worktree-access.json show SSH/API paths. GitHub stays origin. Local disk holds trees.
next
Easy access
Member SSH keys. Optional WAN map or clavue.com reverse-proxy for /health. No passwords on the site.
later
Cloud development
clavue-agent jobs run in /srv/worktrunk trees. imux can offer “use Clavue host” as a choice. Still push to GitHub.
later
Larger storage
Keep git worktrees on POSIX disk/NFS. Put artifacts/logs on object storage. Prune merged trees. Add a volume, then a second node on the same export.

Read the docs →Same membership /account →Agent workflows →Upstream Worktrunk →

This page does not replace the homepage. Other family lines: Chat, Bot, GUI, CLI, imux IDE. Worktree is a working-copy option and still uses /account and api.clavue.com.