FAQ

Does Constant share memory between Codex and Claude?

No. There is no shared brain. Constant reads visible local session evidence and authors a session the target runtime can resume. See What carries.

Does a switch cost anything or call an API?

No. A switch runs zero model inference: no embeddings, no API calls, no summarization. It is a deterministic local text transformation that takes milliseconds. See How it works.

Will it overwrite my existing sessions?

No. Your originals are read as seeds and never written. Constant keeps its own projection pair per thread. See the Trust boundary.

Is my conversation sent anywhere?

No. Constant is local-first: no API proxy, no cloud. It reads and writes local session files on your machine.

What about secrets in my conversation?

Constant redacts common secrets (API keys, tokens, auth headers, emails) and strips runtime scaffold before anything crosses over.

Which versions are supported?

Codex 0.137.x and Claude Code 2.1.x. Session formats are private and can change between releases; run constant doctor to check.

Does it work inside tmux?

Yes, but Ctrl-B collides with tmux's own prefix. Use a different one:

constant host codex --prefix C-t

Can I carry tool calls and reasoning?

Not today. The conversation carries; tool and reasoning history does not, because the schemas are not 1:1 across runtimes. For coding sessions the narrative usually survives; the machine-level tool history does not.

Can I add another runtime?

OpenCode, Aider, and Gemini CLI are planned. Each one needs a single codec pair, to and from the neutral model.

Is it stable?

It is early, alpha software. Read the Trust boundary before using it on sessions you care about.