Connect your MCP client
Each client runs the HYTHE stdio bridge and connects to your chosen server. The same configuration pattern works with a local Docker server or a dedicated server: choose the endpoint, provision the credential file, and assign a distinct agent identity.
Configuration and recovery
| Client | Configure the connection | Session recovery |
|---|---|---|
| Claude Code | Add the MCP bridge and install the HYTHE agent-kit plugin; bind the same identity in the bridge and Claude process | The plugin supplies session-start and post-compaction hooks; verify both with your installed version |
| Codex | Add the MCP server configuration and the matching agent-kit instructions | Use trusted session identity injection and the supplied recovery instructions; verify against your client version |
| Kimi | Configure the bridge; use the schema adapter required by your client/provider combination | Check your client's hook support; automatic compaction recovery is unverified in the recorded tests |
| Other MCP clients | Adapt the bridge command, arguments, and environment to the client's MCP configuration | Checkpoint, resume, and inbox calls can be exercised directly; automatic recovery needs client-specific support |
The quickstart provides concrete Claude Code and Codex examples. The agent kit includes integration files for supported clients. Configure one HYTHE integration per client to avoid conflicting bridge and plugin settings.
Dated compatibility checks
Reviewed 2026-09-07. These observations describe tested configurations; they do not guarantee every version of a client.
| Client configuration | Recorded evidence | Limits |
|---|---|---|
| Codex with HYTHE plugin | Bridge 0.2.0 initialized and listed 20 tools; v3 resume returned schemaVersion 3 and pointer selection on 2026-09-07 | Compaction recovery was historically exercised, but not rerun in this bridge check |
| Kimi with Moonshot schema adapter | Bridge 0.2.0 initialization and 20-tool listing checked on 2026-09-07 | The earlier memory canary was not repeated; compaction recovery remains unverified |
| Claude Code with HYTHE integration | Version 0.2.0 configuration inspected on 2026-09-07; earlier workflows documented in the tutorial | No new runtime or compaction test was performed during that inspection |
What the September checks did
The Codex check initialized a fresh bridge, listed tools, and resumed the recorded project with v3. The Kimi check explicitly requested initialization and schema-adapted tools/list. Bridges can attempt automatic registration during startup; these checks are not isolated proof of a complete application restart or a new compaction cycle.
Reproduce the transport checks with the quickstart, then test checkpoint/resume and recovery in your own client. These dated integration checks are distinct from public CI results.
Public contract evidence
Source tests support server contracts. They do not substitute for running each client and its recovery hooks.