# Local development against the deployed backend.
#
# The dev server proxies /api and /health to VITE_API_PROXY_TARGET, so the app
# talks to the deployment through its own origin — which is what keeps the
# session cookie (Secure, SameSite=Lax, host-scoped) working in the browser.
VITE_API_BASE_URL=/api/v1
VITE_API_PROXY_TARGET=https://mcp.krowforce.com

# Owliver's agent endpoint.
#
# Relative FOR DEVELOPMENT ONLY: vite proxies it to VITE_API_PROXY_TARGET above.
# The production image cannot use a relative value — nginx serves it as a static
# path and answers a run POST with 405 — so Dockerfile passes an absolute URL as
# a build arg instead. Changing this file does not change what ships.
#
# Empty is what it was, and an empty value is not a broken panel: the provider
# answers every question with "Owliver is not configured on this deployment",
# deliberately, because a panel that quietly does nothing is harder to diagnose.
VITE_AGENT_API=/api/v1