open-swe/ui/vercel.json

{
  "framework": null,
  "buildCommand": "bun run build",
  "outputDirectory": ".output/public",
  "rewrites": [
    {
      "source": "/dashboard/api/:path*",
      "destination": "https://open-swe-v3-f2834ffc0df05a46a10262a9690e8490.us.langgraph.app/dashboard/api/:path*"
    },
    {
      "source": "/(.*)",
      "destination": "/_shell.html"
    }
  ]
}
feat: proxy /dashboard/api/* through Vercel to dodge third-party cookie blocks (#1303) Browsers (Safari, Brave, Firefox, increasingly Chrome) refuse to set or send SameSite=None cookies cross-site. With the frontend on openswe.vercel.app and the API on *.langgraph.app, the osw_session cookie from `/auth/callback` was being silently dropped, so every subsequent /me call returned 401. Adding a Vercel rewrite makes the API same-origin from the browser's point of view: the request goes to openswe.vercel.app/dashboard/api/..., Vercel proxies it to the LangSmith deployment, and the Set-Cookie comes back attributed to openswe.vercel.app — a first-party cookie that all browsers honour. Pair with the matching deployment-side config changes: - GitHub App callback URL → https://openswe.vercel.app/dashboard/api/auth/callback - DASHBOARD_API_BASE_URL → https://openswe.vercel.app (LangSmith env) - VITE_DASHBOARD_API_BASE_URL → unset / empty (Vercel env) 2026-05-15 12:23:27 -07:00			`{`
chore(ui): deploy dashboard as a static SPA instead of SSR (#1395) Enable TanStack Start SPA mode so the build prerenders a static shell (/_shell.html) and emits a fully static bundle under .output/public, removing the Nitro serverless function from the Vercel deploy. The dashboard is a thin client (all data via client-side fetch to the FastAPI /dashboard/api/*), so SSR rendered nothing of value. Point Vercel at the static output and add a SPA catch-all rewrite to the shell for client-side routing, keeping the API proxy rewrite first. 2026-06-03 15:56:46 -04:00			`"framework": null,`
			`"buildCommand": "bun run build",`
			`"outputDirectory": ".output/public",`
feat: proxy /dashboard/api/* through Vercel to dodge third-party cookie blocks (#1303) Browsers (Safari, Brave, Firefox, increasingly Chrome) refuse to set or send SameSite=None cookies cross-site. With the frontend on openswe.vercel.app and the API on *.langgraph.app, the osw_session cookie from `/auth/callback` was being silently dropped, so every subsequent /me call returned 401. Adding a Vercel rewrite makes the API same-origin from the browser's point of view: the request goes to openswe.vercel.app/dashboard/api/..., Vercel proxies it to the LangSmith deployment, and the Set-Cookie comes back attributed to openswe.vercel.app — a first-party cookie that all browsers honour. Pair with the matching deployment-side config changes: - GitHub App callback URL → https://openswe.vercel.app/dashboard/api/auth/callback - DASHBOARD_API_BASE_URL → https://openswe.vercel.app (LangSmith env) - VITE_DASHBOARD_API_BASE_URL → unset / empty (Vercel env) 2026-05-15 12:23:27 -07:00			`"rewrites": [`
			`{`
			`"source": "/dashboard/api/:path*",`
chore: point Vercel rewrite at the prod LangSmith deployment (#1304) PR #1303 was merged before this URL change landed on the branch. Updates the rewrite destination from the open-swe-test deployment to the prod open-swe-v3 deployment so openswe.vercel.app proxies to the right backend. 2026-05-15 13:37:07 -07:00			`"destination": "https://open-swe-v3-f2834ffc0df05a46a10262a9690e8490.us.langgraph.app/dashboard/api/:path*"`
chore(ui): deploy dashboard as a static SPA instead of SSR (#1395) Enable TanStack Start SPA mode so the build prerenders a static shell (/_shell.html) and emits a fully static bundle under .output/public, removing the Nitro serverless function from the Vercel deploy. The dashboard is a thin client (all data via client-side fetch to the FastAPI /dashboard/api/*), so SSR rendered nothing of value. Point Vercel at the static output and add a SPA catch-all rewrite to the shell for client-side routing, keeping the API proxy rewrite first. 2026-06-03 15:56:46 -04:00			`},`
			`{`
			`"source": "/(.*)",`
			`"destination": "/_shell.html"`
feat: proxy /dashboard/api/* through Vercel to dodge third-party cookie blocks (#1303) Browsers (Safari, Brave, Firefox, increasingly Chrome) refuse to set or send SameSite=None cookies cross-site. With the frontend on openswe.vercel.app and the API on *.langgraph.app, the osw_session cookie from `/auth/callback` was being silently dropped, so every subsequent /me call returned 401. Adding a Vercel rewrite makes the API same-origin from the browser's point of view: the request goes to openswe.vercel.app/dashboard/api/..., Vercel proxies it to the LangSmith deployment, and the Set-Cookie comes back attributed to openswe.vercel.app — a first-party cookie that all browsers honour. Pair with the matching deployment-side config changes: - GitHub App callback URL → https://openswe.vercel.app/dashboard/api/auth/callback - DASHBOARD_API_BASE_URL → https://openswe.vercel.app (LangSmith env) - VITE_DASHBOARD_API_BASE_URL → unset / empty (Vercel env) 2026-05-15 12:23:27 -07:00			`}`
			`]`
			`}`