Use browser and computer tools when your task needs a webpage or an application's interface. You can ask your agent to operate those interfaces, or call the installed tools yourself from a terminal.
If a connected app already provides the operation you need, start with Tools. A direct app operation often gives you a clearer object ID and result to check.
Choose a route
Use a browser
Read or interact with a public webpage. A working browser provider and the page URL.
Browser sessions and profiles
Use a particular login or continue an open page. The correct account context or a live returned session.
Sign in and recover access
Finish sign-in during an app connection. The current connection page or job.
Use your computer
Inspect or control a desktop application. An installed computer provider and operating-system access.
Work in desktop apps
Edit, save, or export a document in an app. The target document and the application's supported operations.
Try a browser task
The browser guide takes you through a complete terminal example: open a public page, read its current contents, and close the session. It does not require a personal website login or an embedded-model API key.
To delegate a similar task, ask:
Agent host
Open this public page in an isolated background browser. Read its main heading and summarize the page. Include the URL and close the session when finished.
What to expect
The agent should discover the installed browser tools, inspect the actual page, and return what it found. A catalog entry alone does not establish that the browser can open a page on your computer.
What to expect while work runs
Background and foreground control
The intended experience is to leave your active window, pointer, and unrelated tabs usable. Isolated browser sessions provide a task-owned headless route. Other browser and desktop routes depend on the installed provider and its permissions; they do not all guarantee background operation.
If a task needs foreground interaction, give explicit direction for that interaction. An agent should not silently replace a background task with control of your active desktop. If no installed route can meet the requested experience, it should identify the specific gap and retain completed work.
Check the result
After each meaningful action, inspect the new page or application state. For the final result, check what matters: the saved document, changed setting, submitted object, or downloaded file. A click succeeding is only evidence that the interface accepted an interaction.
For sign-in, the connector must verify access. For a file, confirm the saved output and its location. For a browser session, confirm cleanup after the work is done. Review and deliver results explains these completion checks.