dbs-computer-use lets an agent operate web pages and desktop apps for you. It first asks whether the job needs the screen at all, since an API, a command line or a file is faster. If it does, it checks which control tools the agent has and uses the best one, preferring work in the background so your mouse stays yours.
When no tool is available it explains which one to install, what that enables and the official install command, and waits for your approval. Passwords, codes and payments are always left to you, and every key action is read back to confirm it worked.
What You Get
- A tool choice based on the tools the agent has loaded, in the order Cua Driver, agent-desktop, then the agent’s own computer use
- Install advice with the official command and what it enables, applied only after you agree
- Background operation by element, with escalation to foreground only after you say yes
- A pause before payments, deletions, sends, form submissions and account changes, naming the button and the effect
- A report with the result, the tool used and anything left unconfirmed
Common Use Cases
- Reading data from a logged-in web dashboard
- Operating a desktop app that has no API
- Setting up a computer control tool on a new machine
- Checking a page without taking over your mouse
What Makes It Unique
Most computer-use setups assume one tool. This Skill detects capabilities by looking at the tool list, ranks three routes, and falls back one step at a time. It refuses to use browser extensions that act inside your signed-in browser because of account-ban risk. It treats a success message as unproven until the screen state is read back.
Under The Hood
The agent follows the steps in SKILL.md and reads reference files for each tool. It calls the computer-control tools your agent already has, such as Cua Driver, and runs the agent-desktop command line through the shell. It can fetch public web pages when only text is needed. When a tool is missing, it proposes shell install commands that download and run official scripts or use npm, and runs them only after you approve; macOS permission prompts are left for you to click. It can click, type and read in real apps and browsers. It does not enter passwords or make payments.