Source control

Your organization’s Home repository

Every organization owns a Home repository at <org>/home. Imported projects and native Composal work meet there as one shared history. Virtual repositories can expose a stable subtree without making a second physical repository.

Clone and access

Use the Composal-native clone path for a local checkout with Composal history and change workflows.

com clone <org>/<repo>
cd <repo>
com status

Use com clone <org>/<repo> --fs virtual only when a local virtual filesystem is available. A normal checkout remains the supported fallback. Repository access tokens allow scoped automation; browser downloads and API tokens have their own authorization boundaries.

For an explicitly enrolled experimental repository, live mode connects real local files to a central JJ store across machines. It uses com clone --live and a separate com live command surface; ordinary local checkouts are not converted automatically.

Submit changes, then land them

Composal tracks JJ changes separately from named bookmarks. Start work above a target, describe it, submit it, and request landing only when it is ready.

com new main
com describe -m "feat: add the change"
com submit --target main
com change show #42
com land #42

Plain com submit publishes ready-for-review Changes, including when you resubmit an existing draft. Pass --draft explicitly to publish work in progress. In the app, Mark ready prepares a draft for review without queueing it; Land marks the drafts in the selected stack or group ready and requests normal queue admission. See drafts and merge queue CI.

com sync fetches the target and reconciles submitted changes with server state. com land #N retains CI, approval, queue-order, and target-freshness gates for the submitted-together closure.

Queued changes show In flight with the number of landing requests ahead. Hover or open the control to see their titles, current queue states, retries, and errors. The preview refreshes every five seconds while the page is visible.

Key repository surfaces

• Browse trees, files, history, branches, changes, checks, and queue state in the web app.
• Create repository access tokens for scoped automation.
• Use virtual repositories when a project needs a rooted view of a monorepo path.
• Connect external Git sources with remote Git sync.
• Run GitHub-compatible workflows from .vex/workflows; see CI. For monorepos, select affected workflows and inspect queue impact details; administrators can request full CI when needed.

Virtual working-copy capability model

The browser shows server-safe repository information; it cannot open a local daemon socket. Inspect the actual host capability with the CLI or desktop application.

com daemon status --format json
com daemon capabilities --format json

The local daemon and its mount are host-specific. When the capability is unavailable, use a normal checkout and keep the same Composal source-control workflow.