Anthropic · Technologies
Computer Use
Claude operates the screen when nothing else can.
Computer use lets Claude work a computer the way a person does: looking at the screen, clicking, typing and navigating real interfaces. It is the capability that reaches the systems with no API, from legacy desktop software to portals that only speak user interface. We deploy it with the guardrails that make it safe.
SCREEN TASKS · EXAMPLE ESTATE
TASK
TARGET
METHOD
STATUS
Portal-Lodgement
Legacy web portal
Browser
LIVE
Data-Rekeying
Desktop app
Screen
LIVE
UI-Testing
Product build
Screen
LIVE
Approval-Gates
Human sign off
Policy
REVIEW
unattended-run
No oversight
None
RISK
Sample estate
live · review · risk
In plain terms
The API is always better. Until there is no API.
Every business has systems that only a person at a screen can drive. Here is what changes.
Without it
- Staff rekeying data between systems that do not talk
- Legacy software untouched by every automation project
- Web portals worked by hand, one record at a time
- Testing that means clicking through the app yet again
With it
- Claude driving the screens people used to babysit
- Legacy systems automated without replatforming them
- Portal work batched and finished overnight
- Interfaces tested by an agent that never gets bored
What CG TECH can do with Computer Use
The work, broken into the parts that matter.
Precision first, screen second
Claude reaches for a connector or an API first, the browser next and the screen only when nothing else can do the job, because screen work is the slowest tool in the kit. We design the same way.
the right tool before the screen
Claude in Chrome for web work
For portals and web apps, Claude works inside the browser: reading pages, filling forms and navigating flows, with site permissions and approval modes controlling what it may touch.
web portals worked by agent
Real applications, really operated
In Cowork and Claude Code, Claude can operate desktop applications directly: opening apps, clicking through interfaces and verifying results on screen, with per app approval.
legacy apps automated, not replaced
Autonomy that stays on a leash
Approved apps only, human sign off on consequential actions, an instant abort key and no access to high risk sites. Screen driving agents earn trust in stages.
an agent that knows its limits
How an engagement runs
From manual screens to governed automation, step by step.
01
Discover
We map the manual screen work and what it costs you.
02
Design
Tool choice, guardrails and approval points designed first.
03
Build
The workflow live on one process, measured against the old way.
04
Expand
Coverage grows where the evidence says it should.
Questions we hear a lot
Common questions about Computer Use
What is Claude computer use?
Computer use lets Claude work a computer the way a person does: looking at the screen, moving the pointer, clicking, typing and navigating real interfaces. It is the capability that reaches systems with no way for other software to connect, from legacy desktop applications to portals that only offer a screen.
Is this just screen scraping?
No. Claude sees the screen, reasons about what it is looking at and adapts when the interface changes, where traditional automation breaks the moment a button moves.
Is it safe to let an agent drive our systems?
With the right design, yes. Approvals on consequential actions, approved applications only, full visibility of every step and a human able to stop it at any moment. We never deploy unattended screen automation on day one.
When should we use computer use instead of an API?
Only when there is no better path. If a system has an API or a connector, we use that: it is faster and more reliable. Computer use is for the systems that offer nothing else.
What does it run on?
Computer use is available to builders through the Claude API, and inside Claude Code and Cowork on the desktop, with Claude in Chrome covering browser work. We pick the surface that fits the workflow.
What sort of systems does this actually reach?
The ones every business has and nobody wants to talk about: an ageing line-of-business application, a government or supplier portal with no integration, a desktop tool one team depends on. If the only way in is a person at a keyboard, this is the option.
How reliable is it compared with a proper integration?
Less reliable, and that is the honest trade. An integration is exact and this is interpretive. We use it where no integration exists, keep the task narrow, and check the result rather than assuming it.
What happens when the screen changes?
It copes with small changes far better than old screen-scraping tools, which broke the moment a button moved. Larger redesigns still need attention, so we build in checks that notice a task stopped working rather than letting it fail quietly.
Ready when you are
Stuck with systems nothing can talk to? Let us talk.
A discovery session maps your manual work, your risks and your quick wins. You keep the plan either way.
What to expect
- A consultant replies within 4 business hours
- Session booked to understand your requirements
- We will provide you with a fixed price quote