docs: VS Code/Ollama endpoints + env & i18n tooling

.dockerignore

@@ -39,10 +39,15 @@ playwright-report
 blob-report
 
 # Documentation
-# Translations (~51 MB) are excluded — the Docs viewer reads English sources.
-# Screenshots (~1.7 MB) and SVGs (~250 KB) are needed at build time for MDX
-# image resolution (fumadocs-mdx bundles them).
-# Raster sources under docs/diagrams/ only (exported SVGs are required).
+# Issue #2348: The Dashboard Docs viewer reads markdown from `/app/docs` at
+# runtime. The previous `docs/*` block hid every file except openapi.yaml,
+# so the in-product help screen failed with ENOENT for every page.
+# We now keep the English markdown tree plus the docs assets imported by MDX
+# during `next build`, while still dropping the bulky translated docs and
+# extra raster diagram sources that account for most of the docs footprint
+# of the ~50 MB docs directory. The Docs viewer reads the default-locale
+# (English) sources at runtime, so translations are not required in the
+# container image.
 docs/i18n/**
 docs/diagrams/**/*.png
 docs/diagrams/**/*.jpg

README.md

@@ -523,6 +523,19 @@ curl http://localhost:20128/v1/models -H "Authorization: Bearer YOUR_KEY"
 
 You should see your connected models listed. 🎉 That's it — start coding, and OmniRoute auto-routes & falls back for you.
 
+If your client cannot send custom headers, OmniRoute also exposes tokenized compatibility aliases:
+
+```txt
+OpenAI catalog:   http://localhost:20128/vscode/YOUR_KEY/
+OpenAI models:    http://localhost:20128/vscode/YOUR_KEY/models
+OpenAI chat:      http://localhost:20128/vscode/YOUR_KEY/chat/completions
+OpenAI responses: http://localhost:20128/vscode/YOUR_KEY/responses
+Ollama chat:      http://localhost:20128/vscode/YOUR_KEY/api/chat
+Ollama tags:      http://localhost:20128/vscode/YOUR_KEY/api/tags
+```
+
+Use these only for clients that cannot attach `Authorization: Bearer ...`. Header auth remains the preferred mode.
+
 <br/>
 
 ## 📦 More install methods — Docker, source, pnpm, Arch</b></summary>

docs/guides/SETUP_GUIDE.md

@@ -153,6 +153,15 @@ API Key:  [copy from Endpoint page]
 Model:    if/kimi-k2-thinking (or any provider/model prefix)
 ```
 
+If your editor cannot send `Authorization: Bearer ...`, use the tokenized compatibility base instead:
+
+```txt
+Base URL: http://localhost:20128/api/v1/vscode/YOUR_KEY/
+Models URL: http://localhost:20128/api/v1/vscode/YOUR_KEY/models
+Chat URL: http://localhost:20128/api/v1/vscode/YOUR_KEY/chat/completions
+Ollama Tags URL: http://localhost:20128/api/v1/vscode/YOUR_KEY/api/tags
+```
+
 Works with Claude Code, Codex CLI, Gemini CLI, Cursor, Cline, OpenClaw, OpenCode, and OpenAI-compatible SDKs.
 
 For detailed per-tool configuration (Claude Code, Codex CLI, Cursor, Cline, OpenClaw, Kilo Code, Copilot, and more), see the dedicated **[CLI Tools Guide](../reference/CLI-TOOLS.md)**.

docs/reference/API_REFERENCE.md

@@ -154,9 +154,17 @@ Authorization: Bearer your-api-key
 | GET    | `/v1beta/models`            | Gemini                          |
 | POST   | `/v1beta/models/{...path}`  | Gemini generateContent          |
 | POST   | `/v1/api/chat`              | Ollama                          |
+| GET    | `/api/v1/vscode/{token}/`          | OpenAI catalog alias            |
+| GET    | `/api/v1/vscode/{token}/models`    | OpenAI models alias             |
+| POST   | `/api/v1/vscode/{token}/chat/completions` | OpenAI tokenized alias   |
+| POST   | `/api/v1/vscode/{token}/responses` | OpenAI Responses tokenized alias |
+| POST   | `/api/v1/vscode/{token}/api/chat`  | Ollama tokenized alias          |
+| GET    | `/api/v1/vscode/{token}/api/tags`  | Ollama tags tokenized alias     |
 
 All POST routes follow the same shape: `Bearer your-api-key` + Zod-validated JSON body (`v1RerankSchema`, `v1ModerationSchema`, `v1AudioSpeechSchema`, etc., see `src/shared/validation/schemas.ts`). 4xx is returned on schema failure.
 
+For clients that cannot attach `Authorization: Bearer ...`, OmniRoute also accepts API keys in the URL via either query-string compatibility (`?token=...`, `?apiKey=...`, `?api_key=...`, `?key=...`) or the dedicated `/api/v1/vscode/{token}/...` endpoints documented below.
+
 ```bash
 # Rerank
 POST /v1/rerank      { "model": "cohere/rerank-3", "query": "...", "documents": ["..."] }
@@ -608,6 +616,39 @@ GET /api/tags
 
 Requests are automatically translated between Ollama and internal formats.
 
+## Tokenized VS Code / Headerless Aliases
+
+Use these aliases when an integration cannot inject an `Authorization` header and needs the API key embedded in the base URL.
+
+```bash
+# OpenAI-style catalog alias
+GET /api/v1/vscode/{token}/
+GET /api/v1/vscode/{token}/models
+
+# OpenAI-style chat aliases
+POST /api/v1/vscode/{token}/chat/completions
+POST /api/v1/vscode/{token}/responses
+
+# Ollama-style aliases
+POST /api/v1/vscode/{token}/api/chat
+GET /api/v1/vscode/{token}/api/tags
+```
+
+Example:
+
+```bash
+curl https://your-host.example/api/v1/vscode/YOUR_API_KEY/models
+curl -X POST https://your-host.example/api/v1/vscode/YOUR_API_KEY/chat/completions \
+  -H "Content-Type: application/json" \
+  -d '{"model":"auto","messages":[{"role":"user","content":"hello"}]}'
+```
+
+Notes:
+
+- The tokenized aliases reuse the same handlers as `/v1/*` and `/api/tags`; response shapes stay identical.
+- Prefer `Authorization: Bearer ...` whenever the client supports custom headers.
+- URL-based tokens may appear in reverse-proxy logs, browser history, and telemetry outside OmniRoute. Treat them as a compatibility option, not the default authentication mode.
+
 ---
 
 ## Telemetry