Attach a running app
Start the app’s local development server, then ask the agent to attach its address to the current thread. The server must use a loopback HTTP address such as http://127.0.0.1:3000.
hai web-connector attach http://127.0.0.1:3000 --name preview
hai web-connector listHaicue opens a LiveApp tab. It displays the real running app, including development-server reloads.
Inspect what is on screen
The Web Connector skill lets the agent inspect the page’s DOM, console errors, network activity, and observed assets. Give it a concrete check:
Open the preview, submit the empty form, and check that each required
field has a visible error. Inspect the console for errors.Agents can also listen for selected events and exchange messages with apps that support that interaction. Inspection is scoped to the attached app; it is not full access to every browser tab.
Recover a stopped preview
If the local server stops, restart it. The connector can recover when the upstream returns. Agents can reload the preview or reattach a failed connector without creating another tab.
hai web-connector reload CONNECTOR_ID
hai web-connector reattach CONNECTOR_IDClose and restart
Closing the tab stops its connector. The upstream app server is separate; the agent that started it can stop it when it is no longer needed. LiveApp tabs are runtime state and need to be attached again after Haicue restarts.
Use Chrome DevTools when a task needs an existing browser login, cookies, or detailed browser performance tools.
Use Chromium and DevTools for browser work
Use Browser control when you need a full Chrome session, an existing debug-browser login, or DevTools inspection. LiveApps keeps a local app inside the thread; browser control lets the agent work directly with a Chromium-based browser.