Add a packaged-client runtime boundary so the shared UI can talk to local, desktop, remote, and VS Code runtimes through the right transport instead of assuming one same-origin web server. Centralize OpenChamber-owned API access behind RuntimeAPIs, runtimeFetch, and runtime URL helpers, while keeping official OpenCode traffic on the SDK path. Support runtime switching, remote host selection, desktop client credentials, and headless connection links for pairing packaged clients with remote OpenChamber servers. Harden the new auth model by moving long-lived client tokens out of browser URLs, introducing short-lived scoped URL tokens for browser-owned transports, restricting URL-token access to explicit readable/realtime routes, and making client-token management session-scoped or self-scoped as appropriate. Update browser-owned assets and preview proxy flows to work with the split runtime model, including authenticated project icons, preview token propagation, CSP-safe preview bridge injection, and preview proxy auth that survives short-lived URL-token expiry. Tighten Electron security boundaries for packaged clients by gating privileged preload state to trusted origins and requiring explicit confirmation before connect deep-links import or switch remote runtimes. Also refresh agent guidance and project skills so future runtime/API, auth, preview, UI, CLI, settings, locale, and drag-to-reorder work follows the new architecture.
OpenChamber Docs Source
This package is the source-of-truth for OpenChamber public docs content.
Layout
content/docs/*.mdx- English docs pages (source of truth)content/docs/<locale>/*.mdx- translations, mirroring the English filenames (e.g.uk/,zh-cn/,pt-br/); seeCONTRIBUTING.md→ Localizationsidebar.config.json- docs navigation structure for Starlight sidebarCONTRIBUTING.md- authoring guide for adding pages, sections, and translationsDEPLOYMENT.md- release/manual packaging and sync trigger model
Local validation
Run from repo root:
bun run docs:validate
This validates:
- frontmatter (
title,description) exists for every MDX page - sidebar links resolve to existing MDX routes
Deployment model
This repo owns docs content.
Website rendering/deployment happens in openchamber-website (apps/docs).
Use .github/workflows/docs-source.yml to package docs source on release or manual trigger.