A preview gives local access to an app port. For a remote app, Vibeke forwards the port through the host connection. The local proxy uses separate origins and loopback addresses.
A browser pane shows an interactive Chromium page inside the terminal. It uses a separate browser profile. Vibeke does not expose the Chrome DevTools Protocol endpoint.
Open a browser pane
-
Check browser availability:
vibeke browser status -
If Chromium is unavailable, run
vibeke browser install. Confirm the download when prompted. -
Open a browser pane for your app:
vibeke browser pane http://localhost:3000 --split right
The terminal must support graphics. Use vibeke doctor to check terminal support.
A browser pane supports page input, navigation, screenshots, and fixed device viewports. Remote previews keep the app on its original host.
Agent browser tools
An agent can open a browser session through the API. It can navigate, click, type, inspect page content, and capture screenshots. Console and network logs are also available.
Each session has a separate browser context. An agent can control its own browser sessions and sessions for panes that it created.
Destination policy limits browser access. Script evaluation needs an explicit browser.script capability.
Use vibeke browser list to find a session ID. Replace <session> with that ID in these commands:
vibeke browser snapshot <session>
vibeke browser console <session> --level error
vibeke browser network <session> --failed
vibeke browser screenshot <session> --full-page --out page.png
View and control a session
-
Open the agent browser in a pane:
vibeke browser watch <session> --split right -
Take control:
vibeke browser take-over <session> -
Use the page controls as necessary.
-
Return control to the agent:
vibeke browser release <session>
While you control the page, agent browser commands return human_control. This prevents simultaneous input from you and the agent.
See the browser commands and control API for arguments.