Under 5 minutes. No instrumentation. No runtime overhead.
Five ways in. Same guardian agent, same execution signals. Here's each surface.
/plugin install loci@claude-code-marketplace
SUPPORTED WORKFLOWS
Preflight during planning (Step 01)
Post-edit on every PR (Step 02)
Human-on-the-loop gate at merge (Step 03)
npx skills add auroralabs-loci/loci-claude
Claude Code · Cursor · Codex · GitHub Copilot · Windsurf · Gemini · Goose · AMP · Antigravity · Cline · Droid · Kilo · Kiro CLI · OpenCode · Roo · Trae · VSCode · ClawdBot
- uses: auroralabs/loci-action@v1 with: gate: post-edit fail-on-regression: true
WHAT YOU GET
LOCI Gate — Post-Edit Review
⚠️ Timing regression: +3.4ms in AES_encrypt() (p95, TLS handshake path)
⚠️ Throughput regression: BLE throughput −8% in ble_ll_tx()
✓ Stack budget: within 2KB limit
✓ Power: no regression detected
Approve or block below.
curl -X POST https://api.loci.dev/v1/gate \ -H "Authorization: Bearer $LOCI_API_KEY" \ -F "binary=@./build/output.elf" \ -F "baseline=@./build/baseline.elf" \ -F "gate=post-edit"
Enterprise teams with strict CI/data requirements
Safety-critical systems (MISRA, AUTOSAR, ISO 26262)
Platforms that aren’t GitHub-native
Enterprise teams with AWS procurement workflows
Organizations consolidating vendor billing through AWS
Teams requiring cloud-native deployment options
Five install paths — but when do the execution signals actually fire in your pipeline?
Code
Incremental .so compile
Function-level signal as you type
Build
Full binary pass
All 5 signals, whole program
Test
Tail & edge case prediction
Paths your suite never reaches
Merge
PR gate
Blocks if signals exceed baseline
Each stage is independently useful, or run the full layer for continuous coverage.
Four pipeline stages, each independently useful. Here's how fast you can get started.
GET STARTED
A minimal working install looks like this:
Install the plugin or skill.
/plugin install loci or npx skills add auroralabs-loci/loci-claude
Authenticate.
Run loci auth and log in with your Aurora Labs account. Free tier available.
Point it at your repo.
LOCI auto-detects compiled artifacts (.elf, .so, .wasm). No config required for most projects.
Run preflight on a change.
/loci:preflight or open a PR — LOCI analyzes automatically.
Review and approve.
Human-on-the-loop. You decide what ships.
No code changes. No instrumentation. No new build steps. No long onboarding.
Five minutes to install. But what if your compiled binary can't leave your network?
FOR ENTERPRISE
LOCI is deployed in safety-critical systems across automotive, industrial, and infrastructure. Enterprise installs support on-prem deployment, SSO, audit logging, and strict data residency controls.
Full air-gapped option. No binary artifacts leave your environment. LCLM runs entirely inside your VPC.
SAML, OIDC, and custom IdP integration. Role-based access control for gate approvers and policy admins.
Every gate decision logged, who approved, what signals fired, which baseline was compared. Exportable for compliance audits (SOC 2, ISO 27001, MISRA traceability).
No customer binaries in LCLM training. Gate analysis runs on your binaries in your region. No cross-tenant data exposure.
SaaS or on-prem — same execution signals, same compiled binary analysis. Ready to start.
Under 5 minutes. Free to try. No instrumentation.