Automation
Run EKOS from CI, cron and scripts.
Refresh an index in CI
ekos build && ekos recover && ekos resolve --force && ekos compile && ekos commit --yes
resolve --forceprints conflicts as diagnostics but does not fail the pipeline.commit --yesskips the LLM-spend prompt (only relevant when[llm-description]is enabled — leave that off in CI unless you intend the spend).- Exit codes are non-zero on failure.
- For a project in the EKOS home, add
--project <name>(or setEKOS_PROJECT) to every command.
Gates
ekos doctor --json | jq .
ekos coverage --strict # fail when an input kind compiled into nothing
ekos check refs --fail-on error --format sarif > refs.sarif
ekos check refs --baseline 2026-10-01T00:00:00Z --fail-on warning # only findings new since then
--baseline takes an RFC 3339 ledger time or an earlier --format json report.
Run logs
On a build from main, build, recover, resolve, compile, commit and every command that
changes something write JSON lines to <state>/runs/<stamp>-<command>.jsonl, or to the file
EKOS_RUN_LOG names. Each run ends with an llm line (model calls made) and run finished, so a
script can assert that a stage made no model call. See Logging.
Scheduled runs and jobs
The web console (separate from the CLI) provides scheduled runs, a command/job runner that runs catalogue commands with the signed-in person's role, a dashboard, and tabs for semantics, conflicts, sources, review and integrity (guide).
Keeping generated docs current
ekos docs generate --layout curated --output doc
Evaluation
ekos eval run grades whole ekos ask answers with deterministic evaluators plus cache/CPU/RSS metrics; ekos eval history shows past runs. Retrieval quality has a separate CI-gated harness.