Chrome Extension Browser Automation
A rysh pane that lives in your browser's side panel and drives the page.
What you'll see
- The extension's side panel is a real rysh pane -- same modes and AI agent -- targeting the browser.
- It connects to the session over a NATS-over-WebSocket link, like every other client.
- Because the agent lives in the pane (not the page), the conversation persists across navigations.
- Wrap: ask the agent to fill a form or pull data and it acts on the live tab -- a browser copilot.
Commands shown
echo 'Chrome side panel = a rysh pane whose target is the browser'
echo 'Extension <-> session over NATS WebSocket -- same bus as the CLI'
echo 'Navigate to a new page -> the agent keeps the whole conversation'
echo 'Ask -> the agent acts on the live tab. A browser copilot in rysh.'
Keys used
Enter
Transcript
0:00A rysh pane that lives in your browser's side panel and drives the page.
0:05The Chrome extension's side panel is a real rysh pane -- same modes, same AI agent -- except its job is to drive the browser you are looking at.
0:15It connects to your session the same way every other client does: a NATS-over-WebSocket link back to the bus.
0:26Because the agent lives in the pane and not the page, your conversation persists across navigations -- click a link, load a new URL, the agent keeps its full context.
0:38Ask the agent to fill a form or pull data, and it acts on the live tab -- a browser copilot wired into your terminal.
Key takeaway
The Chrome side panel is a rysh pane connected over NATS WebSocket whose agent drives the browser and keeps context across navigations.