Relationship with Klaus

The two are clients of the same engine, and both connect only through the named methods the engine exposes; there is no engine capability that only one of them can use. User-level configuration, skills, hooks, and MCP servers all live under ~/.klaus, and project-level ones live under <project directory>/.klaus. Both clients read the same set of files (when a name collides, the project-level one overrides the user-level one). Session records land in ~/.klaus/sessions by default as well, so a session you open in Klaus Cli is visible in Klaus. What is unique to Klaus is everything that needs a graphical interface: the browser panel, voice input, the system tray, and window screenshots. What is unique to Klaus Cli is that its output can be consumed by pipes and exit codes (--json, chaining scripts with klaus exec).