Developer overview

This section is for people changing Quasar. Installing and running it needs no Go, Rust or Node toolchain.

The repository is the authority; where it disagrees with this site, the checkout wins. Start with:

make help

Then read CLAUDE.md (architecture, invariants, frozen contracts), AGENTS.md (operating and verification rules) and docs/developer-tooling.md (every command).

Repository map

Path	Responsibility
`control-plane/`	Go API, authentication, scheduling, signaling and persistence.
`node-agent/`	Rust GPU-host agent: sessions, media pipeline, app containers.
`web/`	React web client and admin interface.
`protocol/`	Frozen wire contracts (a submodule). Source of the Control-plane API reference.
`deploy/`	Image builds, the recovery image, and contributor Compose stacks (not a supported install).
`scripts/dx/`	Developer and diagnostic commands behind the Makefile. New tooling goes here, not `deploy/`.
`docs/`	Design records, configuration reference and developer tooling.
`site/`	This knowledge base (Astro/Starlight).

The main development loop

Initialise and inspect the checkout.
Make one bounded change.
Run the verification its files require. It’s not done until those pass.
Validate GPU or streaming changes on a real GPU host.
Keep commits scoped, and push the branch as you go.

Continue with Set up a checkout.