Aplexica

At a glance

Aplexica translates local memory, skills, tool configuration and conversations between coding agents. It is worth a careful trial if you regularly switch between Claude Code and other assistants and keep rebuilding context. The tradeoff is a daemon reading and potentially writing their native state, so begin with a narrow route rather than syncing everything.

Good fit

Developers who want agent-state portability rather than another generated session summary. The documented design imports native formats into a canonical event store, then exports to enabled receivers. Conversation translation can make a session visible in another client, but it does not make the receiving model identical or give it the original agent’s capabilities.

Consider something else when

You only use one agent, cannot tolerate another copy of sensitive history or need verified hosted multi-device sync. The README’s optional relay link currently opens an electric-vehicle-tools coming-soon page, which does not establish that service’s availability. This guide concerns the local repository project. Agent versions and native database formats remain material compatibility constraints.

Start here

After evaluating installation and backups, use aplexica list to inspect imported artifacts before enabling a receiver. Add one narrow route and use aplexica rules test on an artifact to inspect the destination decision. Close clients that read their history database only at startup before enabling writes. A private tag alone does not restrict routing, and a later route change does not retract copies already sent.

Cost and requirements

The local core is declared AGPL-3.0, with a specific out-of-process plugin exception; it needs supported agents installed locally. Default local use is documented without an account. A source build may show a placeholder instead of the release web UI unless its separate bundle is present. Remote-plugin costs and access should be established separately rather than inferred from the local core.

Limits to know

No daemon, installer, backup, state import or cross-agent resume was executed for this guide. Selected source confirms native adapters, secret-store plumbing and an in-process recursion guard, not universally lossless translation or tested restoration. The dedicated Homebrew guide documents release packages with the UI, while an older quickstart still says that channel is pending. Prefer the current installation guide and verify the exact release. Treat source-format compatibility and recovery as acceptance tests for your own clients.

Related work

• Graphicle: retrieves cited project evidence instead of translating each agent’s native state (complement)