Repository navigation
v3.5.5
✨ New Features
-
feat(docs): integrate multi-page documentation into OmniRoute dashboard (#1969)
-
feat(settings): add request body limit setting (#1968)
-
feat(auth): add Gemini CLI OAuth client secret default (#1974)
-
feat(models): expose models.dev context windows in /v1/models (#1972)
-
fix(db): resolve legacy encryption fallback causing re-encryption loops (#1941)
-
fix(auth): fix Codex assistant final_answer response sanitization (#1965)
-
feat(providers): Implement Image Generation and Editing capabilities for ChatGPT Web, including in-band chat image generation and caching (#1606).
-
feat(ui): Integrate OpenCode Zen/Go API tool logo SVG and polish API key copy-to-clipboard interactions (#1607).
-
feat(providers): Integrate AgentRouter as a new OpenAI-compatible passthrough provider with $200 free credits via sign-up (Issue #1572).
-
feat(ui): Implement on-demand per-model testing in the provider dashboard, allowing single-token diagnostic checks without triggering rate-limits (Issue #1532).
-
Node.js 24 Compatibility Warning: Added a proactive version incompatibility warning on the login page to guide users to the stable Node.js 22 LTS, preventing native sqlite binding crashes.
-
Context Relay Combo Strategy: Added the new
context-relaycombo strategy with priority-style routing, structured handoff summary generation once quota usage reaches the warning threshold, and handoff injection after the next real account switch. -
Global Context Relay Defaults: Added global Settings defaults plus combo-level configuration for
handoffThreshold,handoffModel, andhandoffProviders, so new or unconfigured combos can inherit the feature consistently.
🐛 Bug Fixes
-
fix(mitm): Compile MITM utilities as NodeNext ESM during prepublish, copy the CommonJS MITM server into the standalone artifact, and resolve MITM data paths without relying on Next.js aliases in packaged runtime.
-
fix(build): Move the local
.tmp/wine32Wine prefix out of the isolated Next.js build path so Windows Electron packaging artifacts cannot triggerEACCESscans during Node 24 builds. -
fix(build): Copy the
wreq-jsnative runtime directory into the isolated Next.js standalone output so packaged Playwright/E2E starts can load the instrumentation hook on Linux. -
fix(api): Validate the Codex Responses websocket bridge and
/v1/batchesJSON payloads with Zod before use, keepingrequest.json()route validation green and returning explicit 400 responses for invalid bodies. -
fix(providers): Add explicit typing to provider alias and category helpers so the strict
typecheck:noimplicit:coreCI gate passes. -
fix(ui): Keep the upstream proxy provider detail page labeled with a fallback "Managed via Upstream Proxy Settings" management surface when translations are unavailable.
-
fix(electron): Harden the production desktop CSP by removing
unsafe-evaloutside development and adding object, base URI, form action, frame ancestor, and worker restrictions. -
fix(cli): Replace shell-interpolated setup and privileged command execution paths with argument-based
spawn/execFilehelpers for database setup, Tailscale sudo commands, MITM DNS edits, and certificate install/uninstall flows. -
fix(ui): Keep provider icons resilient by using direct
@lobehub/iconscomponents first, then local PNG/SVG fallbacks, avoiding the@lobehub/uipeer runtime in the dashboard. -
Proxy Connection Healthchecks: Applied proxy resolution per connection in the sweeping loop (
tokenHealthCheck.ts) and global provider validation sweeps, resolving Node 22 bypass and improving proxy stability (#1051, #1056, #1061). -
Security Vulnerability Remediation: Resolved multiple CodeQL scanning alerts including SSRF in model sync, insecure randomness in web crypto (
generateSessionId), and incomplete URL sanitization. -
Context Relay Typing & Synchronization: Reverted out-of-scope test breakages and resolved
handoffProviderand responseinputextraction payload typing. -
Legacy OpenAI-Compatible Responses Routing: Fixed legacy/imported OpenAI-compatible providers (for example
openai-compatible-sp-openai) incorrectly routing Chat Completions traffic to/chat/completionswhen the real provider node was configured asapiType: "responses". OmniRoute now treatsproviderSpecificData.apiTypeas authoritative across routing, executors, and translator tools, avoiding false empty-content failures during combo/provider smoke tests (#1069). -
Gemini PDF Attachment Integration: Fixed payload generation and format for parsing
inline_dataand generic base64 sources for deep Gemini PDF routing (#993, #1021). -
Vercel AI SDK Fallbacks: Mapped
max_output_tokenstomax_tokensfor strict OpenAI-compatible providers, resolving errors from standard AI agents and frameworks (#994). -
External Auth & UI Reliability: Handled null
statefailures in Cline OAuth exchange (#1016), added 3rd-party 400 error patterns to combo fallback (#1024), and resolved desktop sidebar layout and popover overflows (#1039, #1001). -
Context Relay In-Flight Deduplication: Prevented duplicate handoff generation for the same session/combo while an earlier summary request is still in flight.
-
Context Relay Provider Gating: Aligned runtime behavior with configuration so explicit
handoffProvidersexclusions, including an empty array, now disable handoff generation as expected.
🛠️ Maintenance & Dependabot
- Updated Sub-dependencies: Bumped
honoto4.12.12and@hono/node-serverto1.19.13to patch critical security gaps (#1063, #1064, #1067, #1068).
📚 Documentation
- Documentation Synchronization: Updated system documentation (README, Architecture, Features, Tools, Troubleshooting) and synced
i18nconfigurations to match the v3.5.5 context relay patterns and proxy troubleshooting steps. - Context Relay Delivery Notes: Documented the current architecture, runtime flow, and Codex-focused scope in the feature docs, changelog, and agent guidance.