Your first Computer Use session: what to expect
Watch, intervene, and let it finish the boring parts
After this, you'll be able to start a simple Computer Use task, supervise it the right way, and know when to let it run versus when to step in.
Before you start
Complete Computer Use: what it actually does first; this lesson builds on understanding that Computer Use takes real actions, because supervising a live session only makes sense once you know the clicks are real.
The idea
Your first Computer Use session is a supervision exercise, not a test of whether you can let go. The cursor moving on its own is uncanny the first time, and that reaction is normal. Your job is to watch what Claude does and step in only when it heads somewhere wrong.
A quick access reminder for your first run: Computer Use is a research preview on the Pro and Max plans only, so you need one of those (Team and Enterprise plans do not have it), and being a preview means its behavior can still change.
The right first task is small and reversible, like renaming a batch of files or exporting a document, where a mistake costs nothing. Once you have watched a few tasks go cleanly, you will know what you can hand off and walk away from.
Here is the before and after: Before, you rename forty downloaded files one at a time, a fifteen-minute chore you resent. With Computer Use, you describe the pattern once, watch Claude rename the first three to confirm it has the pattern right, then let it finish while you read email.
Now try it: in Cowork, pick a genuinely safe task (renaming files in a folder, or exporting an open document to PDF) and ask Claude to do it. Watch the first few actions closely, then let it continue if the pattern is right.
Your first session is a supervision exercise, not a test of whether you can let go completely.
Try it (11 min)
Watch out for
- Picking a risky first task; choose something reversible like renaming or exporting, never sending or deleting
- Looking away during the first few actions; the early steps are where you confirm Claude understood the pattern
- Micromanaging every click after the pattern is clearly right; supervision means watching, not narrating each step
- Forgetting to ask for a pause-and-confirm; a checkpoint after the first few items catches mistakes before they multiply
- Trusting it unattended on day one; build that trust over several clean runs first
Paste this into Claude
I am about to run my first Computer Use task in Cowork and I want a safe, simple one to learn on. Here is the task: I have a folder of screenshots all named like "Screen Shot 2026-05-28 at 9.14.22 AM.png". I want them renamed to "project-alpha-01.png", "project-alpha-02.png", and so on, in the order they currently appear. Please: 1. Before you do anything, tell me your step-by-step plan in plain English. 2. Rename only the first THREE files, then pause and ask me to confirm the pattern looks right. 3. After I confirm, rename the rest. Do not touch any file outside this folder. Stop and ask me if anything looks ambiguous.
What good looks like
- Claude states its plan before acting, so you can catch a misunderstanding early
- Claude renames only the first three files and pauses for your confirmation as instructed
- The actions are visible on screen in real time and you can follow each one
- Claude stays inside the target folder and does not touch unrelated files
- After your confirmation, the remaining files are renamed in the correct order
When this breaks
- Breaks when you choose an irreversible first task, because any early mistake is permanent and teaches you to fear the feature instead of supervising it.
- Breaks when you skip the early pause-and-confirm, because a misread instruction repeats across every item before you notice, turning one small error into forty.
AI can help with this
In Cowork, type: 'I want a safe first Computer Use task. Suggest one reversible task you could do on my computer right now, tell me your plan first, do the first step, then pause for my confirmation before continuing.'
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that claude states its plan before acting, so you can catch a misunderstanding early.
- You can verify that claude renames only the first three files and pauses for your confirmation as instructed.
- You can verify that the actions are visible on screen in real time and you can follow each one.
- You can verify that claude stays inside the target folder and does not touch unrelated files.
Key takeaways
Your first Computer Use session is about supervision. Pick a small reversible task, watch the opening actions to confirm Claude understood, then let it finish the repetitive part. Trust grows from clean runs, not from letting go on day one.
- Choose a small, reversible first task so an early mistake costs you nothing.
- Watch the opening actions closely; that is where you confirm Claude understood the pattern.
- Ask for a pause-and-confirm after the first few items to catch a misread before it repeats.
- Let Claude finish the repetitive remainder once the pattern is clearly correct.
Go deeper