Repository navigation
Windows 1.0.0 runtime: /scenes and /scene/<id> routes return HTTP 500 (root canvas works) #876
Description
Activity
I also have the same problem.
/scenesis not working. I was trying to create a scene using OpenCode (via MCP) and it successfully created the scene with an ID, and instructed me to see it on/scene/[scene_id]but it neither opened/scenesnor/scene/[scene_id]. It's an internal server error.Thanks for the second report. Keeping this open as a runtime bug: successful MCP saves do not establish that the web runtime’s
/scenesand/scene/<id>routes can load those scenes.Please include the installed CLI version, the running editor runtime version reported by
pascal doctor, and the server-side error/stack produced when opening one failing route. A newly created minimal scene would help separate the route failure from project contents. The browser’s generic error ID alone does not identify the server failure. Please remove tokens and personal paths from logs before posting.
Environment
@pascal-app/cli1.0.0, Node 24.15.0pascal start+pascal editor --no-openhttp://pascal.localhost:60994; MCP service healthy on loopback (scenes save/load via MCP work fine)Repro
pascal start && pascal editor --no-open/scenes, or to/scene/<id>(any saved scene, project-bound or not)Actual: HTTP 500 server-side. The page renders the error boundary: "This page couldn't load — A server error occurred. Reload to try again." (error id
3227098399in one case). Client console shows a minified React error #441. Navigating client-side from/to/scenes(clicking "Open saved scenes") fails the same way after the route transition.Expected: the scenes list / scene editor routes render.
Notes
/route and the full editor canvas load and work; only the scenes/scene routes 500 (both on direct load and after client-side navigation).create_room→save_scene→load_sceneround-trips geometry exactly on this same install, so the data layer is fine — this looks like an SSR/prerender route issue in the web runtime.