Skip to content

runtime API: CORS allowed-origins should be configurable (currently hardcoded) #561

@Hmbown

Description

@Hmbown

Summary

crates/tui/src/runtime_api.rs hardcodes the CORS allowed-origins list. The whalescale UI hits this when developing against a Vite dev server on a non-default port and has to manually pin Vite to port 1420 as a workaround.

Proposal

Add config knob (config.toml [runtime_api] cors_origins = ["..."] and/or env override DEEPSEEK_RUNTIME_CORS_ORIGINS). Defaults stay as today (localhost:7878 + the documented dev origins). When set, the CORS layer in runtime_api.rs uses the configured list.

Tracks

  • whalescale#255 — CORS allowlist hardcoded port (workaround: Vite on 1420)
  • Umbrella: whalescale#228

Acceptance

  • New config field + env override documented in config.example.toml and docs/RUNTIME_API.md.
  • Default behavior unchanged.
  • Whalescale UI confirms it can run on any local port without daemon recompile.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestv0.8.10Targeting v0.8.10

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions