Web Workspace Shell
The web workspace shell owns the product navigation structure, responsive layout expectations, and feature grouping for the Nuxt app.
Implemented
Section titled “Implemented”- Chats, Connectors, Library, Response Templates, Skills, Spaces, and account controls are reachable through shared navigation.
- The shell supports responsive desktop and mobile layout patterns.
- Intelligence grouping keeps knowledge and assistant-shaping surfaces together.
- Top-header submenus use Nuxt UI default triggers, close after route navigation, and the Spaces submenu marks the active scope with an explicit
In scopestate. - Desktop sidebar chat-list scrollbars are thin, muted, and flush to the content edge while section controls keep enough inset spacing.
- The sidebar account menu groups Settings links with All Settings and Profile above a separator and API keys below it.
- The
/settingspage uses the same authenticated app shell as other workspace settings surfaces and stages user setting changes behind the shared page-level Save action. /settings/profileincludes Better Auth profile controls for full name and avatar image. Email/password avatars upload through auth-owned first-party storage with a 1 MB input cap, trusted browser-origin checks, and a managed auth path resolved by the web runtime; SSO avatar images come only from trusted provider claims and arbitrary image URL entry is not supported./settingsincludes a final Account area for profile and account-access pages such as API keys./settingsincludes the private-chat preferenceAsk clarifying questions, which controls optional source-choice and bounded detail-clarification prompts.- Spaces are treated as organizational context rather than an auth or data-boundary replacement.
- Pre-release local Prisma-backed databases must keep
user-settingsrows in the canonical shape. The one-time repair for older localoptionalChatClarificationRequestsEnableddata was run on 2026-06-24 and removed; if a restored local snapshot reports old-shape drift, clear/regenerate local data or add a reviewed one-off repair instead of adding runtime compatibility reads.
Current Limits
Section titled “Current Limits”- Focused-chat boundary hints need a deeper UX pass.
- Branded error routes remain deferred.
- Whitelabel theme consumption waits for accepted governance-owned brand settings.
Read Next
Section titled “Read Next”Canonical Sources
Section titled “Canonical Sources”docs/features/web-workspace/spec.mddocs/features/user-settings/spec.mddocs/features/web-workspace/decisions/docs/features/web-workspace/stories/docs/features/web-workspace/tests/apps/web/app