Browser & the CLI
The lel CLI's Browser pane is a placeholder today - drive browser sandboxes with the SDK or the raw REST / CDP / RPC contracts instead.
The lel CLI (@lelantos-ai/cli) is the terminal cockpit for your fleet. Its Compute and Events panes are live, but the Browser pane is a navigable placeholder.
The CLI Browser pane is not implemented. It renders a "coming soon" stub - there is no working lel command to create, list, connect to, or destroy a browser sandbox today. Do not script against it. The CLI is the infrastructure cockpit; browser automation runs over the SDK's /cdp + /rpc rails, not the TUI.
Drive browser sandboxes today
Use one of these supported surfaces instead:
- First-party SDK -
lel.browser.*in@lelantos-ai/sdk. The recommended path. See the Browser SDK reference. - REST API -
POST /browser-sandboxesand friends. See the Browser Sandboxes API reference. - Raw wire contracts - connect directly over CDP or the NDJSON
/rpcAPI.
Create a browser sandbox with cURL
curl -X POST https://api.lelantos.ai/browser-sandboxes \
-H "X-API-Key: lel_your_key_here" \
-H "Content-Type: application/json" \
-d '{"browser": "chromium", "timeout": 600}'The response carries wsEndpoint, ndjsonEndpoint, and accessToken - use them with the CDP or RPC contracts.
What the CLI does cover
For compute sandboxes the CLI is fully functional - list, create, exec, kill, pause, and a live event tail. See the CLI's own README in @lelantos-ai/cli for the keybindings and panes.