Install
Install the xcsh Chrome Extension from the Chrome Web Store, then connect the native-messaging bridge to the xcsh CLI. This is a one-time setup for developers and sales engineers.
Prerequisites
Section titled “Prerequisites”- Google Chrome (or a Chromium-based browser)
- The xcsh CLI installed
Install the extension
Section titled “Install the extension”-
Open the Chrome Web Store listing. Go to the xcsh extension page.
-
Add it to Chrome. Click Add to Chrome, then confirm Add extension.
-
Verify the extension ID. Open
chrome://extensions, enable Developer mode (top-right toggle), and confirm the xcsh card shows the ID:klajkjdoehjidngligegnpknogmjjhkcThis is the fixed ID the native-messaging bridge expects.
Connect the native-messaging bridge
Section titled “Connect the native-messaging bridge”-
Run the setup command to register the native-messaging host:
Terminal window xcsh chrome setup -
Reload a console tab. Open or reload a tab on your F5 Distributed Cloud console (
*.volterra.us). -
Confirm the connection. Right-click the extension icon → Options — the status should show Connected to xcsh (green).
Updating
Section titled “Updating”Chrome updates the extension automatically from the Web Store. To force an update now, open chrome://extensions, enable Developer mode, and click Update.
Develop locally (unpacked)
Section titled “Develop locally (unpacked)”Working on the extension itself? Build a keyed unpacked copy that loads under the same canonical ID as the store build, so the native bridge works while you iterate.
-
Build a dev copy:
Terminal window bun run build:devThis builds
dist/and injects the store’s publickey, pinning the unpacked ID toklajkjdoehjidngligegnpknogmjjhkc(the same ID store users get). -
Load it. At
chrome://extensions(Developer mode on), click Load unpacked and select thedist/folder. Confirm the ID matches the canonical ID above. -
Register the bridge with
xcsh chrome setup, then reload a console tab.