Home (Assistant)

Home (nav id copilot) is the assistant-first entry point. Use it to ask questions about your workspace, draft workflows and agents, get setup guidance, and navigate to the right screen without memorising the sidebar.

First-run onboarding

When copilot.config.get reports onboardingComplete=false, Home renders assistant-first onboarding inside the conversation instead of an empty state:

1. Display name — collected as a short text reply.
2. Assistant name — collected as a short text reply.
3. Vertical — inline VerticalStep card (law, healthcare, marketing, coding, or other).
4. Tool selection — inline ToolSelectionStep card listing integrations and MCP tools for your vertical.
5. Configuration plan — inline ConfigurationPlanStep card with per-tool setup status and configure actions.
6. Provider setup — inline cards for LLM (LlmProviderCard), OAuth connectors (OAuthProviderCard), or API keys (ProviderConfigModal).

Progress is persisted through onboarding.session.upsert. Web first-access completion waits until the assistant flow reaches done.

Everyday chat

After onboarding, Home is a full-page chat grounded by workspace RAG (when knowledge sources are indexed — see Knowledge).

• Slash commands — type / to open the slash palette (copilot.slash.list / copilot.slash.parse).
• @-mentions — reference agents, flows, or tools inline (copilot.mention.parse).
• Proactive cards — system events can surface action cards (copilot.proactive.fromEvent).
• Tool proposals — destructive actions escalate to the Inbox for human approval.

For operators who do not work with workflow schemas, describe the outcome in plain Portuguese or English. For example: “Create a launch campaign, draft a LinkedIn post and X thread, ask Ana to review it, then publish next Monday.” Home asks only for missing audience, goal, channel, date/time, source brief, or reviewer. It then shows a workflow preview; it does not save, send, or publish until you approve the current revision.

Marketing automation can guide a safe Google Drive brief → content draft → Gmail review request → human approval → Buffer draft/schedule proposal plan. The preview binds Buffer only when you name it. Drive and Gmail stay clearly marked as unresolved until you choose their exact tools and targets; the assistant does not invent them. The preview does not claim a final Buffer publication. A provider shown in the catalog is not automatically connected. Home names the missing account, permission, folder/channel/reviewer, credential save, or health check. It never calls the integration ready without both a verified credential record and canonical provider-specific connection verification evidence, and it never asks you to paste a token into chat.

If you choose Modify, describe the feedback in normal language. Home collects the change and requires the current full workflow topology before it revises anything. If that topology is not visible, it explains the blocker instead of rebuilding a flow from its name. Any changed revision still needs validation and a fresh approval.

Inline UI in chat

The assistant can render registered inline components (link cards, button groups, run summaries, workflow validation reports, provider setup cards, and onboarding steps). When you ask "show me options" or "where do I configure X", expect an inline card or a navigation button — not instructions to edit files by hand.

Command palette shortcuts

Press Cmd K / Ctrl K and search for copilot, assistant, chat, or help to jump back to Home from any screen.

Related screens