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 works
Klaus Desktop
Your agent workspace
Give 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)
Review changes file by file
The 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 GitKeeps running when you're away
Checks, daily reports and information gathering run on a schedule, with results sent to Feishu, DingTalk or WeChat — the places you already use.
Scheduled tasksNew: friend collaboration
Add a friend by email, @ them in an ordinary task, and let your agents work it together. The person receiving it decides which directories, apps and execution mode to authorise.
How one task runs from start to finish
Three moments from the same task in Klaus, all taken from real screen recordings.
-
01
Planning and execution
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.
-
02
Changes and review
Expand a sub-agent's progress and changes in the Overview panel: per-file counts first, then the actual edits file by file.
-
03
Schedules and reports
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.
How Klaus works
A good tool should widen what a person can do.
Let your agents work a task together
Find a friend by their registered email, start a collaboration from an ordinary task, and leave the choice of apps, directories and execution mode to the person receiving it.
Manage contacts on the friends page
The friends entry sits below Dreams. When you send or accept a request you can choose whether to receive that person's task requests, and change it later. Accepting a request does not by itself authorise any task.
Confirm who they are by email
Look up the account by the email they registered Klaus with, check the real nickname and avatar, then send the request.
See the task before deciding whether to start
@ a friend in an ordinary task, or let the agent send it after understanding your request in plain language. The request arrives at the designated receiving computer and only starts once authorised; the final answer returns to the device and session that started the task. If that computer is offline you're told clearly — it is not rerouted to another device.
Scope the authorisation to real resources
On the receiving computer, choose directories as read-only or editable, and which apps may see and act on visible content. Execution can be ask every time, auto-edit, or automatic within the granted scope; directory authorisation bounds direct file and command access.
Sample accounts and tasks are shown. Friend collaboration needs Klaus desktop 0.4.28 or later on both sides. You can remember an authorisation so that friend's later tasks start automatically on this computer within the scope you chose; revoking it stops tasks already authorised. Removing a friend ends the relationship on both sides and stops authorised tasks, while history is kept.
and more
Each one has a doc page explaining what it does and where to set it up.
Memory
Turn it on and your project conventions, release process and preferences accumulate as you work. Every entry can be viewed, edited and deleted.
View docsSkills and plugins
Write a routine you repeat as a skill and reuse it in one sentence. Plugins and MCP tools are picked up per task.
View docsSub-agents
Split a large task across sub-agents running in parallel, with their plans, progress and artifacts in the Overview panel.
View docsParallel worktrees
Changes land on separate branches that don't interfere, so several tasks can run at once — and you decide what gets merged.
View docsSpec mode
When the requirement isn't settled yet, write the spec document together first and start implementing once it's final.
View docsVoice input
Hold to talk and dictate the requirement or an extra note; it turns into text and sends.
View docsWhat you probably want to know before installing
How do I start?
Install 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.
Which systems are supported?
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.
Which models does it use?
Two kinds of source: your own Claude Code, Codex, Qoder, QwenWork, QoderWork, WorkBuddy or Kimi subscription, or a custom API (an OpenAI-compatible endpoint with your own base URL and model name). It runs on your account and your quota — Klaus neither meters nor reports it. When a model is called, the task content that call needs goes to the service you chose.
Can the important actions run away?
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.
Need help, or want to give feedback?
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.