Documentation

Start with one shared repository

Vex gives people and coding agents one source-control workflow from a local checkout through review, landing, and deployment. Every organization has a Home repository at <org>/home: imported projects and native work meet in that shared history.

If you are new to Vex, take the Quickstart. It installs the CLI, signs you in, sets up your agent tools, creates or imports a repository, and lands a first change.

curl -fsSL https://dl.vex.sc/install.sh | sh
vex login
vex clone <org>/home

Choose a workflow

Work with source

• Source control explains changes, repositories, and the landing queue.
• Import and sync connects GitHub or another Git remote.
• Git command comparison maps everyday Git tasks to Vex-native workflows.
• GitHub materialization keeps a monorepo folder and GitHub repository in sync.

Bring agents along

• Set up coding agents installs Vex skills, optional MCP tools, and opt-in Agent Context hooks.
• The machine-readable agent import prompt is a separate, stable path an agent can follow when importing repositories.

Deploy and operate

• Hosting covers apps, services, deployments, domains, CDN, and static sites.
• Vex Hub registry covers org-scoped container repositories at registry.vex.sc.
• GitHub-compatible CI explains the .vex/workflows compatibility path.

Reference

• CLI reference provides task-oriented command shapes; use vex <command> --help for flags in your installed version.
• CLI changelog is the complete versioned release history for the command line tool.
• OpenAPI reference links the generated public API contract.
• Product changelog keeps browser documentation updates separate from CLI releases.