Lite config and operations
Use this page when you need to run Lite reliably, change local defaults, or debug startup behavior.
Startup commands
The normal local path is:
npm install
npm run lite:startThe Lite shell also exposes the app-local commands:
npm --prefix apps/lite run start
npm --prefix apps/lite run start:print-envActual startup chain
Lite starts through this chain:
apps/lite/scripts/start-lite-app.shapps/lite/src/index.jssrc/index.tssrc/runtime-entry.ts
That means the shell is thin and src/runtime-entry.ts remains the runtime truth for assembly and route startup.
Default Lite environment
The startup script sets these defaults unless you override them:
| Variable | Default |
|---|---|
AIONIS_EDITION | lite |
AIONIS_MODE | local |
MEMORY_AUTH_MODE | off |
TENANT_QUOTA_ENABLED | false |
RATE_LIMIT_BYPASS_LOOPBACK | true |
PORT | 3001 |
LITE_REPLAY_SQLITE_PATH | .tmp/aionis-lite-replay.sqlite |
LITE_WRITE_SQLITE_PATH | .tmp/aionis-lite-write.sqlite |
LITE_LOCAL_ACTOR_ID | local-user |
SANDBOX_ENABLED | true |
SANDBOX_ADMIN_ONLY | false |
Useful overrides
Change the local actor
LITE_LOCAL_ACTOR_ID=lucio npm run lite:startMove the SQLite files
LITE_WRITE_SQLITE_PATH=/tmp/aionis-write.sqlite \
LITE_REPLAY_SQLITE_PATH=/tmp/aionis-replay.sqlite \
npm run lite:startChange the port
PORT=3101 npm run lite:startUse an OpenAI-compatible embedding backend
Lite can also call an OpenAI-compatible embeddings endpoint instead of the default fake embedder. For providers that expose a /v1/embeddings surface, set:
EMBEDDING_PROVIDER=openai \
OPENAI_API_KEY=your-provider-key \
OPENAI_EMBED_BASE_URL=https://api.moonshot.cn/v1 \
OPENAI_EMBEDDING_MODEL=your-embedding-model \
npm run lite:startOPENAI_EMBED_BASE_URL defaults to https://api.openai.com/v1, but it can now point at any OpenAI-compatible embeddings host.
Use an OpenAI-compatible governance model
The review / governance path already accepts OpenAI-compatible chat-completions backends. For example:
GOVERNANCE_MODEL_CLIENT_TRANSPORT=openai_chat_completions_v1 \
GOVERNANCE_MODEL_CLIENT_BASE_URL=https://api.moonshot.cn/v1 \
GOVERNANCE_MODEL_CLIENT_API_KEY=your-provider-key \
GOVERNANCE_MODEL_CLIENT_MODEL=kimi-k2.6 \
WORKFLOW_GOVERNANCE_HTTP_MODEL_PROMOTE_MEMORY_PROVIDER_ENABLED=true \
REPLAY_GOVERNANCE_HTTP_MODEL_PROMOTE_MEMORY_PROVIDER_ENABLED=true \
TOOLS_GOVERNANCE_HTTP_MODEL_FORM_PATTERN_PROVIDER_ENABLED=true \
npm run lite:startPrint the effective startup environment
npm --prefix apps/lite run start:print-envSandbox operation modes
Lite exposes sandbox routes when SANDBOX_ENABLED=true.
The common local-safe preset is:
LITE_SANDBOX_PROFILE=local_process_echo npm run lite:startThat profile narrows the executor to:
SANDBOX_EXECUTOR_MODE=local_processSANDBOX_ALLOWED_COMMANDS_JSON=["echo"]
If you want sandbox routes gated behind the admin token again:
SANDBOX_ADMIN_ONLY=true npm run lite:startHealth and operational checks
Check runtime health
curl http://127.0.0.1:3001/healthLook for:
runtime.editionlite.route_matrixlite.storessandbox
Memory lifecycle routes
Lite now exposes local memory lifecycle mutations directly:
POST /v1/memory/archive/rehydratePOST /v1/memory/nodes/activate
From the SDK, those map to:
aionis.memory.archive.rehydrate(...)aionis.memory.nodes.activate(...)
Rebuild or validate before sharing
npm run -s build
npm run -s lite:test
npm run -s smoke:liteImportant Lite boundary assumptions
Lite is intentionally opinionated:
- auth is off by default
- tenant quota enforcement is off by default
- some server-only route groups, such as admin control, return structured
501 - Lite is designed for local-first use