Ciresk CI

Ciresk CI runs the checks, tests and builds a repository declares in .ciresk/ci.yaml on remote workers with warm caches, and returns an exit code, a bounded summary and the exact next command, from a terminal, a coding agent or GitHub Actions.

Your first check in 5 minutes

Install the CLI and log in. The token goes to the OS keychain. See Install the CLI.
Terminal
```
curl -fsSL https://get.ciresk.com/ci | sh
ciresk ci auth login
```
Write the manifest. init detects the toolchain and writes .ciresk/ci.yaml with check and test; commit it. See Manifest.
Terminal
```
ciresk ci init
```
Run the check. The exit code is the verdict, the summary is the evidence, and the last line is the next command. See the Quickstart.
Terminal
```
ciresk ci check
```

Getting started

Install the CLI, log in and run a first check.

QuickstartFrom a repository with no manifest to a first ciresk ci check in five minutes.Install the CLIInstall the ciresk CLI, log in or set a token, and check that everything is in place.

Concepts

The manifest, workers and trust tiers, caching and tree sync.

How it worksWhat happens between ciresk ci check and the exit code: the manifest, the tree, the cell, the worker and the summary.Manifest.ciresk/ci.yaml is the only place a repository tells Ciresk CI what a check , test , build or lint is, which files feed it, which toolchains it needs and whether its result may be cached.Workers and trustWhat a worker is, which tasks it may run, and how the cell decides the trust tier of a job.Caching and tree syncHow a working tree reaches the cell, what goes into a cache key, and which targets a task runs on.

Guides

Claude Code, Codex, Cursor, GitHub Actions and your own workers.

Claude CodeRun checks on Ciresk CI from Claude Code: a CLAUDE.md snippet, a hook that gates git push , and the MCP endpoint.CodexRun checks on Ciresk CI from Codex: an AGENTS.md snippet, the MCP entry in ~/.codex/config.toml , a PreToolUse hook and codex exec recipes.CursorRun checks on Ciresk CI from Cursor: an always-on rule and the MCP entry.GitHub ActionsRun a Ciresk CI check as a GitHub Actions step with no repository secret, and gate pushes with a git hook.Run your own workerJoin a worker to Ciresk CI: your own machine, a Linux box at home, WSL2, or an instance in your cloud account.

Reference

Every CLI command, configuration key, exit code and error.

CLI commandsEvery ciresk ci command with its flags, its human output, its --json data and its exit code.ConfigurationThe settings of the CLI and the worker: flags, environment variables, files in the repository and worker.toml .LimitsEvery limit Ciresk CI applies to a request, a tree, a log, an artifact, a job and a worker, with its default and what you get when you reach it.Exit codesEvery ciresk ci exit code, what it is mapped from, and what to do next.ErrorsHow an error looks in the CLI and in --json , and where every error code is explained.FAQThe questions a developer or a CTO asks before adopting Ciresk CI, answered in a paragraph each.

Security

The security model, where data lives and the compliance status.

Security modelThe tenancy and credential model, written for a security reviewer: where data lives, who holds which credential, how trust is derived and what Ciresk never holds.Data residencyWhere every kind of data lives today, and what never crosses a region.ComplianceThe controls a public-sector, financial or defense reviewer asks about, the supply chain of a release, and the status of each attestation.

Ciresk CI API referenceEvery endpoint of the Ciresk CI API, generated from its OpenAPI document; the platform-wide keys, scopes and conventions are under API.