Instruction file imported from zqyoiv/hyz-space-2026 (.cursor/rules/tunnel-config.mdc). Copyright stays with the author.

Tunnel spaces

Per-tunnel behavior and content (steps, optional steps[].stepBackgroundBundled, floorTextureOpacityByStop for textured-floor fade per stop, colors, vignette, titleStepBackgroundBundled, floorMapBundled, interaction, scene): public/risingriver.config.json only. Keys match projects.config.json project id where spaceType is "tunnel".
Vite-bundled assets (any string id referenced from that JSON): register in src/tunnel/tunnelBundledRegistry.js. Do not hardcode projectId === "…" or tunnel-specific imports in ProjectSpace.jsx.
Merging / defaults: src/tunnel/initTunnelConfig.js.
ProjectSpace.jsx: generic tunnel viewer; it reads tunnelCfg and registry maps only.

When adding a new tunnel or asset: update risingriver.config.json, add imports + id to tunnelBundledRegistry.js, and extend initTunnelConfig if new top-level fields are needed.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install tunnel-config and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

tunnel-config

About

Tunnel spaces

Use it

Install tunnel-config and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews