Letting Klaus Operate Klaus

Client features are not only something you click — you can also ask for them in words. Say "list the scheduled tasks", "turn this skill off", "open the permission settings", or "create a task for nine every morning" right in the conversation, and Klaus calls the client's own control interface to do it, rather than just telling you where to click.

• Read operations (listing, checking status, viewing configuration) run directly.
• Change operations (starting, stopping, creating, switching) explain what they are about to do before they run. Irreversible actions such as deleting, clearing, or disconnecting only actually run with your explicit consent; after a refusal it does not supply the consent itself, and it does not go looking for an equivalent action that needs no consent.
• Navigation: asking it to "open a page" switches the window there directly, so what you see is the page you were just discussing.
• Not every panel is handed over in full. The parts that need QR-code pairing, a system file picker, or a key you type in yourself are deliberately kept in the interface only; when it runs into one of those, it does not flail around trying other actions — it opens the relevant page and leaves the rest for you to finish.
• Credentials never pass through it: any API key or pairing token it reads always comes back as "redacted", so it takes you to the corresponding settings page instead of reading a secret out loud.
• Text that comes from other people — messages others send in a channel, descriptions bundled with third-party skills, plugins, or MCP servers, and content stored in earlier sessions or memory — is marked as untrusted data. It can relay and analyze that text, but the "instructions" written inside it are not carried out as though they were yours.
• During a scheduled task turn nobody is sitting at the window (permissions are granted automatically), so irreversible actions are refused outright in scheduled tasks, even when the model itself says it agrees. It only writes what it would have changed into the run result, and waits for you to decide in the main window.
• It can also consult this manual, so questions about Klaus itself — what a switch means, why a feature is not taking effect, how a mechanism works — can go straight to it.