Skip to main content

​
Start with one local gate

The local CLI gate is Experimental, as recorded in feature status. In your first hour, use gate. Write a reviewed case, accept a passing baseline, break the case, and read the blocking result. Start with the TypeScript / JavaScript five-minute loop.
Preview writes nothing; --apply authorizes the scaffold. Package installation requires network access, but deterministic initialization and evaluation need no account, browser, organization, GitHub remote, EvalGate API key or model call. Always use the scoped npx @evalgate/sdk; the unscoped npm package is unrelated. In a Python project use the installed evalgate executable and the Python guide, checking its released capability boundary. Each runtime executes its own specs. The loop is complete when a non-empty reviewed baseline passes unchanged, a deliberate behavioral regression exits 2, and restoring the behavior passes against that same baseline. status --json exit zero only means the status document was produced. A gate pass supports its configured evidence; it is not universal safety or deployment permission. evalgate.product.json is not an init artifact: Experimental understand --apply writes product intent separately. .evalgate/project.json is not local-init output either: link writes hosted linkage. Remember evalgate.project.json as local execution, and .evalgate/project.json as hosted linkage.

​
After the first gate

Use CI/CD gates for the command-mode comparison: what gate, later ci, and later hosted check prove, their costs, and what a red build means. Quality score is the shared descriptive scoring contract; a blended score does not replace release checks. Use migration guidance for existing cases. The public playground offers a synthetic review fixture; it makes no production or provider-quality claim.

​
Optional hosted setup

The hosted platform is Beta. Repository Intelligence, Agent Skills, MCP and product-understanding availability follow feature status. Hosted collaboration is a separate, browser-approved step:
login saves a revocable human session outside the repository. link adds non-secret organization/repository/root identity without replacing local specs, baselines, configuration or user edits. Cloud intake is pinned to an exact commit; branch movement changes checkout status, not repository identity. A behind checkout may remain linked and locally ready. Unpushed or diverged work cannot silently borrow evidence from another commit. Repository Intelligence supports GitHub repositories. GitLab CI can run the local gate recipe; it does not provide GitLab repository connection or cloud repository discovery. Creating a connected repository scan requires eval:write and an organization member role because it persists evidence; reading existing evidence requires eval:read. Model-backed judges require separate BYOK credentials and provider spend. Check production adoption before expanding a hosted pilot.

​
Optional coding-agent instructions

The official Skills repository is Experimental. Inspect with npx skills add evalgate/skills --list, then install deliberately with npx skills add evalgate/skills. Instructions do not issue credentials, approve spending or enforce release policy. See write evals with your agent after the deterministic first loop.

​
Inspect installed capabilities

npx @evalgate/sdk version reports the installed CLI; npm view @evalgate/sdk version observes the current registry version. npx @evalgate/sdk capabilities --format json reports supported commands. Do not treat a source-tree version as published. Package publication does not establish that a matching hosted API is deployed.