Connect subscription-backed models, API-based providers, local agents, and custom runtimes. Charles keeps them working as one system.
C.H.A.R.L.E.S.
Cognitive Hybrid Assistant forReasoning, Logic, and Empirical Synthesis.
Every brain the job needs. One Charles. Switch between Claude Fable 5 and GPT Sol without losing context, while one durable identity keeps the memory, skills, and objective intact. Connect your Claude, your Codex, and other runtimes for one super agent.
Switch the underlying brain without losing Charles, his memory, his operating context, or the way he works with you.
Charles can divide work across runtimes, verify what comes back, and deliver one coherent, accountable outcome.
More than a runtime router
One agent. Every place you work.
C.H.A.R.L.E.S. is not a product line or a collection of bots. He is one durable AI agent who knows your stack, holds one governed memory, and can move between the runtimes best suited to the work—or use several hands at once—without leaving the job behind.
Mission Control, E:Voice, and AERIS OS are his homes. The surface changes. Charles does not.
Charles
One memory. Many hands.
Runtimes are hands, not replacements. Charles can switch hands mid-job or direct several at once while his identity, governed memory, skills, objective, and accountability remain intact.
Underneath the partnerMemory below.
Memory below.
Accountability above.
Charles is the one you talk to. Two systems sit under him and keep the work honest across every runtime he enters: the AERIS Node holds the durable, governed memory, and AERIS Overwatch holds the record of what was actually done. Neither is a chat log, and neither depends on you remembering to write things down.
Governed memory that reads back in
The Node is a living graph of your work—decisions, preferences, systems, people, and the standing state of every project—stored with provenance and kept under your control. It is local-first and it belongs to you, not to whichever model happens to be answering.
Before a turn starts, the Node selects only the entries relevant to what you just said and injects them as context, leaving a retrieval trace of exactly what was pulled and why. Suppress an entry and it stops being used; restore it and it returns. That is how Charles can change brains mid-job and still know the job.
How the Node works →Evidence over every runtime
Overwatch is the append-only ledger of the work itself. It separates three things most assistants blur together: what is active, what the runtime claims it did, and what independent verification confirms. Every job carries a lifecycle state, redacted evidence, replay after a restart, and a durable terminal receipt.
It runs whether or not you are watching. Because Overwatch is already recording outcomes as they happen, the durable facts it produces are written back into the Node in the background—no summarisation ritual, no end-of-session note-taking.
See Overwatch →01 · Work runsCharles executes through whichever runtime fits the job—his own or one you connected.
02 · Overwatch recordsActivity, runtime claims, and verified evidence land in the ledger while the work is still moving.
03 · The Node is populatedDurable outcomes are written into governed memory in the background, with provenance attached.
04 · Context is injectedOn the next request the Node pulls what is relevant in real time and loads Charles before he answers.
The loop is the point. Overwatch writes into the Node in the background while the Node reads out of it in real time—so the runtime can change, the session can end, and the machine can restart without the work losing either its memory or its receipts.
Where he livesOne Charles.
One Charles.
Three homes.
Not three products pretending to know you. One operating partner, carrying the same memory and working context wherever you meet him.
Mission Control
Charles’s seat beside the owner: a private, live view of the company where he knows the products, infrastructure, launches, and the work already in motion.
Open Mission Control →E:Voice
Your hands-free home for Charles. Speak the request, keep moving, and let the same agent turn it into real work against the stack he already understands.
Explore E:Voice →AERIS OS
His orchestration home on the desktop—where Charles can inspect, build, verify, and bring the right runtime or runtimes to bear on a larger job.
Explore AERIS OS →Hands-free
Build software by voice.
Tell Charles what needs to change, ask what he found, and keep the work moving without living at the keyboard. It brings the voice-first idea behind E:Voice into software building.
Downloads
Choose your track.
Charles is in pre-launch. Preview downloads require sign-in, and access is granted to each person individually.
Preview
For people invited into pre-launch access. Sign in to the portal to see whether access has been granted to your account and get the current download.
Sign in for PreviewStable
The stable release track is not available yet. No version, package, or date is being promised here.
Coming soonGoogle Play
Android release
The public Google Play listing is coming soon. This is a neutral placeholder, not an official store badge.
Coming soon