Installing the LOCI Claude Plugin

Prerequisites

Requirement	Version	Required for
Claude Code	latest	Everything
Python	3.12+	The loci CLI (local ELF/build analysis)
uv	any	Installs the loci CLI as a tool. Install this yourself — the plugin checks for it and gives you the install command if it's missing.
jq	any	Session hooks. Install this yourself — the plugin checks for it and gives you the install command if it's missing.
Compiled binaries	.elf / .o / .axf	All skills

Cross-compiler (one required, depending on your target):

LOCI Target	CPU / Silicon	Default cross-compiler
armv6-m	ARM Cortex-M0+	arm-none-eabi-gcc
armv7e-m	ARM Cortex-M4	arm-none-eabi-gcc
aarch64	ARM Cortex-A (A53)	aarch64-linux-gnu-gcc
tc399	Infineon TriCore TC3xx	tricore-elf-gcc

These are the only 4 architectures LOCI's analysis backend supports. Rust sources are also supported (via rustc — LOCI needs the matching rustup target add triple for your LOCI target); a project can mix C/C++ and Rust.

Inside Claude Code:

Step 1 — Add Marketplace

/plugin marketplace add auroralabs-loci/loci-claude

Step 2 - Install plugin

/plugin install loci@loci

There is no separate CLI download step. The loci command-line tool installs itself automatically in the background the first time a Claude Code session starts, using uv.

You can also do this through the interactive menu instead of typing the commands directly: run /plugin, then go to Discover → LOCI and Install → LOCI. Both paths do the same thing.

Step 3 — Reload plugin

/reload-plugins

Required. Claude Code needs this to pick up the newly installed plugin's hooks and skills in your current session — without it, LOCI won't be active yet even though the install succeeded.

Step 4 — Run plugin

/loci:setup

Required. This installs the loci CLI (as a uv tool) and verifies your environment — compiler, architecture, and build system detection, plus the health checks covered in Troubleshooting. It's idempotent and safe to re-run any time; if uv or jq aren't already on your system, it tells you the exact install command for your OS instead of installing them for you (they need root/an interactive password prompt).

The plugin's SessionStart hook also attempts this install automatically in the background on every session start, but running /loci:setup explicitly is how you confirm it actually succeeded before relying on any skill.

You're done

Once setup reports healthy, the plugin is ready to use. Next, sign in — then try any on-demand skill (e.g. ask "What's the execution cost of main()?") or just start editing C/C++/Rust source and loci-post-edit will run automatically.

Next steps

• Authenticating the LOCI Claude Plugin — sign in before using any analysis skill

• Skills Reference — what each skill does

• Troubleshooting — if the install doesn't finish or a skill won't respond