Bring a friend's Klaus into your work

Some work needs files, tools or know-how on someone else's computer. @-mention a friend in a chat, choose Ask to handle or Just notify, and your words go out as written. Their Klaus handles it on their own computer within their permissions, and the reply lands in the chat you asked from. You don't wait; your own work carries on.

Fix checkout timeout testsYour computer
LinFriendCan you check whether the PayNow callback signing config on staging matches production?Heads-up: production PayNow callbacks now sign with the new key, and staging will switch over later.
Lin DeliveredLin Awaiting authorizationLin ProcessingLin RepliedLin DeclinedLin Delivered
Let's fix the timeout tests' wait condition first and compare once Aoife's result is back.
LinFriendreplied · to your 14:02 request
Staging still signs callbacks with the old key, so it doesn't match production. I've marked it in the staging config; switching to the new key fixes it.
Reply to senderAsk my Klaus
LinFriendCan you check whether the PayNow callback signing config on staging matches production?Heads-up: production PayNow callbacks now sign with the new key, and staging will switch over later.
Send a message…
Ask to handleJust notify
Lin's computerOnline
No new messages
LeoFriendasks you to handle thisJust notify
Can you check whether the PayNow callback signing config on staging matches production?Heads-up: production PayNow callbacks now sign with the new key, and staging will switch over later.

Leo asks your Klaus to handle this

Runs in a regular chat

Runs with the permissions you set for Leo.

View permission scope
Lin's Klaus is working…

LeoTask result · marks this request complete

Staging still signs callbacks with the old key, so it doesn't match production. I've marked it in the staging config; switching to the new key fixes it.
You declined this request.
Just notify doesn't start Lin's Klaus. The message stays in the chat, and Lin can still choose Ask my Klaus later.

In a chat, @-mention Lin, write the request and choose Ask to handle. Your words go to Lin as written and your own Klaus doesn't run; the composer is free at once and you keep working. The request lands in Leo's folder in Lin's sidebar. Lin's settings say to ask first. Lin's Klaus handles it on Lin's own computer, within the permissions Lin set for you. It sends the result back as an explicit reply, which lands in the chat you asked from. If Lin declines, the status under your message changes to Lin Declined, and nothing runs on Lin's side. Just notify only delivers the message: Lin is notified and it stays in the chat, but Lin's Klaus doesn't start.

The receiver decides how requests are handled

Each friend has their own permissions, changed in that friend's settings; new friends start from your defaults in Settings → Friends. Requests never expire with time.

A request that lands in one of your own chats (say, answering something you sent them) doesn't run on its own within that scope. It comes with Ask my Klaus, Reply myself and Decline, and once handed to Klaus it runs with that chat's permissions.

Run permissions
Ask for approval, approve for me, or full access
Location
A regular chat, a project or a workspace
Folders
Added one by one, read-only or editable, plus a folder shared with this friend
Network
Whether task commands may use the network; on by default, and you can turn it off
Apps
Whether it may operate apps on the computer, only the ones you tick
Receiving computer
Every online computer by default, or one you pick; while offline, messages are kept and delivered once it's back

Questions

Does my own Klaus run when I send a request?

No. A message to a friend goes out as written without passing through your model, and your composer is free at once so you can keep working. When they reply, the reply lands in the chat you sent from.

Can a friend see my files or chats?

Not directly. Only the text of that one message is sent; your chat history, attachments and files are not. What comes back is only what their Klaus explicitly replies with, and the same holds the other way.

Whose models and quota are used?

Whoever does the work. A request you send is handled by the Klaus on your friend's computer with their own model sources, not your quota.

What if my friend is offline?

The message is kept on the server and delivered once their computer is back online; it never expires with time. By default it goes to all of their online computers, or to one they pick.

What if their Klaus doesn't reply?

If it finishes without replying, you see that it finished without attaching a result; on their side they're told and can have Klaus send a reply in one click.

How do I stop a friend's task?

Set Receive tasks to Don't accept in that friend's settings, or remove the friend; either stops their running tasks. Removing a friend ends the friendship on both sides and keeps history. A request you sent can be cancelled from its bubble.