AI workspace

web-nuxt exposes a complete AI workspace instead of routing every workflow into one playground:

• /dashboard/ai-chat is the persistent conversational product surface, including history and multi-turn continuation.
• /dashboard/ai-playground is AI Studio for image, video, audio, and other structured generation workflows.
• /dashboard/usage combines Chat and provider generation usage, including image, video, audio, requests, tokens, credits, daily activity, and model breakdown.

Why it matters

All three surfaces share the same session lifecycle, so they already understand:

• auth state
• guest sessions
• available credits
• API key lifecycle
• conversation and generation history
• provider-specific inputs
• user-scoped usage and billing data

Site owners can keep the native Workers AI binding or configure any HTTPS OpenAI-compatible Base URL and API Key in the admin AI upstream settings. The credential remains server-side in node10-ai-service; users only see enabled models, never the upstream key.

Recommended user path

1. Start from /guest-demo or /dashboard
2. Open /dashboard/ai-chat for conversational work or /dashboard/ai-playground for generation
3. Continue previous conversations or create the first result
4. Review /dashboard/usage before upgrading to a full account or a higher plan

What product teams should avoid

• Do not ask first-time users to paste a manual API key before they understand the product.
• Do not collapse Chat and structured generation into competing interfaces; keep each entry point tied to a distinct job.
• Do not separate credits, AI generation, and account state into unrelated pages without a guided default path.