Friends
@-mention a friend in a chat and choose Ask to handle or Just notify; your words go out as written, their Klaus handles it on their computer under their permissions, and the result comes back as a reply in the chat you asked from.
Friends let two Klaus accounts message each other. You @-mention a friend in a chat and write what you need, and the message goes to them as written. If you ask them to handle it, their Klaus works on their own computer, with their models, their files, and the permissions they chose. The result comes back as a reply in the chat you sent the request from. It is all asynchronous: once the message is sent your composer is free again and you carry on with your own work.
Both sides need to be signed in to a Klaus account. While you are signed out the Friends entry is unavailable; everything else is unaffected. See Account and sign-in.
Adding a friend
"Friends" in the sidebar's fixed entries opens the Friends page. The "+" menu at the top right has three ways in:
- Add friend: enter the other person's registered email, click "Find", check their name and avatar, then "Send request". The dialog also lets you set this friend's "Friend permission" in advance; it takes effect as soon as they accept.
- My QR code: let them scan it. You can "Save my QR code" or "Share my QR card", or "Copy link" to get an "Add-me link". When they open the link in Klaus, a request dialog opens with your email filled in, and they still have to click send themselves; a link alone never adds anyone.
- Scan to add: "Use camera" to scan their code, or pick a QR image to read a screenshot.
The other person sees the request under "Friend requests" and can "Accept" or "Decline", choosing how to receive your tasks as they accept. Until then you can "Cancel request". The friendship exists only once both sides have confirmed.
Each row under "Your friends" shows whether they are online, whether they receive your tasks, and how you receive theirs. A row has "Send task" (puts that friend straight into the composer) and "Friend settings".
Messaging a friend
Type @ in the composer; the "Friends" group of the mention menu lists your friends with their online state and whether they receive tasks. Pick one and a mention marked "Friend" appears in the composer. A menu then appears in front of the send button:
- Ask to handle (the default): ask their Klaus to take care of it.
- Just notify: deliver the message only. It does not start their Klaus. They get a notification and the message stays in the chat; they can hand it to their own Klaus later if they want to.
Only an intact friend mention in the composer sends the message to a friend; typing a name in plain text does not. The message goes out as written and your own Klaus does not run. What goes out is only the text of that message: attachments are stopped with a prompt to remove them, and neither your chat history nor your files are sent. One message can mention up to eight friends.
You can also ask your own Klaus to message a friend for you, for example "tell Lin what we found". It asks you to confirm the message first; whether it asks every time follows that chat's permission level. When Klaus writes the message, content from the chat may go to your friend, but never credentials.
Delivery status
A status line under the sent message follows its progress: "Sent · not yet delivered" → "Delivered" → "Awaiting recipient authorization" → "Recipient is processing" → "Replied". Other states are "Additional information requested", "Declined", "Cancelled", "Failed", and "Sending failed".
- Until they are done you can "Cancel request"; their side stops the request, but anything already completed is not undone.
- A message that failed to send can be retried with "Retry sending"; it keeps its identity.
You can message a friend who is offline. The message is kept on the server and their computer receives it as soon as it comes online; requests do not expire with time.
Receiving a request
A friend's messages land under that friend's folder in the sidebar's project area. Messages from the same source chat land in the same paired chat, whose row is marked "Awaiting reply", and the friend's folder shows how many need attention. A system notification is shown too. To keep a friend quiet, use "Mute friend notifications" in their folder's menu.
How a request is handled depends on the "Receive tasks" choice you made for that friend:
- Ask once per conversation (the default): a first-execution approval card appears when a friend's request creates a new conversation on your computer. "Allow this conversation" admits later requests in that conversation as well. Completion, cancellation and app restart do not revoke that approval. You can also "Decline", or "View permission scope" first. Multiple requests awaiting the first decision share one card and run in order after approval.
- Run automatically with the defaults below: the request starts without another admission question, using the configured initial directories and permissions. Individual actions follow the conversation's current permission preset.
- Do not receive: new requests are declined automatically and the sender sees them as declined.
If a request lands in one of your existing chats (for example because it answers a request you sent), it runs with that chat's own permissions when the chat is free. It does not show the execution approval for a new incoming friend conversation.
Your own messages always use the conversation's current permissions and never require friend admission. You can ask your own questions even while a friend's request awaits its first approval. Your input does not implicitly approve the pending friend request.
Handling and replying
The work stays in the receiver's own chat. To send the result back, their Klaus uses a reply tool once; the chat shows it as the task result that marks the request complete. Its final answer is shown only to its owner and is never sent to the friend automatically. If it needs more information, it sends a question back, and the exchange continues in the same chat once the sender answers.
If Klaus finishes without sending a reply, it is reminded once. If there is still nothing, the requester sees that the friend's Klaus finished without attaching a result, and the owner sees "Klaus did not reply; {friend} was told the task ended", with "Let Klaus reply to {friend}" to send one after all.
The reply comes back to the chat you sent the request from, labelled "{friend} Friend replied · in response to your HH:MM request"; the second half links back to the original request. Hovering it shows "Reply to sender" and "Ask my Klaus". Messages longer than 12 lines or 800 characters fold into a summary with "Expand full message", "Open in reader", and "Copy full message". If the original chat has been deleted, the reply goes into a new chat.
If a reply cannot be delivered (most often because the requester is offline), the receiving computer retries after 15 seconds, 1 minute, 5 minutes, 15 minutes, and 1 hour, and sends it at once when it sees the requester come online. A definite refusal from the server stops the retries.
While a task runs
- No time limit: a friend task runs until it finishes on its own.
- Directories and execution permissions: operations outside the default roots use the same approval or review flow as ordinary conversations, while Full access removes the ordinary directory sandbox. A directory access request can still add a directory to the default writable roots and optionally save it in that friend's standing settings.
- Stopping: stop it in the chat; or switch that friend to "Do not receive" or remove the friend, which cancels that friend's pending and running tasks (switching to Do not receive tells you how many will be cancelled first).
Settings → Friends
The "Friends" page under the account group manages two things:
- Receiving computer: which computer a friend's tasks go to. With nothing chosen it is "All online computers (default)"; once you choose one, tasks go only there.
- Default friend permission: applies to friends you add and requests you accept; each friend can be adjusted later. It covers:
- Receive tasks: Ask once per conversation (the default), Run automatically with the defaults below, or Do not receive.
- Execution permission: the initial preset for a new friend conversation: "Ask for approval" (the default), "Approve for me", or "Full access", with the same meaning as ordinary conversations. Later changes belong to that conversation and survive reconstruction.
- Run in: "Plain conversation" (the default), a project, or a workspace. With a project or workspace, the task chat is filed under it and may read and write its folders.
- Allow task commands to access the network: on by default, and you can turn it off; an app's own network access is up to the selected app.
- Allow Computer Use in selected apps: off by default; when on, only the apps you tick can be operated.
- Files and directories: "Add directory" saves additional paths. "Can edit" adds a path to the initial writable roots; "Read only" does not pre-authorize writes. Actual access follows the conversation's current permission preset. New entries default to read only.
- Shared friend space: every friend automatically gets their own subfolder (
~/.klaus/friends/<friendship id>/); friend tasks start there and it is always editable. The default writable roots include only this friendship's own subfolder, plus the selected project or workspace directories.
Directory settings supply initial default roots rather than an additional full-access ceiling. Ask for approval and Approve for me handle operations outside those roots through the ordinary approval flow. Selected Computer Use application authorization remains independent. See How permissions are decided. These settings are stored only on this computer.
A friend's "Friend settings" on the Friends page lets you write a remark (kept only on this computer, never shown to the friend, and used for display and search), adjust that friend's own Friend permission, or "Remove friend". After removal you are no longer friends and task grants are revoked; both sides keep their local chat history.
Global search (⌘/Ctrl+K) also finds friend chats.