Plan and approval
A broad goal becomes a sequence of steps you can act on, with the reasoning and status of each in the Overview panel. Change one midway and carry on.
How plan mode worksGive it the outcome. It plans first and waits for your approval, then edits files, runs commands and verifies the result. Review the changes file by file, and confirm the moves that matter.
Supports Apple Silicon Macs (macOS 13 or later) and Windows x64 (Windows 10 or later)
A broad goal becomes a sequence of steps you can act on, with the reasoning and status of each in the Overview panel. Change one midway and carry on.
How plan mode worksThe diff view starts with per-file counts, then opens a single file to show the actual lines. Once it looks right, commit the whole repo in one go.
Workspaces and GitChecks, daily reports and information gathering run on a schedule, with results sent to Feishu, DingTalk or WeChat — the places you already use.
Scheduled tasks@ a friend in a chat and their Klaus handles it on their computer; the result comes back as a reply in the same chat. The receiver decides how requests are handled.
Three moments from the same task in Klaus, all taken from real screen recordings.
A broad goal is broken into a plan, and tools are called one at a time as it runs. Add a line at any point to change direction — no need to wait for it to stop.

Expand a sub-agent's progress and changes in the Overview panel: per-file counts first, then the actual edits file by file.

Routine tasks run on their own schedule, the run history stays in the scheduled-tasks panel, and the conclusions go to the chat channels you already use.

A good tool should widen what a person can do.
Two Klaus accounts message each other: ask the other side to handle something, or just let them know. Their Klaus works on their computer under their permissions, and you don't wait.
Type @ in any chat, pick a friend and write what you need. Your words go out as written, your own Klaus doesn't run, and the composer is free again at once. Only the text is sent, never attachments or the chat history.
Each friend has a folder in the receiver's sidebar, and requests land there paired with the chat they came from. Depending on the receiver's settings, a card asks first, the work starts within the granted scope, or the request is declined.
When their Klaus is done it hands the result back in a single reply, in the chat you asked from, marked with the request it answers. Their Klaus's own final answer stays with them.
Settings → Friends decides how incoming requests are handled: ask every time, run automatically within the granted scope, or don't receive, plus execution permission, where it runs, which folders it may read or edit, and which apps it may operate. Each friend can be adjusted on their own.
The images use sample accounts and chats. Both sides sign in to a Klaus account and add each other by registered email, QR code or link. If they're offline the message waits and is delivered when their computer comes online. Switching to Don't receive, or removing the friend, stops that friend's running tasks; both sides keep their chat history.
Each one has a doc page explaining what it does and where to set it up.
Turn it on and your project conventions, release process and preferences accumulate as you work. Every entry can be viewed, edited and deleted.
View docsWrite a routine you repeat as a skill and reuse it in one sentence. Plugins and MCP tools are picked up per task.
View docsSplit a large task across sub-agents running in parallel, with their plans, progress and artifacts in the Overview panel.
View docsChanges land on separate branches that don't interfere, so several tasks can run at once — and you decide what gets merged.
View docsWhen the requirement isn't settled yet, write the spec document together first and start implementing once it's final.
View docsHold to talk and dictate the requirement or an extra note; it turns into text and sends.
View docsInstall it, then sign in with a Klaus account or continue as a guest. Create a project from a real project directory and say clearly what outcome you want. Its file operations and commands happen inside that directory, and complex work produces a plan for your approval first.
The desktop app currently supports Apple Silicon Macs (macOS 13 or later) and Windows x64 on Windows 10 or later. the macOS installer is available, and the Windows installer is released.
All of them are your own accounts: Claude Code, Codex, Cursor, Qoder, QwenWork, WorkBuddy, Antigravity, TRAE CN, Kiro, Kimi and other subscriptions work once you sign in, the Bailian, MiniMax, Zhipu and Ark plans take a key, and a service you don't subscribe to can be added with your own API key. It runs on your account and quota; Klaus doesn't meter or report it. When a model is called, the task content goes to the service you chose.
Before writing a file, running a command or touching an external service, a permission card appears: allow once, allow for this session, or always allow. A deny rule you set overrides every mode. Scheduled tasks run automatically and don't wait for per-item approval, so agree the task's scope and permission rules before setting one up.
The docs cover features and internals. The in-app feedback entry attaches the session and environment details automatically, or write to support@klaus-ai.cn.