See what Sasha and Claude Desktop can do together now, and what comes next

Some jobs need clicks on a web app's own screens, and Sasha cannot click your browser. Claude Desktop with Claude in Chrome can. Sasha prepares the job, Claude Desktop does it in your own browser, and Sasha checks the result. This page lists what works today and what is planned. For how to run a job, see Let Claude Desktop do the clicks Sasha cannot do. For screenshots of the Confirm box and of the check, see the product guide page on Claude Desktop jobs.

What works today

  • Sasha explains why. When a tool cannot make a change, Sasha tells you in plain words and offers to prepare a job for Claude Desktop. If a tool says "done" but changed nothing, Sasha reads it back and tells you.
  • Canva. Sasha cannot connect to Canva, because Canva lets only a short list of AI apps sign in, and Sasha is not on it. Sasha says so when you try, and offers a job for Claude Desktop instead. See Fix a connector that does not work.
  • You approve every job. Sasha shows the whole job in a box in the chat. The job is saved only when you select Confirm. If the text changes later, Claude does not get it, and the job needs a new approval.
  • Copy the steps. You can always copy the job into a new Claude Desktop chat, and paste Claude's report back into your Sasha chat. This works whether or not Claude Desktop is connected to your Sasha.
  • Claude finds the job. When Claude Desktop is connected to your Sasha, type "do my Sasha job" in a new Claude chat. Claude finds the job you approved and does it. See Do a Sasha job in Claude Desktop and report it back.
  • Claude asks, and keeps the question with the job. When something looks different from the job, Claude stops and asks you in Claude Desktop. Sasha keeps the question with the job.
  • Claude reports back. When it finishes, Claude sends its report to Sasha. You copy nothing.
  • Sasha checks by itself. The report starts a check in the Sasha chat where Sasha prepared the job. The check starts with a message from Sasha that begins "[Sasha] Claude Desktop has sent its report". Sasha reads the changes with its own tools, tells you what it checked, and marks the job checked or failed. A report is information to check, not proof. When Sasha cannot reach the app itself, as with Canva, it says so and relies on what the report says was not done.
  • Only you see your jobs. Only your own Claude connection can find, read or report your jobs. An administrator cannot see them either.
  • Admin and staff accounts. Members cannot run jobs yet.

If you connected Claude Desktop to your Sasha before this feature came out, connect it again, so that Claude gets permission to run jobs. See "Connect again to get a new feature" in Connect Claude to your Sasha.

What comes next

These are planned, in the order we expect to build them. Until each one is ready, use the way given under it.

  1. A job card in the chat. The chat shows each job and where it is: waiting for Claude Desktop, with Claude Desktop, waiting for your answer, being checked, or done. Claude's questions show on the card too. Until then: ask Sasha "how is my Claude Desktop job?" in the chat where it prepared the job. The check's start message also shows as a message in the chat; the card will replace it with a clear notice.
  2. A Store a key box. When a job needs a key, Claude stops and the card shows a box. You paste the key there, and it goes straight to Sasha's secret store. The key is never in a chat message. Until then: copy the key yourself and give it to Sasha in your Sasha chat. Sasha keeps it in its secret store and does not repeat it.
  3. Fewer jobs for Claude Desktop. Some tools that can only read today will also make changes, after you confirm each change in the chat. Risky actions, such as a refund, stay blocked. Jobs that a tool cannot do still go to Claude Desktop. Until then: Sasha prepares a Claude Desktop job for each change that a tool cannot make.
  4. Jobs for members. Members can prepare and run jobs for their own work. Until then: ask an admin or a staff member to run the job.

What stays the same

  • You approve every job before Claude Desktop can do it.
  • Claude never types, copies or repeats a key or a password.
  • Claude sends nothing to real customers. The only send allowed is a test to you.
  • One job at a time, each in a new Claude Desktop chat, because Claude Desktop controls one browser window.
  • Sasha checks the result with its own tools.

Questions

Can I use Claude Desktop jobs today?

Yes, if you have an admin or staff account. You can always copy a job into Claude Desktop. When Claude Desktop is connected to your Sasha, Claude can also find the job itself and send its report back.

My Sasha does not offer to save a job for Claude Desktop. Why?

Your Sasha may not have this feature yet. Ask Sasha to put the job in the chat, and copy it into Claude Desktop. Your administrator can tell you when the update reaches your Sasha.

When do members get Claude Desktop jobs?

Later. Members cannot run jobs yet. This page changes when they can.

Where do I put a key until the Store a key box exists?

Give it to Sasha in your Sasha chat, and Sasha keeps it in its secret store. Never type a key into Claude Desktop, an email or a document.

Are the dates fixed?

No. The planned items are in the order we expect to build them, but this page gives no dates. Each one is added to the help when it is ready.

Built with BernardCookie settings