Docs › Agent
Browser tools
Let the agent open your running app, read the page and the console, and click through it.
The agent can drive a browser against your own running application. It is for checking work it just did: open the page, read what the console says, click the thing that is supposed to work now, rather than for browsing the web.
What it can do
| Tool | What it does |
|---|---|
| browser_navigate | Opens a URL. |
| browser_dom | Reads the page structure, so it can find what to click. |
| browser_console | Reads console output, including errors your app logged. |
| browser_click | Clicks an element. |
Why it matters
Without it, a change to a page is verified by reading the diff, which tells you the code changed, not that the page works. With it, the agent can make a change, load the page and read the error it caused, in the same run.
It drives a browser AstraCode controls, not the one you are signed into. It cannot see your sessions, your cookies or your tabs.
Turning it off
Set astracode.agent.browserTools to off. The tools disappear from the agent entirely rather than being offered and refused, so it does not waste a step discovering they are unavailable.
All documentation
Get started
Agent
- Agent overview
- Approvals and permissions
- Plan mode
- What the agent can do
- Running commands
- Browser tools
- Checkpoints and undo
- Infrastructure as code
- Running several agents at once