# End AI agent lock-in. Start conversation with one agent – continue with another > Source: > Published: 2026-09-02 15:40:30+00:00 **Cross-agent state portability for AI coding agents.** Your memories, skills, tools, and conversation history — portable across every AI coding agent you use. Switch agents without starting over. Run several side-by-side, all reading from the same context. Try the next agent the day it ships and lose nothing if you don't like it. Deterministic lossless replication of agent state — not LLM-summarized briefing.The next agent doesn't readaboutyour previous session; itisthe previous session, continued. **Aplexica is complete and usable as a local open-source application.** It does not require an account, a hosted service, or a network connection. Optional remote plugins are separate, user-selected integrations and are never required for local operation. For cross-device synchronization across your AI agents, visit [aplexica.com](https://www.aplexica.com/) to learn more. ``` brew install Aplexica/tap/aplexica aplexica setup --yes --install ``` **Uninstall Test.** A portability tool should survive its own removal. See the [Uninstall Test](https://www.aplexica.com/#uninstall-test). Today, picking an AI agent is a one-way door. The moment you commit to Claude Code or Codex or any other, you accumulate context that only *that* agent can read — memories about you, skills you've installed, MCP servers and subagents you've wired up, conversations you've built up. After a few weeks of real use, that context is what makes the agent useful. Switching means starting over. Running two in parallel means maintaining two siloed copies by hand. Trying a new agent that just launched means abandoning everything you've built. Aplexica eliminates that lock-in. It sits beside your AI agents and turns the artifacts they produce — memories, skills, tools, and conversation history — into portable, agent-agnostic state that **you own** and that **follows you to every agent you use**. With Aplexica installed you can: **Use every agent like it has always known you.** Memories, skills, and conversation history sync among all your installed agents within seconds.**Switch agents without losing a thing.** One command converts your full state from any V1 agent into any other agent's native format.**Fork a conversation across agents.** Start in one agent, branch into a second to try a different direction, keep both. Compare results.**Back up and restore.** Snapshot everything your agents know, restore it after a lost laptop or OS reinstall. After Aplexica is installed and the daemon is running, try this quick conversation sync check: - Open the local Aplexica web UI and go to **Routing rules**. - Choose **Add from preset** and create the**Sync everything everywhere** routing rule template. - Open Codex and ask: ``` What is the largest planet in our solar system? ``` - Wait for Codex to answer. - Open another terminal window, run `claude` , then type`/resume` . - In Claude Code's conversation list, select the conversation named like: ``` Codex: what is the largest planet in our solar system? ``` Claude Code should resume the conversation that started in Codex, using its own native conversation history. For Hermes, you may need to close Hermes and open it again before the refreshed conversation list appears. The same `codex` and `claude-code` adapters also serve their installed desktop apps. After writing a Codex rollout, Aplexica asks Codex's own app-server to load it; when that best-effort registration succeeds, Codex's normal thread inventory can discover it without Aplexica touching private app state. Claude Code Desktop shares configuration and project state, including guarded mirrors for its default active worktrees, but Anthropic keeps its Desktop conversation list separate. On macOS and Windows, resume the synchronized artifact in the CLI and run `/desktop` for the supported app handoff. The CLI and desktop surfaces are detected independently; either can be used by itself. The daemon retains candidate roots for these two adapters and rechecks surface availability at runtime, so installing the CLI or desktop app later activates synchronization without requiring the other surface to be present. Activation completes the native safety snapshot before first synchronization and backfills recent peer-device conversations using the configured history limit without synthesizing duplicates of locally authored sessions. Aplexica installs three executables together: `aplexica` — CLI, daemon, local web UI server, and setup wizard.`aplexica-status` — status helper the tray spawns, so process monitors can tell the watcher apart from the daemon.`aplexicatray` — menu bar / system-tray companion. The local web UI is compiled into `aplexica` itself in release builds; there is no separate UI package to install. **macOS / Linux — Homebrew:** Homebrew is a live channel at 1.0.74. Full steps: [brew.md](/Aplexica/Aplexica/blob/main/docs/install/brew.md). ``` brew install Aplexica/tap/aplexica aplexica setup --yes --install ``` **Debian / Ubuntu — .deb:** follow the exact-version download and verification steps in [apt.md](/Aplexica/Aplexica/blob/main/docs/install/apt.md), then: ``` aplexica setup --yes --install ``` **Windows (release archive):** download `aplexica-1.0.74-windows-amd64.zip` or `aplexica-1.0.74-windows-arm64.zip` from the [v1.0.74 release](https://github.com/Aplexica/Aplexica/releases/tag/v1.0.74), verify it following [verify.md](/Aplexica/Aplexica/blob/main/docs/install/verify.md), unzip it into a folder you own, and run `aplexica.exe` or `aplexicatray.exe` from that folder. Full steps, including start-at-logon: [windows.md](/Aplexica/Aplexica/blob/main/docs/install/windows.md). Then: ``` aplexica setup --yes --install ``` That one `setup` command registers and starts the daemon, installs and launches the tray when it is enabled (the default on every supported desktop OS), and brings up the local web UI. Adapters are built in and auto-discover your agents. | Platform | Channel | Status and guide | |---|---|---| | Debian / Ubuntu | Versioned `.deb` | Available; | [direct.md](/Aplexica/Aplexica/blob/main/docs/install/direct.md)[build.md](/Aplexica/Aplexica/blob/main/docs/install/build.md)[brew.md](/Aplexica/Aplexica/blob/main/docs/install/brew.md)[windows.md](/Aplexica/Aplexica/blob/main/docs/install/windows.md)[update.md](/Aplexica/Aplexica/blob/main/docs/install/update.md)Aplexica release authority is a non-exportable AWS KMS key—not GitHub, a CDN, a package registry, or a maintainer workstation. Each release ships a KMS-backed cosign signature over `SHA256SUMS` and a KMS-backed, public-policy-checked SLSA v1 provenance bundle. GitHub Actions receives only a short-lived AWS session for the isolated signing job; the publication job has no signing authority. Verify `SHA256SUMS` with the independently distributed `aplexica-release.pub` , check the selected artifact digest, and verify its provenance and semantic policy. GitHub Releases, a NAS, USB, or a local HTTP directory may all transport the same authenticated bytes. The exact commands are in [Verify a release](/Aplexica/Aplexica/blob/main/docs/install/verify.md). Never pipe downloaded text to a shell or PowerShell expression. Development builds use the public Go source directly: ``` git clone https://github.com/Aplexica/Aplexica.git cd Aplexica make build make tray ``` The local web UI is replaced by an explanatory placeholder unless `internal/web/embed/dist-local/` contains a Portal bundle. Release-style builds add `-tags release` , which makes the daemon fail closed when that bundle is missing; development builds can omit the tag. See the [source-build guide](/Aplexica/Aplexica/blob/main/docs/install/build.md) for tests, cross-compilation, and local installation. ``` # 1. Install Aplexica using one of the available methods in docs/install/. # 2. Register and start the daemon, install tray autostart, launch the tray, and # bring up the local web UI. The tray is enabled by default on every OS. aplexica setup --yes --install aplexica status # (Run `aplexica setup` with no flags for an interactive walkthrough.) # 3. Watch the canonical store aplexica list # nothing yet — agent state hasn't been imported # 4. Add at least one matching routing rule first; docs/quickstart.md gives # the exact TOML and `aplexica rules add` command. Then enable receivers. aplexica sync enable --all # or name specific agents aplexica daemon reload # 5. Let your agents create artifacts naturally. Once Claude Code, # Codex, or any other supported agent writes its native file, the # daemon imports it within ~2 seconds and fans it out to every # enabled agent's native location. # 6. Anywhere along the way: aplexica list # see every artifact across kinds aplexica show # inspect one aplexica conflicts list # any divergent writes that need your decision aplexica branch list # branch topology if you've forked ``` A guided walkthrough from install to working two-agent sync lives at [docs/quickstart.md](/Aplexica/Aplexica/blob/main/docs/quickstart.md). Five V1 agents, four artifact kinds, full bidirectional translation: | Agent | Surfaces | Vendor | Memory | Skill | Conversation | Tool | Canonical conv (`acf.conversation.v1` ) | |---|---|---|---|---|---|---|---| | Claude Code | CLI + Desktop | Anthropic | ✅ markdown | ✅ skill.md | ✅ session.jsonl | ✅ MCP (.mcp.json) | ✅ | | Codex | CLI + Desktop | OpenAI | ✅ AGENTS.md | ✅ skill.md | ✅ session.jsonl | ✅ MCP (config.toml) | ✅ | | Hermes | CLI | Nous Research | ✅ MEMORY.md / USER.md | ✅ skill.md | ✅ SQLite (state.db) | ✅ MCP (config.yaml) | ✅ | | OpenClaw | CLI | community | ✅ MEMORY/AGENTS/CLAUDE/DREAMS.md + memory/YYYY-MM-DD.md | ✅ skill.md | ✅ session JSONL | ✅ MCP (openclaw.json) | ✅ | | Kilo Code | CLI | Kilo | ✅ AGENTS.md / AGENT.md | ✅ skill.md | ✅ SQLite (`kilo.db` ) + `kilo import` | ✅ MCP (kilo.jsonc) | ✅ | Adding a new agent is one ~80-line adapter package. See [docs/adapters/](/Aplexica/Aplexica/blob/main/docs/adapters) for per-agent specs and [internal/adapter/openclaw/](/Aplexica/Aplexica/blob/main/internal/adapter/openclaw) for a reference implementation. Each supported agent has an **adapter** that translates between its native format and the **Aplexica Canonical Format (ACF)** — an append-only event log per artifact, hash-chained for integrity, plus a typed payload. State lives in the user-owned **canonical store** at `~/.aplexica/store/` . The daemon, run through `aplexica daemon` , watches each agent's native location and runs the import → fan-out cycle on every change. Secrets live in a separate protected store and never enter the canonical event log. The whole stack is **deterministic and lossless** — no LLM summarization, no consolidation, no briefing layer. The public BRDs in [docs/](/Aplexica/Aplexica/blob/main/docs) describe the canonical format and local product requirements. Power-user workflows are first-class: **Branches.**`aplexica fork --from --to-agent codex` creates a divergent branch; the source agent's view is unchanged.`aplexica log --graph ` renders the topology.`aplexica merge --from --into ` reconciles.**Selective sync.**`aplexica tag add work` then a TOML rule like`route.agents = ["claude-code", "codex"]` routes that artifact only to your work agents.`aplexica rules test ` explains every routing decision.**Stays-local content.** Tags are metadata, not policy, and no routing rules are active by default. To keep a`private` memory on its originating agent, add an explicit rule matching that tag with`route.agents = ["__originatingAgent__"]` and`route.remote = "exclude"` ; the[quickstart](/Aplexica/Aplexica/blob/main/docs/quickstart.md#8-selective-sync)gives the complete rule and safe replacement sequence. Full reference: [docs/04-brd-forking-and-merging.md](/Aplexica/Aplexica/blob/main/docs/04-brd-forking-and-merging.md), [docs/05-brd-selective-sync-and-routing.md](/Aplexica/Aplexica/blob/main/docs/05-brd-selective-sync-and-routing.md). `aplexicatray` is a cross-platform menubar / system-tray / SNI indicator that reflects daemon state at a glance: | Icon | Meaning | |---|---| | Idle | Daemon up, no recent activity | | Active | Snapshot ticks arriving | | Paused | Daemon up but quiet for ≥ 5 minutes | | Conflict | Unresolved conflicts (overrides other states) | | Error | Daemon not reachable | Right-click for `Pause / Resume` , `Show Conflicts` , `Open Logs` , `Pending Projects` , and `Open Aplexica` . Packaged installs include it, and `aplexica daemon install` wires it to start with Aplexica on every desktop OS unless you explicitly opt out. | Path | Purpose | |---|---| | [docs/user-guide.md](/Aplexica/Aplexica/blob/main/docs/user-guide.md)[docs/quickstart.md](/Aplexica/Aplexica/blob/main/docs/quickstart.md)[docs/install/](/Aplexica/Aplexica/blob/main/docs/install)[docs/01-brd-backup-restore.md](/Aplexica/Aplexica/blob/main/docs/01-brd-backup-restore.md)[docs/02-brd-format-adapters.md](/Aplexica/Aplexica/blob/main/docs/02-brd-format-adapters.md)[docs/03-brd-local-realtime-sync.md](/Aplexica/Aplexica/blob/main/docs/03-brd-local-realtime-sync.md)[docs/04-brd-forking-and-merging.md](/Aplexica/Aplexica/blob/main/docs/04-brd-forking-and-merging.md)[docs/05-brd-selective-sync-and-routing.md](/Aplexica/Aplexica/blob/main/docs/05-brd-selective-sync-and-routing.md)[docs/09-security-and-trust-model.md](/Aplexica/Aplexica/blob/main/docs/09-security-and-trust-model.md)[docs/10-non-functional-requirements.md](/Aplexica/Aplexica/blob/main/docs/10-non-functional-requirements.md)[docs/adapters/](/Aplexica/Aplexica/blob/main/docs/adapters)[docs/plugin-protocol-spec.md](/Aplexica/Aplexica/blob/main/docs/plugin-protocol-spec.md)[docs/plugin-author-guide.md](/Aplexica/Aplexica/blob/main/docs/plugin-author-guide.md)[CHANGELOG.md](/Aplexica/Aplexica/blob/main/CHANGELOG.md)Aplexica welcomes contributions. Start with [CONTRIBUTING.md](/Aplexica/Aplexica/blob/main/CONTRIBUTING.md) for branch / commit / test conventions, then open a PR. - Contributions are accepted under a **Contributor License Agreement**. The CLA grants Aplexica the right to distribute your contribution under AGPL-3.0*and*under a separate commercial license. A bot comments on your first PR with the signing link; see[CONTRIBUTING.md](/Aplexica/Aplexica/blob/main/CONTRIBUTING.md)for the full terms. - Bug reports → [issues](https://github.com/Aplexica/Aplexica/issues)with the`bug_report` template. - Security vulnerabilities → **do not file a public issue**; see[SECURITY.md](/Aplexica/Aplexica/blob/main/SECURITY.md)for the responsible-disclosure address and policy. - Community conduct → [CODE_OF_CONDUCT.md](/Aplexica/Aplexica/blob/main/CODE_OF_CONDUCT.md)(Contributor Covenant 2.1). Aplexica OSS is licensed under the **GNU Affero General Public License v3.0** ([LICENSE](/Aplexica/Aplexica/blob/main/LICENSE)). The AGPL-3.0 plugin-boundary stance is documented in [LICENSE-EXCEPTIONS.md](/Aplexica/Aplexica/blob/main/LICENSE-EXCEPTIONS.md): third-party plugins running in their own process and communicating with the `aplexica` daemon via the documented JSON-RPC stdio protocol are **NOT considered derivative works of the daemon** for AGPL-3.0 purposes. See that document for the full legal statement. Aplexica is under active development. Use the [release page](https://github.com/Aplexica/Aplexica/releases) and [CHANGELOG.md](/Aplexica/Aplexica/blob/main/CHANGELOG.md) for shipped-version status.