Before you begin
Sign in to the console(console). Administrator credentials come from your deployment configuration. See Operations to start a local instance.
If enterprise-demo exists, use its sql-query and code-review Skills. Otherwise, connect your own repository below.
1. Connect and synchronize a repository
In Git repositories(console), add the remote URL, credential reference, default ref (for example, refs/heads/main), and Skill root skills. Private Git hosts must satisfy the deployment's allowlist and network policy.
Test the connection, then synchronize. Inspect Pipelines(console). For failures, fix the reported files, rules, or lines, commit, and synchronize again.
2. Inspect candidate versions
In Skills Registry(console), verify the name, description, source commit, and file tree. Open SKILL.md and check referenced files.
Successful validation prepares a candidate; it does not change a live channel.
3. Create a complete snapshot
Open Create release(console). Review the set inherited from Stable, add Skills, and replace versions that need updating. Preview the complete view, review warnings and affected Profiles, then create the immutable snapshot.
A snapshot is a complete set, not a patch. If production contains A, B, and C, updating A still requires A's new version and the existing B and C versions. The drawer inherits Stable by default and explicitly reports removals.
4. Promote Canary first
In Release channels(console), select the new snapshot for Canary, review differences, enter a reason, and confirm. Record the snapshot ID. After verification, promote that same snapshot to Stable.
5. Connect a test Agent
Create a test Agent Profile(console): channel canary, explicitly authorized Skills, and dynamic mode. Register a mount client(console) for it and save the token, which is shown only once.
Follow the client guide to mount on Linux and connect an Agent. Verify both file contents and Agent behavior before promoting Stable.
Completion checklist
- The pipeline succeeds and Registry shows the expected commit.
- Canary points to the new snapshot; Stable stays unchanged until promotion.
- The test client reads only Skills authorized by its Profile.
- After Stable promotion, new opens on dynamic clients see updated content.
- The release appears in the audit log(console).