APLEXICA

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.

Get Started View on GitHub
Read the docs
Platforms
macOS · Linux · Win
Storage
Local-first
Cloud
Zero-knowledge
aplexica · install
$ brew install Aplexica/tap/aplexica && aplexica setup --yes --install
Package manager · No account · Open Source v1.0.74

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 receive updates as they happen, while each agent keeps its native refresh behavior.

  • 04

    Forking workflows

    Branch a conversation across two agents. Compare answers side by side. Continue with whichever you prefer.

The Uninstall Test

A portability tool should survive its own removal.

Watch one conversation move from Claude Code to Codex and back, then see Aplexica removed. Both agents keep their native history because your context was never trapped inside Aplexica.

Install free Read the manifesto
aplexica · uninstall-test
56-second silent demonstration · On-screen annotations Claude Code ↔ Codex
Video summary
  1. A conversation created in Claude Code is synchronized into Codex.
  2. Codex resumes the conversation, adds a follow-up, and the updated history synchronizes back.
  3. Aplexica is uninstalled; its command is no longer available.
  4. Claude Code and Codex still resume with their native conversation histories intact.

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.

Aplexica filesystem-native architecture A three-layer stack: AI agents on top, the Aplexica canonical state in the middle, and each agent's native filesystem at the bottom. Coral dashed arrows show writes; cream solid arrows show reads. AGENTS · YOUR MACHINE Claude Code Codex Hermes APLEXICA · CANONICAL STATE ~/.aplexica agent-agnostic · versioned · forkable NATIVE FILES · EACH AGENT'S OWN FORMAT ~/.claude/ ~/.codex/ ~/.hermes/ writes reads
Fig 01 — Filesystem-native architecture

One install. Every agent.

  1. 01

    Install

    Use a supported package manager, then setup detects the agents you already have and installs the daemon and tray.

    brew install Aplexica/tap/aplexica && aplexica setup --yes --install

  2. 02

    Use any agent

    Keep working in whichever agent you prefer. Aplexica watches files in the background and propagates changes.

    aplexica status

  3. 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 <artifact> --from <event> --to-agent codex

We Take Pride in Our Numbers

By the Numbers.

Supported Agents · Growing

5

Supported Agents · Growing

Same-Machine Sync

Local

Same-Machine Sync

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.
Aplexica manifesto

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 & comparison

  1. oss

    Open Source

    Free, forever

    Learn more

  2. personal

    Personal

    $9 / user / month

    Learn more

  3. pro

    Pro

    $19 / user / month

    Learn more

  4. team

    Team

    $29 / user / month (3-user minimum)

    Learn more

  5. enterprise

    Enterprise

    Custom

    Learn more

Auditable, encrypted, yours.

  • 01

    Open source

    The Aplexica daemon is open source under AGPL-3.0. 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 free, forever. Add Cloud sync only when you need it. The two paths share the same canonical state — there's no migration.

Get Started Read the Docs