FAQ

The questions people actually ask before they install — which agents, which dependencies, what it writes, and whether it phones home. Short answers.

Which coding agents does it work with?

Any of them. Sirius is agent-agnostic: you hand it a shell command with --agent-cmd, and it runs whatever that command runs — Claude Code, another CLI agent, or your own script. The agent brings its own model; Sirius only supervises the loop around it.

sirius run --workers 3 --agent-cmd 'claude -p "fix the claimed issue"'

Do I really need both Ametrite and Hayvenhurst?

For the full loop, yes — Ametrite is where issues and claims live, and Hayvenhurst provides the code graph that Sirius locks against and selects tests from. Both are public and both run entirely on your machine. sirius doctor tells you exactly which one is missing or misconfigured before a run gets that far. Some commands, like filing a receipt with sirius link by hand, are useful even with no agents running.

Does Sirius call an LLM?

No. Sirius makes no LLM calls of its own — no cloud, no accounts, no API keys. Every model call belongs to the agent you point it at. Sirius is the supervisor loop, not another model.

What does it write to my machine?

Only its own ledger: .sirius/sirius.db, a SQLite audit log of runs, receipts, workers, and policy outcomes. It never writes Ametrite’s or Hayvenhurst’s databases — it talks to those strictly through their CLIs. Delete the ledger and no work is lost, only the trail of how it happened.

Which languages does it support?

Whatever Hayvenhurst understands, since locking and affected-test selection operate on Hayvenhurst’s code graph. The test command the gate runs is entirely yours — cargo test, bun test, pytest, anything that exits non-zero on failure.

Does it run on Windows?

Yes. Prebuilt binaries are published for five platforms — macOS (arm64, x64), Linux (x64-glibc, arm64), and Windows (x64) — each with a sha256 checksum and a Sigstore signature. See getting started to install.

Is the download safe?

The binaries are checksummed and Sigstore-signed, and the site says exactly that — no more. The checksum alone only catches a corrupted download; authenticity comes from the signature, whose certificate binds the artifact to the release workflow. A bad signature aborts the install, and so does a missing one.

Is it production-ready?

No — Sirius is early alpha (v0.1.0). The binary and its commands are implemented and covered by an offline test suite, with CI on macOS, Linux, and Windows, but it is young and evolving alongside the rest of the suite. Treat it as a tool to try on a repo you can supervise, not an unattended production service.