Appearance
Lite Public Beta + Server Core
Agents keep rediscovering the same work.
Aionis gives agents execution memory.
The next session resumes the work instead of rereading the repo, rebuilding the mental model, and re-explaining the same reasoning.
Aionis is execution continuity for agents: durable memory, exact handoff recovery, replayable workflows, and inspectable evidence.
Execution continuityExact handoff recoveryReplayable workflowsAuditable evidence
Real continuation testOpen source
pallets/click
Aionis resumed a real repository task from stored execution memory instead of starting from zero.
77%lower output tokens
33%lower total tokens
What resumes
Prior handoffs, replayable run state, decisions, and evidence come back without rereading the whole repo.
What becomes reusable
Successful work can become playbooks, exact handoffs, and inspectable traces instead of throwaway prompt history.
Start here
Fastest path
Start with Lite
Run Aionis locally with SQLite, validate continuity, replay, and exact handoff recovery, and get to first value quickly.
Best for local evaluation, single-user workflows, and low-friction trials.Best integration pathUse it with Codex
Connect Aionis to coding-agent workflows so new sessions can recover context instead of rebuilding it from scratch.
Best for local coding agents, MCP, and continuity-sensitive handoffs.Production pathMove to Server
Adopt the self-hosted production path when you need stronger deployment discipline, operator workflows, and team-facing runtime behavior.
Best for self-hosted production and operational rollout.What changes when agents stop restarting
Continue work instead of reconstructing it
New sessions can resume from stored execution state, exact handoffs, and replay traces instead of rereading the repo and rebuilding the patch plan.
Recover exact handoffs
Bring back the prior task summary, exact handoff text, risk notes, and acceptance checks when continuity matters.
Turn successful work into replayable paths
Replay and playbooks turn one-off agent runs into reusable workflows instead of throwaway prompt history.
Keep runtime evidence inspectable
Decision IDs, commit URIs, replay runs, and handoff artifacts make the work auditable instead of opaque.
How it works
Evidence, not promises
Continuity
Cross-session work continues instead of resetting
Public A/B runs already show the difference between restarting from prompt history and resuming from execution memory.
CostReal token reduction on a larger open-source repo
pallets/click showed 77% lower output tokens and 33% lower total tokens in continuation-sensitive work.
Lite is real, local, and usable now
Lite is not a concept demo. It is the fastest path to trying Aionis locally with a repeatable beta workflow.
Browse the docs
Understand the model
Read the product model, the core concepts, and why Aionis is more than token optimization.
Get to first value fast
Start Lite, write memory, recall it later, and validate exact handoff recovery and replay identifiers.
Integrate with coding agents
Use Codex, MCP, and SDK flows when your first use case is local coding agents and continuity-sensitive work.
Wire the APIs
Move from guide-level understanding to memory, policy, replay, and endpoint contracts for real integrations.