One chat, no wizard#
A new workspace opens directly into chat at /dashboard/{workspaceId}. There
is no multi-step setup wizard to complete before you can talk to Sidekick —
type the first thing you want done, the same way you'd open a conversation
with any chat assistant.
Onboarding happens implicitly, inline, as part of that conversation. If your request needs something the workspace doesn't have yet — a model source, a connected tool — Sidekick asks for it at the moment it's needed, not as a gate in front of chat.
What Sidekick asks for, and when#
| Sidekick needs | What you see |
|---|---|
| A model source | If neither managed inference nor a BYOK provider key is configured, Sidekick explains what's missing before it can respond, with a link to model configuration |
| A tool connection | An inline connect widget appears in the conversation the first time a request needs that integration — for example, asking Sidekick to triage Gmail prompts an inline Gmail connect card |
| Workspace or trust decisions | Handled once at workspace creation (the human role and starting trust posture), not repeated as onboarding steps |
You never leave the conversation to connect a tool or supply a key — the prompts are inline widgets in the same chat thread.
Model source#
Every workspace needs a working model source before Sidekick can respond. Two options:
| Model source | What it means |
|---|---|
| Managed | LumenFlow provides the inference endpoint — nothing to configure |
| BYOK | You supply an API key for your own provider (see API Key Management) |
If neither is set, Sidekick's first reply explains exactly what's missing and links to where to fix it, rather than failing silently or showing a generic error.
Connecting tools inline#
Tool connections aren't a checklist you work through up front. They surface as inline widgets exactly when a request needs them — ask Sidekick to check your calendar and, if calendar access isn't connected yet, an inline connect card appears in that same message. Approve it once and the request continues.
info Nothing about this flow reads or writes a long-lived workspace credential into your shell, a repository, or command history. Provider connections use scoped OAuth installations; model keys are entered once into the encrypted settings store. See API Key Management for how those secrets are handled.
Next step#
Fine-tune billing, budgets, trust, and model configuration in Settings.