On the right side of the onboarding wizard sits a compact AI rail — a chat surface specifically scoped to help you finish setup. Ask it for industry-specific advice ("what pipeline stages do agencies typically use?"), tell it to take a small action ("load sample data," "skip the invite step"), or just ask where you are in the flow.

It runs the same Laureo AI as the main app's chat, but with a different persona, a smaller toolset, and stricter guardrails — the copilot is a guide, not a power tool.

The copilot has access to a curated subset of tools — read-only operations plus four onboarding-specific writes:

• Read your CRM — list companies, people, deals, pipelines, etc. to answer "what's already here?" questions.
• Mark an onboarding step complete or skipped via the mark_onboarding_step tool.
• Load sample data for the org via the load_sample_data tool.
• Send you to the inbox-connect flow via the request_inbox_connection tool (it opens the OAuth prompt for you).
• Invite a single teammate via the invite_team_member tool (one at a time, with explicit name/email/role).

By design, the onboarding copilot has no destructive or outbound tools:

• It cannot delete any record (company, person, deal, activity, anything).
• It cannot send email, log a call, send an SMS, or push to any external integration.
• It cannot edit existing records — no field updates, no stage changes, no reassignment.
• It cannot bulk-invite or modify role permissions.

If you ask the copilot to do something it doesn't have a tool for, it will say so and point you to the right surface (usually a wizard step or an admin page). Two independent gates enforce this: the prompt-level filter that hides non-onboarding tools, and a dispatch-site allowlist check that rejects any tool call the prompt shouldn't have produced. The double-gate is defense against prompt-injection from content the AI reads.