The Sigilix Models
Sigilix is an AI lab. The CLI and agent surfaces run on Sigilix’s own model line — Boreas, Pyroeis, and Astraeus, memory-native models we tune for engineering work and for your organization’s code and memory. Four tiers, one contract:
| Model | Tier | Status |
|---|---|---|
| Boreas | Light — the everyday coding agent | Available — the CLI default |
| Pyroeis | Base — a stronger tier for harder changes | Available |
| Astraeus | Premium — the top agentic tier, for the hardest multi-file and subtle-logic work | Available |
| Phanes | The top of the lineup | Coming soon |
The hosted PR review ensemble is a different lane: each review specialist runs a model tuned to its role, behind cross-provider fallback — see The Ensemble. The lineup on this page powers the CLI and agent surfaces.
Tuned models, one contract
Every tier is one of our own tuned models, and every tier runs the same agent contract — the loop through which the rest of the platform fuels the model with real repository context on each run:
Ground before edit
Before touching code, the agent pulls a repo-aware context packet — the repo map, relevant symbols, and prior learnings — from the earned-context layer, so changes are grounded in your actual repository instead of guessed.
Edits with discipline
Minimal patches, verified with your project’s own tests and linters. Pure-logic edits can carry proof from a sealed sandbox check.
Knows the blast radius
Impact-analysis tools surface what an edit affects — callers, dependents, and a review of the change — before it lands. See The Code Graph & Blast Radius.
Remembers
Compounding per-developer, per-repo memory that improves every run — layered with your org’s learnings. See Review Memory.
The tiers share this contract and differ in the strength of the tuned model driving it: Boreas for everyday work, Pyroeis for harder changes, Astraeus for the hardest multi-file and subtle-logic work.
How they’re served
The line is served through Sigilix’s authenticated gateway — you authenticate to Sigilix (sigilix login) and never manage provider keys or serving infrastructure.
- Ordered failover. Each model has an ordered chain of independent serving backends. Failover triggers only before the first response byte (connection failures, timeouts, upstream errors) — a genuine request error is returned, not retried into confusion.
- Never silent. Every response records which backend served it, so a fallback is observable, not invisible.
- Availability guarded. Per-model daily ceilings protect the service from runaway usage instead of degrading everyone’s latency.
Using them
sigilix models # list the models available to your account
sigilix # the interactive UI runs on the lineup by defaultPrefer to run on your own provider account instead? See Bring Your Own Key — a paid-tier feature. Note the trade-off documented there: Sigilix’s hosted models are tuned to prioritize your injected context and memory most reliably, so BYOK trades that grounding guarantee for model choice and your own billing.