Code in your terminal.See what changed in the binary.
LOCI runs as a skill inside Claude Code. You write code, LOCI analyzes the compiled binary and surfaces execution signals in real time.
HOW LOCI WORKS
Three primitives.One quality gate.
Preflight audits the plan. Post-edit reviews the PR. Gate gives the human the final call.
STEP 01
PLANNING PHASE
Audit the plan.
When the AI agent plans a change, LOCI models the resulting binary before a line of code is written. Stack depth, timing, power, regressions, predicted from the plan.
1
Agent plans a change
2
LOCI models the incremental binary
3
Feedback: +3.4ms in AES_encrypt()
Fix the plan, not the PR.
STEP 02
CODE CHANGE
Review the PR.
Agent writes code and opens a PR. LOCI diffs the new binary against baseline and surfaces regressionsת before merge, at the binary level.
1
Agent opens PR
2
LOCI diffs the binary
3
Feedback: BLE throughput −8%
Every AI PR, reviewed at the binary.
STEP 03
HUMAN-ON-THE-LOOP
Human decides.
LOCI presents the evidence. You approve or block. Over time, LOCI calibrates to your quality bar and surfaces only what matters.
1
LOCI filters noise
2
Notifies what matters
3
You stay in control
Evidence on every PR. You control what ships.
WHAT LOCI MEASURES
Five signals. From the binary.No instrumentation.
LCLM reads the binary and predicts five classes of execution behavior. Each can be set as a budget, LOCI enforces it on every change.
Timing & Latency
Critical-path execution time, p95/p99 latency, tail amplification.
+3.4ms in AES_encrypt() on TLS handshake path
Throughput
Requests/sec, tokens/sec, instructions per cycle. Regressions against baseline.
BLE throughput −8% in ble_ll_tx()
Stack & Memory
Worst-case stack usage per function. Enforced against MISRA / AUTOSAR budgets. No instrumentation needed.
motor_ctrl() exceeds 2KB stack budget
Power & Energy
Execution cost, energy per operation, expensive paths.
Input-dependent branch skips bounds check in parse_packet()
All five signals run without executing your code. Learn how →
Execution Gates
12 gates. Binary in. Pass or Block out.
LOCI lifts two binaries to IR, builds an execution graph, and fires or clears each gate from the diff, before a single instruction runs. No execution required. No instrumentation. Just two ELF files.
CUSTOMER PORTAL
Your execution intelligence hub.ROI, signals, gates - all in one place.
Track regressions caught, debugging hours saved, and team-wide signal trends. Manage seats, plans, and quality budgets from a single dashboard.
INTEGRATIONS
Install in minutes.Runs where you work.
LOCI ships as a plugin, a cross-agent skill, a CI/CD action, and via AWS Marketplace. Same signals, any surface.
PLUGIN
Claude Code
/plugin install loci@claude-code-marketplace
Adds /loci:preflight and /loci:post-edit slash commands. Stop gate hook runs on every PR. Human approves in the terminal.
Nine skills – loci-preflight, loci-post-edit, exec-trace, stack-depth, memory-report, control-flow, trends, bug-report, and help. Works in Claude Code, Cursor, Codex, Copilot, Windsurf, and 15+ other agents. Audit-verified on skills.sh.
Not a GPT wrapper.A vertical model built for binaries.
LCLM | LOCI’s Large Code Language Model – is trained on billions of ASM blocks and real-time traces from open-source projects spanning IoT, networking, safety-critical, and industrial systems. It learns the execution behavior of compiled code, not just the syntax of source code.
That’s how LOCI models the binary before the code is written. And why LOCI’s signals are inspectable, explainable, and verifiable, every time.