Claude DuetUndisclosed

Claude drives the mouse for a day of real Mac work: 40+ files sorted, PDF data typed into a spreadsheet, one form filled eight times - and where it fails quietly

Popular-Help5516(Reddit 用户 u/Popular-Help5516,原帖作者本人,自述用一天时间在自己 Mac 上实测)Reddit · 2026-03-24

Read original

Saved text / editorial summary

原帖正文(Reddit r/PromptEngineering,作者 u/Popular-Help5516,Atom 源 updated 字段 2026-03-24;本轮经 Reddit 公开 Atom feed 取得,以下为节选,删节处以 … 标出,英文部分逐字未改写): “Claude launched Computer Use yesterday. it takes screenshots of your screen, figures out whats on it, then moves your mouse and types on your keyboard. like a person sitting at your desk. mac only, research preview, Pro/Max plans. spent most of today testing it on actual work stuff instead of demos. heres what i found. works surprisingly well: - file management — told it to rename and sort 40+ files in my Downloads folder. took about 5 minutes but got every single one right - spreadsheet data entry — had it pull data from a PDF and enter it into a Numbers spreadsheet row by row. slow but accurate - browser form filling — filled out the same web form with different data 8 times. only messed up one date format which i fixed with a follow up message - research compilation — opened 5 tabs, pulled key info from each, compiled into a text doc works but needs babysitting: - anything involving multiple apps switching back and forth — sometimes loses track of which window its in - longer workflows (20+ steps) — failed silently at step 15 once. had to catch it and redirect doesnt work yet: - anything needing speed (2-5 seconds per click adds up fast) - captchas, 2FA, login screens - complex drag and drop interactions - anything you cant afford to have mis-clicked (like sending emails or making purchases) the biggest thing nobody mentions: it takes over your whole machine. you cant use your mac while claude is working. so the best use case is actually "start a task then walk away." come back to finished work. … reliability is maybe 80% on simple tasks, 50% on complex ones.” 中文对照:他说 Computer Use 的工作方式是截图、判断屏幕上有什么,然后移动鼠标、敲键盘。他拿真活而不是演示测了一天:文件管理(下载文件夹里 40 多个文件改名归类,约 5 分钟,全对)、表格录入(从 PDF 取数据逐行进 Numbers,慢但准)、表单填写(同一张表单用不同数据填 8 次,只错一处日期格式,补一句就改好)、资料汇总(开 5 个标签页取要点合成一份文档)。需要盯着的两类:跨应用来回切会弄不清在哪个窗口;20 步以上的长流程有一次在第 15 步静默失败。做不了的:要速度的事(每次点击 2 到 5 秒)、验证码/二次验证/登录页、复杂拖拽、以及点错代价高的动作(发邮件、付款)。他特别强调:它会接管整台机器,工作时你不能用这台 Mac,所以最好的用法是开个任务就走开。他自估可靠率简单任务约 80%、复杂任务约 50%。

Business model

Reddit user u/Popular-Help5516 tested Claude's Computer Use on a day of real work rather than demos, and posted the results in r/PromptEngineering. What worked better than expected: file management - rename and sort 40+ files in the downloads folder, about five minutes, every one correct; spreadsheet entry - pull data from a PDF into Numbers row by row, slow but accurate; form filling - the same web form eight times with different data, one date format wrong, fixed with a follow-up message; research compilation - open five tabs, pull the key points, compile into a document. What needs babysitting: switching back and forth between apps, where it sometimes loses track of which window it is in, and longer workflows of 20+ steps, one of which failed silently at step 15 until he caught it. What does not work yet: anything needing speed (two to five seconds per click adds up), captchas, 2FA and login screens, complex drag and drop, and anything you cannot afford to have mis-clicked, such as sending email or making purchases. His most useful observation is the one he says nobody mentions: it takes over the whole machine, so you cannot use the Mac while it works - the right pattern is start a task and walk away. He paired it with Dispatch, a phone remote: he texted a task while out getting coffee and came back to finished work. He estimates reliability at roughly 80 percent on simple tasks and 50 percent on complex ones. No cost, token or subscription figure appears in the post, and it ends with a link to his own site's longer write-up, which is disclosed here.

The useful part is not that it can drive a computer. It is the author's three-tier boundary plus the fact nobody mentions: it occupies the machine entirely. The first tells you what to hand over - bulk, repetitive, reversible work. The second dictates when: start it and leave. Grading tasks by the cost of a mis-click is what decides whether this survives contact with real work.

Workflow

  1. Grade every task by the cost of a mis-click; irreversible actions never go to the agent. (AgentFlow's rule; the author simply lists email and purchases as not-ready.)
  2. One application per run - the author's window-tracking failure came from switching apps.
  3. Split anything longer than 20 steps and make it report progress at each segment; silent failure at step 15 is otherwise invisible. (AgentFlow's rule.)
  4. Start it and walk away, because it takes over the whole machine. (The author's own observation.)
  5. Captchas, logins and 2FA are yours to handle; do not attempt to bypass them. (AgentFlow's boundary and a compliance line.)
  6. Finish with a before/after list and an unfinished list, so you can tell what actually got done.

Adaptation plan

The post gives no cost, token count, subscription price or runtime figure, and no numbers behind the 80/50 reliability estimate. It does not say which Mac or OS version, which file types were sorted, how the PDF to Numbers run was verified, or how often the silent failure happened beyond the one instance. The author's link at the end points to his own site and is disclosed as self-referral. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

Prompt

AgentFlow draft · Untested.

You are my desktop operation assistant. You may read the screen, move the mouse and type to get through bulk organising, data transcription and repeated form filling. You do not send email, do not pay, do not order, do not delete originals, and do not attempt to bypass any verification or login.

[INPUT]
- Task type: [file organising / data transcription / form filling / multi-page compilation - pick one per run]
- Scope: [specific folder, files or pages]
- Rules: [naming or sorting rules / target sheet and fields / form fields and data list]
- Mis-click cost: this task is [reversible if wrong / fixable if wrong]; irreversible actions are out of scope

[STEPS]
1. Restate what you will do and the rules, and give the expected step count. If it exceeds 20 steps, split it and run only the first segment.
2. Stay inside one application. If you must switch apps, stop and report, then wait for my decision.
3. At the end of each segment report: which steps are done / current window / results / anything abnormal.
4. On a captcha, login page, 2FA prompt or complex drag and drop: stop, say what it is, hand it to me.
5. Before deleting, overwriting or moving originals: list them and wait for confirmation; do not execute.
6. Finish with a before/after list and an unfinished list.

[OUTPUT]
1) step count and segment plan; 2) per-segment report; 3) before/after list (e.g. old filename to new filename); 4) exceptions and unfinished items.

[NEEDS MY CONFIRMATION]
- Deleting, overwriting or moving originals.
- Sending email, paying, ordering or submitting anything.
- Any case the rules do not cover: ask me rather than deciding.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Screen unclear, element not found, step limit exceeded, stuck midway: say which step and which window, then stop and wait. Do not retry the same action in a loop and do not switch to another path to get around a restriction.

Running costs and pitfalls

The post gives no cost, token count, subscription price or runtime figure, and no numbers behind the 80/50 reliability estimate. It does not say which Mac or OS version, which file types were sorted, how the PDF to Numbers run was verified, or how often the silent failure happened beyond the one instance. The author's link at the end points to his own site and is disclosed as self-referral. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.