Bybon VS Code Bridge

This is the official VS Code-side adapter for Bybon Assistant. It runs only on 127.0.0.1 and accepts requests only with a per-user token stored in ~/.bybon/vscode/bridge-token (or the path from BYBON_VSCODE_TOKEN_FILE). Each VS Code window receives its own dynamic local port and publishes a small focused-window registry under ~/.bybon/vscode/bridges. This is important when several VS Code windows are open at the same time.

The extension does not classify voice commands and does not execute arbitrary shell text. Bybon sends an allowlisted operation or a previously inspected project candidate.

Local development

1. Open integrations/bybon-vscode in VS Code.
2. Press F5 and choose the Extension Development Host.
3. Install/run the Bybon Assistant API in the original VS Code window.
4. The bridge token is created automatically on first activation.

The current bridge endpoints are:

• GET /health
• GET /context
• GET /project
• POST /execute for allowlisted operations
• POST /run for an inspected candidate id
• GET /runs/:id

The default setting bybon.vscodeBridgePort: 0 means "choose a separate port for this window". Set a fixed port only for a controlled single-window setup.

Package and publish

The publisher field in package.json must match the publisher ID from the Visual Studio Marketplace. It is not the Microsoft account email. After that:

npm install --global @vscode/vsce
vsce package
vsce publish

For the first local test, install the generated VSIX instead of publishing it. Use a short-lived credential or the Marketplace trusted publishing flow for CI; do not commit a Personal Access Token.