Claude Code

Use this when you want Claude Code to use Aionis automatically, not only when it decides to call an MCP tool.

Aionis installs two layers:

Layer	Purpose
Claude Code hooks	Inject governed execution memory before prompts and record execution evidence after tool use.
Aionis MCP	Keep interactive tools available for context, handoff, snapshots, and Flight Recorder replay.

Install

Start a local Runtime first:


npx @aionis/create@latest
cd Aionis
npm run -s lite:start

Then install the Claude Code plugin:


/plugin marketplace add https://github.com/ostinatocc/aionis-claude-code
/plugin install aionis@aionis-claude-code
/aionis:onboard

Check everything:


/aionis:doctor

Then run Claude Code normally:


claude

What Gets Installed

Aionis plugin loads:


MCP server: aionis
Hooks: SessionStart, UserPromptSubmit, PostToolUse, PreCompact, PostCompact, SessionEnd
Commands: /aionis:onboard, /aionis:doctor, /aionis:status

Plugin source and releases: ostinatocc/aionis-claude-code .

After that, run claude from any project. Aionis derives a stable workspace scope per project without requiring manual project setup.

CLI fallback if you do not want to use Claude Code plugins:


npx @aionis/claude-code@latest onboard --base-url http://127.0.0.1:3001

Lifecycle


UserPromptSubmit
  -> Aionis guide
  -> governed execution context injected into Claude Code

PostToolUse / PostToolUseFailure
  -> Aionis observe
  -> execution evidence recorded

PostCompact / SessionEnd
  -> Aionis handoff
  -> continuation state preserved

This is stronger than MCP-only integration because Claude Code cannot forget to ask for context before the turn. The hook fires at the lifecycle boundary.

One-command Runtime + Claude Code

If you want the Runtime installer to also run Claude Code onboarding:


npx @aionis/create@latest .aionis-runtime \
  --with-claude-code \
  --claude-code-dir . \
  --claude-code-base-url http://127.0.0.1:3001

Use --claude-code-dir as the onboarding cwd when your Runtime checkout and Agent project are different directories.

Scope

Use --scope-from workspace for coding work. onboard stores stable workspace identities in the user’s Aionis Claude Code cache, so a new project can use Aionis without local hook files first.

Use --scope <name> only if your host already owns scope assignment.

When To Use MCP Only

Use MCP directly when your host does not support Claude Code hooks or when you want a manual tool-only trial. MCP exposes aionis_context, aionis_record_step, aionis_handoff, aionis_flight_recorder, and related tools.

Learn the MCP tool bridge.
Use Execution Memory for cross-session coding work.