Files
OmniRoute/changelog.d/features/10697-vscode-copilot-guide.md
Diego Rodrigues de Sa e Souza d7368e243d docs(guides): DASHBOARD_ALLOW_EMBED is a build-time flag, not a runtime one (#10697)
* docs(guides): DASHBOARD_ALLOW_EMBED is build-time, not a runtime flag

The VS Code guide told operators to "start OmniRoute with
DASHBOARD_ALLOW_EMBED=vscode". Next.js compiles headers() into the route
manifest, so next.config.mjs reads the variable while the bundle is built —
exporting it in front of an already-built server does nothing, which is the
exact trap anyone on `npm install -g omniroute` or the Docker image falls into.

Documents the build-time nature, the working from-source recipe, and which
install paths can enable it at all. ENVIRONMENT.md and .env.example already
said build-time; this aligns the how-to with them and with the extension's own
fallback message.

* docs(changelog): announce the VS Code Copilot Chat integration

The release notes only mentioned OmniCopilot in passing, inside the DASHBOARD_ALLOW_EMBED bullet — a reader would never learn the extension exists. Adds the fragment that says it plainly, with both store links.

---------

Co-authored-by: Xiangzhe <bakryun0718@proton.me>
2026-08-18 20:35:52 -03:00

768 B

  • docs(guides): OmniRoute now serves VS Code's native Copilot Chat model picker through the OmniCopilot extension (Marketplace · Open VSX — Cursor, Windsurf, VSCodium, Theia…) — no Copilot subscription needed since VS Code 1.122. New docs/guides/VSCODE-COPILOT.md covers setup, how the picker collapses the dual-prefix catalog via GET /v1/models?prefix=alias, and the build-time DASHBOARD_ALLOW_EMBED=vscode flag that renders the dashboard in an editor tab (#10697)