Veect reads your components and tokens straight from the source — then composes production React on a branch you can publish. Nothing to paste, nothing to upload.
Enter this code at github.com to grant access. Veect requests the narrowest scope that still lets it read components and open pull requests.
Sign-in worked, but solstice/web is behind an organization policy. An owner needs to approve Veect once — then every seat can connect.
First connection to git.solstice.dev over SSH. Check this fingerprint matches what your host published before trusting it.
Veect will run {{ cxRepoName }}'s install scripts and dev server on your machine to render real components. Only connect repositories you trust.
This runs on your machine and can take a few minutes on first connect. You can leave it running.
No veect.config.json yet — pick the folders to read. This config rides your first published branch.
Your preview needs a few keys. They stay on this machine, encrypted — Veect never sends them anywhere.
Your system is waiting — everything you compose exports as real React.
Devon updated the tokens. Paste the new file — Veect diffs it against the live system and shows the impact before anything changes.