Silently surfaces OMP agent file edits and diffs inside VS Code — without stealing focus from your terminal.
The extension is the VS Code client for the OMP bridge. Each OMP process runs its own local TCP server; each VS Code window discovers only the OMP endpoints attached to its own terminals, maintains persistent connections, and opens edits in the correct window.
How it works
- OMP starts an ephemeral localhost server and publishes an authenticated endpoint record under
~/.omp-vscode/servers/. - Each VS Code window matches endpoint metadata to its own terminals using process ancestry, with workspace cwd as a fallback.
- The client registers the window, terminal, and workspace with each matching OMP process over one persistent newline-delimited JSON connection.
- OMP routes file edits using the logical session ID from its session manager; the client opens diffs or files in the owning window.
- Heartbeats, reconnects, atomic endpoint records, and per-process random tokens keep the bridge resilient and local.
No data leaves your machine — the bridge uses loopback TCP and local endpoint metadata.
Cross-environment Windows↔WSL endpoint discovery is intentionally deferred. Same-environment and Remote-WSL operation are the supported paths for this release.
Requirements
- Visual Studio Code
1.85.0or newer. - OMP with the companion
bridge-serverextension deployed.
Commands
| Command | Title |
|---|---|
ompBridge.showLogFile |
OMP Bridge: Show Log File — opens the bridge output channel. |
ompBridge.showSessions |
OMP Bridge: Show Sessions — lists detected OMP sessions and connection details. |
The status bar shows connected versus detected sessions. Click it to inspect terminal, workspace, PID, session, and last-edit details.
Building from source
cd src/vscode
npm install
npm run compile # emits ./out/extension.js via tsc
code --install-extension omp-vscode-bridge-0.1.0.vsix # after packaging
License
MIT © 2026 OMP Authors