Claude Code Demo

This is the 3-5 minute Aionis demo for Claude Code and Cursor-style MCP clients.

It shows the core product difference:


related memory -> governed execution state -> bounded Agent context

Claude Code remains the Agent. Aionis is the memory Runtime beside it: record execution evidence, decide what can influence the next turn, and replay the decision later.

What The Demo Proves

Claude Code can reach Aionis through @aionis/mcp.
Aionis can record a failed branch and an accepted branch.
aionis_context compiles a governed execution-memory contract.
Failed history stays visible as counter-evidence, not direct instruction.
Agent Flight Recorder can replay what memory was visible without exposing raw prompt payload.

Install

Start from npm:


MINIMAX_API_KEY="your-key" npx @aionis/create@latest --provider minimax --quickstart sdk

Or start an existing Runtime:


export EMBEDDING_PROVIDER=minimax
export MINIMAX_API_KEY="your-key"
npm run -s lite:start

Add Aionis To Claude Code


claude mcp add --transport stdio --scope project aionis -- \
  npx -y @aionis/mcp@latest \
  --base-url http://127.0.0.1:3001 \
  --scope checkout-migration

Then check Claude Code:


/mcp

You should see tools such as:


aionis_context
aionis_record_step
aionis_flight_recorder
aionis_health

Demo Prompt

Use the prompt from the public repo:

claude-code-aionis-demo-prompt.md

The prompt asks Claude Code to call:


aionis_health
-> aionis_record_step failed legacy branch
-> aionis_record_step accepted current branch
-> aionis_context
-> aionis_flight_recorder

What To Show

In aionis_context, point to:

Field	Meaning
`use_now_memory_ids`	The accepted current route.
`inspect_before_use_memory_ids`	The failed legacy route as guarded evidence.
`memory_use_receipt`	Why each memory was exposed, downgraded, or suppressed.
`memory_admission_record`	Per-memory admission decisions for audit or dataset export.
`agent_prompt`	The bounded contract passed to Claude Code.

In aionis_flight_recorder, point to:

Field	Meaning
`agent_prompt_included: false`	Replay does not dump raw prompt payload.
`runtime_mutation: false`	Flight Recorder is read-only.
`use_now_memory_ids`	What direct-use memory the Agent could see.
`replay_sources`	Context, receipt, admission record, and feedback surfaces used for replay.

Short Talk Track


Most memory tools bring back related history. Aionis decides whether that
history is allowed to affect the next action.

Here Claude Code has two memories. One route failed. Another route was
accepted. A normal recall layer may retrieve both. Aionis compiles state: the
accepted branch goes into use_now; the failed branch stays visible only as
inspect-first counter-evidence.

That is the product difference. Aionis does not just remember. It adjudicates
state, compiles context, and leaves an audit trail.

Terminal-Only Proof


npm run -s runtime:quickstart:claude-code-mcp

Expected checks:


{
  "context_compiled": true,
  "should_continue_present": true,
  "failed_branch_guard_present": true,
  "memory_use_receipt_visible": true,
  "memory_admission_record_visible": true,
  "flight_recorder_replayed": true,
  "no_prompt_payload_in_recorder": true,
  "no_runtime_mutation_in_recorder": true
}