Browser and computer-use agents
Decide when an agent should operate a browser or desktop like a person, build it safely with scripted tools first and screen control last, and contain the risks.
Pro 1 · Quality engineerabout 3 hours7 sections
Quick answer
Computer-use agents operate a browser or desktop by looking at the screen and clicking. Use them only when no API exists, and run them in a contained environment.
Why it matters
Many Indian businesses run on portals and old desktop software with no APIs: government sites, insurer portals, legacy ERPs. Agents that can use them unlock automation that was impossible before, and carry new risks clients will ask about.
Sign up free to read the whole lesson
The rest of this lesson: 7 parts, video lessons, the best course, practice and a quick check. It is free, takes a few seconds and needs no card.
Accounts are for learners aged 18 and over. Under 18? The quick answer and the first part of every lesson stay open: browse lessons by topic.
Lessons on Agentic AI Engineer0 of 27 done
- 1Call an LLM API from code
- 2Get structured JSON output
- 3Tool calling
- 4The agent loop
- 5Designing tools for agents
- 6Agent memory
- 7Planning and reflection
- 8Context engineering
- 9LangGraph: agents as graphs
- 10Agent SDKs and sub-agents
- 11Multi-agent systems
- 12MCP servers and clients
- 13Browser and computer-use agents
- 14Logs and traces for agents
- 15How agents fail
- 16Test sets and evals
- 17Defend against prompt injection
- 18Human approval steps
- 19Guardrails
- 20Permissions and sandboxing
- 21Loop limits, budgets and kill switches
- 22Evaluating agents
- 23Advanced harness engineering
- 24Harnesses for long-running agents
- 25Deploy and monitor an LLM app
- 26Cost control
- 27Accountability for agent actions
Related
On the roadmap: Agentic AI Engineer
AgentsPro 1: Quality engineerVideo lessonsComputer-use agentSandboxPrompt injectionHuman in the loop