Quickstart
This guide gets a local Aionis Runtime running on your machine, then shows how to connect SDK, HTTP, MCP, AIFS, or native plugins. The goal is to put governed memory in front of a real Agent loop:
observe -> guide -> agent action -> feedback -> measure -> snapshotAionis runs beside your Agent host and compiles governed context for that host.
Prerequisites
| Requirement | Why it matters |
|---|---|
| Node.js 22+ | The Lite Runtime uses the Node SQLite runtime. |
| An embedding key | Required for stored-memory recall and recall-backed guide output. |
| A local shell | The Runtime runs beside your Agent host. |
The Runtime defaults to loopback for local Agent development.
One-command Install
The fastest path is the guided product CLI:
npx aionis setupThe setup command clones the Runtime, installs Runtime dependencies, writes a
local .env, and prints the next commands for starting the Runtime and
connecting an Agent host. Choose an embedding provider during setup so stored
memory recall works immediately.
SDK, MCP, AIFS, and native hook integrations are published from their own package repositories and connect to this Runtime through the product API.
For a non-interactive install with OpenAI-compatible embeddings:
OPENAI_API_KEY="your-key" npx aionis setup --provider openai --yesFor MiniMax embeddings:
MINIMAX_API_KEY="your-key" npx aionis setup --provider minimax --yesIf you already cloned the repository, use the local workflow below.
Claude Code Plugin
If your first target is Claude Code, install Runtime into a side directory:
npx aionis setup .aionis-runtimeThen start Runtime:
cd .aionis-runtime
npm run -s lite:startNow run Claude Code from your project:
claudeInside Claude Code, install the plugin:
/plugin marketplace add https://github.com/ostinatocc/aionis-claude-code
/plugin install aionis@aionis-claude-code
/aionis:onboardClaude Code receives Aionis context before prompts, and Aionis records execution evidence after tool use. The plugin installs user-level hooks and MCP tools, so new projects can use the same Runtime configuration.
Local Repository Setup
git clone https://github.com/ostinatocc/Aionis.git
cd Aionis
npm installConfigure embeddings:
export EMBEDDING_PROVIDER="openai"
export OPENAI_API_KEY="your-openai-key"MiniMax is also supported:
export EMBEDDING_PROVIDER="minimax"
export MINIMAX_API_KEY="your-minimax-key"Optional: run the SDK verification flow after the Runtime is configured:
npm run -s runtime:quickstart:sdkThat flow exercises the product path:
rememberwrites ordinary scoped memory.observeSteprecords execution evidence.guideForRolecompiles governed Agent context.feedbackFromOutcomeattributes the result to memory that was actually exposed by the guide.measureRunreports whether memory helped or created risk.snapshotRuncreates an operator-facing replay view.
What Success Looks Like
A successful run prints a JSON result with fields like:
{
"prompt_preview": "AIONIS EXECUTION CONTEXT...",
"execution_context_contract": "aionis_execution_agent_context_v1",
"memory_use_receipt_visible": true,
"used_memory_ids": ["mem_..."],
"snapshot_visible": true
}The important part is the contract shape:
| Field | Meaning |
|---|---|
prompt_preview | The Agent-facing context compiled by Aionis. |
memory_use_receipt_visible | The guide includes a compact audit of what was used or suppressed. |
used_memory_ids | The host can attribute outcome only to memory exposed by that guide. |
snapshot_visible | Operator replay can explain what Aionis admitted and why. |
Choose Your First Loop
| If you are building | Start with | What it proves |
|---|---|---|
| Claude Code | /plugin install aionis@aionis-claude-code | Plugin hooks inject context and record execution evidence automatically |
| Cursor, Zcode, or MCP-capable hosts | npx @aionis/mcp@latest --base-url http://127.0.0.1:3001 --scope-from workspace --workspace-id-store user | MCP tools can record steps and compile context |
| TypeScript or Node Agent | @aionis/sdk | Call observe, guide, feedback, measure, and snapshot from your host |
| Raw HTTP service | Runtime HTTP API | Use the public product endpoints without SDK helpers |
| Multi-agent system | Shared Runtime scope + agent IDs | Preserve execution state across planner, worker, verifier, reviewer |
| External memory backend | /v1/memory/govern | Govern Mem0/Zep/vector/markdown candidates before prompt use |
| Operator debugging | /v1/operator/snapshot | Read-only incident replay without prompt payload |
Source guide: AIONIS_QUICKSTART_MATRIX.md .
Minimal SDK Loop
import {
agentPromptFromGuide,
createAionisClient,
feedbackFromGuide,
} from "@aionis/sdk";
const aionis = createAionisClient({
baseUrl: "http://127.0.0.1:3001",
scope: "my-project",
});
await aionis.remember({
kind: "preference",
text: "Do not reuse failed migration branches as current instructions.",
});
const guide = await aionis.guide({
query_text: "Continue the migration from the current accepted path.",
context_mode: "compact_agent",
});
const prompt = agentPromptFromGuide(guide);
const result = await agent.run(prompt);
const usedMemoryIds = result.usedMemoryIds ?? [];
if (usedMemoryIds.length > 0) {
await aionis.feedback(feedbackFromGuide({
guide,
run_id: result.runId,
outcome: result.ok ? "positive" : "negative",
reason: result.summary,
used_memory_ids: usedMemoryIds,
used_surface: "use_now",
}));
}Common First-run Issues
| Symptom | Fix |
|---|---|
| Runtime cannot recall stored memory | Check EMBEDDING_PROVIDER and provider API key. |
| Guide has no useful history | Make sure tenant_id, scope, and Agent identity match between observe and guide. |
| Feedback is rejected | Aionis only accepts attribution to memory IDs exposed by that guide. |
| MCP client sees no tools | Confirm the MCP server points at the same Runtime base-url. |
| Ordinary facts are not showing up | Confirm embeddings are enabled, then add Substrate when you want stronger factual recall and durable evidence search. |
Next
- Follow the full Get Started path.
- Build with Execution Memory.
- Connect a TypeScript host with the SDK guide.
- Add Memory Firewall in front of Mem0 or a vector DB with the Memory Firewall guide.
- Use Claude Code or Cursor through MCP.