End AI agent lock‑in.
Aplexica makes your memories, skills, and conversation history portable across every AI agent you use. Switch agents, run several in parallel, fork conversations across them, and try new agents the day they ship.
- Platforms
- macOS · Linux · Win
- Storage
- Local-first
- Cloud
- Zero-knowledge
curl -fsSL https://get.aplexica.com/install.sh | sh curl -fsSL https://get.aplexica.com/install.sh | sh winget install aplexica.aplexica The source code of your agent state. One canonical form. Any agent reads it natively.
Version it, fork it, sync it across machines — like Git, but for the state your agents actually run on.
Deterministic, lossless replication of agent state — not LLM-summarized briefing.
The next agent doesn't read about your previous session. It is the previous session, continued.
Works with
- Claude Code
- Codex
- Hermes
- OpenClaw
- Kilo
- Claude Code
- Codex
- Hermes
- OpenClaw
- Kilo
You started with one agent. Now you're stuck.
-
01.
Switching is expensive
Months of context — memories, skills, conversation history — live inside whichever agent you started with. Trying a new one means starting over.
The cost of moving your own context is a tax on every developer running AI agents.
-
02.
Multi-agent is painful
When you use more than one agent, you pay an N× maintenance tax keeping their context in sync. Updates land in one and not the other.
-
03.
You can't evaluate fairly
A new agent ships and you want to compare it head-to-head — but the second agent starts cold. The comparison is rigged before you begin.
Your context, in every agent.
Aplexica stores your agent state in a portable, agent-agnostic format and writes it natively into each agent's own files. Uninstall Aplexica tomorrow and every agent keeps its full state.
- 01
Portable memories
One CLI command converts your full state from any supported agent into any other agent's native format.
- 02
First-class adapters
Round-trip support for Claude Code, Codex, Hermes, OpenClaw, and Kilo — including conversation history.
- 03
Real-time sync
Multiple agents on the same machine see updates as they happen. p95 sync latency under two seconds.
- 04
Forking workflows
Branch a conversation across two agents. Compare answers side by side. Continue with whichever you prefer.
We don't move your data. Your agents do.
Other tools unlock you by storing your state on their server — moving the lock-in, not removing it. Aplexica writes into the files each agent already reads. Local-first by default. Optional zero-knowledge cloud sync when you need cross-device continuity.
One install. Every agent.
-
01
Install
A single command. The daemon detects the agents you already have and registers a per-agent adapter.
curl -fsSL https://get.aplexica.com/install.sh | sh
-
02
Use any agent
Keep working in whichever agent you prefer. Aplexica watches files in the background and propagates changes.
aplexica status
-
03
Switch or fork freely
Open a second agent and your full context is already there. Fork a conversation. Run agents in parallel.
aplexica fork codex
We Take Pride in Our Numbers
By the Numbers.
- Supported Agents · Growing
-
5
Supported Agents · Growing
- p95 Sync Latency
-
<2s
p95 Sync Latency
- Network Calls (Open Source)
-
0
Network Calls (Open Source)
- Agents per Machine
-
∞
Agents per Machine
- Cloud Encryption
-
E2E
Cloud Encryption
Your agent state is yours — by authorship, not by permission.
Open source forever. Cloud for everything else.
Five tiers. The free Open Source edition stays free, forever. Cloud tiers add backup, multi-device sync, governance, and Open Source when you need them.
Full pricing & comparisonAuditable, encrypted, yours.
-
01
Open source
The Aplexica daemon is open source. The whole thing is on GitHub. Audit what runs on your machine.
-
02
Zero-knowledge cloud
When you upgrade to Cloud, we still cannot read your content. End-to-end encrypted, by design.
-
03
Local-first
The Open Source edition makes zero network calls in its default configuration. Your machine, your data.
Stop starting over. Install free in under a minute.
The Open Source edition is shipping today. Add Cloud sync only when you need it. The two paths share the same canonical state — there's no migration.