Human-in-the-Loop Patterns for Claude Computer Use
Design Claude computer use workflows with appropriate human oversight. Learn when to require confirmation, when autonomous action is safe, and how to balance efficiency with safety in GUI automation.
Autonomous computer use is powerful — and dangerous. Claude can click the wrong button, submit the wrong form, or delete the wrong data just as easily as a human can. Human-in-the-loop (HITL) patterns define when Claude should act autonomously and when it should pause and ask for confirmation.
The goal isn't to eliminate autonomy — it's to put checkpoints at the right places so autonomy is fast where it's safe and careful where it's not.
The Risk-Based Autonomy Model
Categorize every action by risk level:
| Risk Level | Examples | Autonomy |
|---|---|---|
| Read-only | Viewing pages, reading content, taking screenshots | Full autonomy |
| Low-risk write | Filling search fields, applying filters, changing view settings | Autonomy with logging |
| Medium-risk write | Filling forms, uploading files, sending messages | Confirm before action |
| High-risk write | Submitting payments, deleting data, changing permissions | Human must perform |
| Destructive | Account deletion, data purge, irreversible changes | Completely blocked |
Specifying Risk Levels in Prompts
ACTION RISK CLASSIFICATION:
READ-ONLY (autonomous):
- Navigating between pages
- Viewing and reading content
- Taking screenshots
- Scrolling, expanding sections
→ Perform these without asking
LOW-RISK (autonomous, log actions):
- Typing in search fields
- Applying filters and sorting
- Changing display preferences
→ Perform these, but include each action in your response so I can review
MEDIUM-RISK (confirm first):
- Filling and submitting forms
- Uploading files
- Sending emails or messages
- Changing settings
→ Before performing: "I'm about to [action]. Here's what will happen: [preview]. Proceed?"
HIGH-RISK (confirm with explicit approval):
- Making payments or purchases
- Deleting records or data
- Changing user permissions
- Publishing content publicly
→ Before performing: "This is a HIGH-RISK action. I will NOT proceed without explicit confirmation. [Full details of what will happen]."
DESTRUCTIVE (blocked):
- Account deletion
- Data purge
- Irreversible operations
→ "This action is blocked. I will not perform it under any circumstances."
Confirmation Patterns
The Preview Pattern
Before I [take action], here's what will happen:
ACTION: [Description of the exact action]
IMPACT: [What will change — be specific]
REVERSIBLE? [Yes / No / Partially — explain]
ALTERNATIVES: [If there's a safer way to achieve the same goal, mention it]
Proceed with this action? (yes/no)
The Batch Confirmation Pattern
For multi-step workflows, batch confirmations to avoid interruption fatigue:
I need to perform these 4 actions to complete the task:
1. [Action 1] — [Impact: low]
2. [Action 2] — [Impact: low]
3. [Action 3] — [Impact: medium — will send email to 5 recipients]
4. [Action 4] — [Impact: low]
I can perform actions 1, 2, and 4 autonomously.
Action 3 needs your confirmation because it sends external communication.
Approve action 3? (yes/no — if yes, I'll perform all 4 in sequence)
The Escalation Pattern
When you encounter a situation that requires human judgment:
1. STOP all autonomous actions
2. Describe the situation: "I've encountered [situation]. The options are:"
3. List the options with implications:
"Option A: [action] → [outcome]. Risk: [risk level]"
"Option B: [action] → [outcome]. Risk: [risk level]"
4. Recommend one: "I recommend Option [X] because [reasoning]"
5. WAIT for human decision
Timeout and Default Behavior
Autonomous agents shouldn't wait forever for human input:
CONFIRMATION TIMEOUT:
If I request confirmation and don't receive a response within [X minutes]:
- READ-ONLY tasks: Continue autonomously (low risk if wrong)
- LOW-RISK tasks: Continue but add a note: "[Action taken without confirmation due to timeout]"
- MEDIUM-RISK tasks: ABORT the workflow. Do not proceed without confirmation.
- HIGH-RISK tasks: ABORT. These should never proceed without explicit approval.
Session Management Patterns
The Session Boundary
At the START of each session:
1. State what you're about to do
2. Confirm you're in the right starting state (right page, right account)
3. Remind me of the autonomy rules for this session
At the END of each session:
1. Summarize what was accomplished
2. List any actions that require follow-up
3. Note any anomalies or unexpected behaviors
The Handoff Pattern
SESSION HANDOFF SUMMARY:
Completed:
- [Action 1] → Success
- [Action 2] → Success
- [Action 3] → Completed with note: [note]
Pending:
- [Action 4] — requires [specific input/information]
- [Action 5] — blocked by [specific issue]
State at handoff:
- Current URL: [url]
- Current page state: [description]
- Any open modals/popups: [describe if any]
Next session should start by: [specific starting action]
Testing HITL Workflows
Test autonomous actions first
Run read-only and low-risk tasks with full autonomy. Verify Claude performs them correctly before adding confirmation checkpoints.
Test confirmation accuracy
Run medium-risk tasks and verify Claude correctly identifies when confirmation is needed — and doesn't ask for confirmation on autonomous actions.
Test timeout behavior
Intentionally don't respond to a confirmation request. Verify Claude handles the timeout according to the specified rules.
Test error escalation
Create a scenario where Claude encounters an ambiguous situation. Verify it escalates rather than guessing.
Note:
Pro Move: Log all confirmation requests and their outcomes. After 50 sessions, analyze: which actions required confirmation but were always approved? Those can likely be reclassified to autonomous. Which autonomous actions led to errors? Those need confirmation added. The risk model should evolve with data.
Note:
The automation bias trap: Humans tend to trust automated systems more over time, even when they shouldn't. Even with the best HITL patterns, users will start reflexively approving confirmation requests. Periodically insert "catch trials" — requests that SHOULD be declined — to verify the human is still paying attention.
Related Pages
- Computer Use Prompting — Master the fundamental prompt structure for describing UI targets and action sequences before layering on HITL safety patterns.
Related Articles
Claude Extended Thinking: When & How to Use It
Master Claude's extended thinking feature. Learn when to enable it, how to read the thinking stream, debug faulty reasoning, and identify which problem types benefit most from silent reasoning.
Social Media Prompts: Viral Content
Optimized Nano Banana prompts for Instagram, TikTok, Pinterest, and Twitter content.
Master Claude Prompts: Complete Strategy Guide
Unlock Claude's full potential with specialized prompt strategies for extended thinking, Artifacts, 200K context, computer use, and Claude Code. Proven techniques for Anthropic's most advanced model.