Import from other clients

If you have used other agent clients before, Klaus can detect the ones installed on this machine and bring over content whose format it can verify (Settings → Import). Importing copies data; it never modifies the original client's data.

• Three clients are detected: Claude Code, Qoder, Codex. Detection relies on the fixed directories each of them uses on this machine, so anything not installed simply does not appear. The page only lists sources with a verified format — a client whose format has not been verified is left out of the list entirely, rather than failing halfway through an import.
• Four kinds of content can be imported: historical sessions, skills, MCP servers, and project root directories. You can import everything at once or pick items individually.
• Explicitly not imported: settings, hooks, commands, sub-agents, instruction files (AGENTS.md and the like), and enabled plugins. None of these have a trustworthy cross-client conversion today — hook and command semantics are not equivalent between clients, and force-converting them would leave you with something that silently runs wrong, so Klaus reports an error instead of guessing. Qoder's native chat format is also not supported yet.
• Where things land: skills are copied into ~/.klaus/skills (or the project's .klaus/skills), and a directory with the same name that already exists is skipped, with a notice to you; session records are converted into Klaus's own format, written into the session storage root ~/.klaus/sessions/, and marked as coming from an external source; project roots are only registered — no directory is moved.
• MCP configuration is normalized against a whitelist: only the fields actually needed to launch are kept (command/args/env for command-based servers, url/headers/oauth for HTTP-based ones), and every other field is dropped. Values inside env and headers, however, are carried over as-is — if the original configuration kept secrets in environment variables or request headers, they come into Klaus with it. After importing, check those values on the MCP page; see MCP and connectors. Project-level MCP from Codex comes with one extra requirement: the project must be registered and marked as trusted by Codex. A server with the same name as one you already have is skipped instead of overwriting it.
• Repeated imports are skipped: an import ledger records the path and content hash of every source session file, so a file that has not changed is skipped on a second import; if the source file has changed (its hash differs), you can import it again.
• Session imports have a volume limit: at most 50 sessions per import, and by default only the last 30 days are considered.
• If MCP configuration changed as a result of the import, running sessions reload MCP right away, with no need to restart the app. Skills, on the other hand, are read from disk when a session starts, and Klaus does not watch that directory — the import writes files straight to disk, so it cannot go through the "edit in the app → automatically rebuilt next turn" path. You need to open a new session to see them (see How extensions are loaded).