Troubleshooting
Ctrl-B does nothing
If you are inside tmux, Ctrl-B is tmux's own prefix and never reaches Constant.
Pick another prefix:
constant host codex --prefix C-tCodex also uses the Kitty keyboard protocol, so Ctrl-B can arrive as an escape
sequence. Constant handles both encodings; confirm what your terminal sends with
constant keys.
"Failed to resume" in the target runtime
The target's session loader is a strict parser. The usual cause is a runtime
version outside the validated range (codex 0.137.x, claude 2.1.x), since
session formats are private and can change between releases. Run constant doctor to check your versions.
The terminal looks broken after detaching
Constant restores terminal modes (alt-screen, mouse, bracketed paste, Kitty) on
exit. If a child process left the terminal dirty, run reset to recover.
The carried thread is too long
A long conversation can exceed a smaller runtime's context window on carry. The carry is the full thread; summarization-to-fit is not yet implemented.
A /resume to a different conversation is not followed
If you /resume an unrelated conversation inside the hosted child mid-thread,
Constant keeps carrying the tracked pair rather than risk hijacking the carry
with someone else's session. It is indistinguishable from an unrelated
same-directory session.
Tool history did not carry
That is by design. Constant carries the conversation, not tool calls or reasoning. See What carries.
Still stuck?
Open an issue on GitHub.