Skip to content

fix(dashboard): proxy SSH source requests and correct the dev:web README #5270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
huangruiteng merged 2 commits into from
Sep 28, 2026
+15 −13
Merged

fix(dashboard): proxy SSH source requests and correct the dev:web README #5270

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
741845f
fix(dashboard): proxy SSH source requests in the Vite dev server
songoow Sep 28, 2026
ca89d0d
docs(dashboard): state what npm run dev:web serves
songoow Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 11 additions & 13 deletions apps/presentation/dashboard/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,9 @@ run in the full development and packaged personal-workspace browser smokes.

## Fresh Clone Public Preview

No private LoopX state is required for the first dashboard preview. The
app bundles `examples/status.example.json` as its public-safe example source,
so a fresh checkout can validate and open the UI before starting any local
status server:
No private LoopX state is required to validate the dashboard. The app bundles
`examples/status.example.json` as its public-safe example source, and
`smoke:demo-readiness` checks it without a local status server:

```bash
cd apps/presentation/dashboard
Expand All @@ -45,15 +44,14 @@ npm run smoke:demo-readiness -- --skip-browser
npm run dev:web
```

Then open `http://127.0.0.1:5173/`. Use the bundled example source for a public
demo, or switch to a loopback status URL only after you have started
`loopx serve-status` locally. Do not commit `status.local.json` or live
status exports; they can contain local registry/runtime paths and private
project summaries.

`npm run dev:web` starts only the Vite UI with the bundled example. `npm run dev`
also starts the loopback status and Chat services and therefore requires a
Python 3.11+ interpreter; see the development section below.
`npm run dev:web` starts only the Vite UI at `http://127.0.0.1:5173/`. The
workspace reads `/status.json` through the Vite proxy from `loopx serve-status`
on port 8766 and the Chat APIs from `loopx chat` on port 8767, so without those
services it opens on a status-load error. Start them locally, or use
`npm run dev`, which also starts the loopback status and Chat services and
therefore requires a Python 3.11+ interpreter; see the development section
below. Do not commit `status.local.json` or live status exports; they can
contain local registry/runtime paths and private project summaries.

Personal Workspace owns Goal, Task, Chat, output, and report workflows. Run
`loopx dashboard` for the installed local workspace; see the
Expand Down
4 changes: 4 additions & 0 deletions apps/presentation/dashboard/vite.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,10 @@ export default defineConfig({
target: "http://127.0.0.1:8767",
changeOrigin: false,
},
"/api/ssh-source": {
target: "http://127.0.0.1:8767",
changeOrigin: false,
},
},
},
preview: {
Expand Down
Loading