Drive Chromium through DevTools
Haicue’s browser-control skill drives Chrome, a Chromium-based browser, through the Chrome DevTools Protocol. The agent can navigate pages, interact with forms, inspect the page structure, take screenshots, and examine console errors and network requests.
This gives the agent context from the website as it actually runs. It can compare what appears on screen with the intended result and investigate what went wrong.
Ask for a browser check
Open the local website in the DevTools browser. Walk through the
signup form, check the validation messages, and inspect the console
and failed network requests. Save screenshots and findings in this thread.Give the agent the URL, the interaction to try, and the result you expect. Say whether it should only report problems or also fix them.
Check the docs at http://127.0.0.1:4186/docs on desktop and mobile.
Try search, navigation, and copying an example. Report anything that
is broken or hard to use, with a screenshot of each problem.Connect the browser
Ask the agent to use the Haicue DevTools skill. Its bundled helper connects to a debugging-enabled browser or launches Chrome with a separate debug profile.
The debug profile has its own sign-ins. It does not automatically use your everyday browser’s logged-in accounts. If the task needs an account, sign in to the service in that browser.
Use the page as evidence
The agent can read the page structure to find controls, use screenshots to check the visible result, and inspect network requests or console errors to explain failures. For example, it can distinguish a form that never submits from a request that reaches the server and fails.
During skill development, browser inspection can also reveal a repeatable API or command path. The resulting skill can use that path for future work when it is more reliable than driving the page.
Browser control or LiveApp?
Use browser control for a full browser session, browser-based services, and DevTools investigation. Use a LiveApp to keep a running local app inside the thread, beside the conversation.
Both let an agent inspect what it is working on. Choose the surface that fits the task: a browser tab for website work, or a thread tab for an interactive local tool.