Quick Analysis vs Project Analysis

Read time: ~5 minutes · Series: Analyst getting started · Previous: Why it can't stay in chat · Next: Plan → Execute → Report

The one-line distinction

Both share the same IDE, the same tables, and the same Agent—the difference is whether you have a "plan contract + Execute gate + Report delivery."

Quick Analysis: what it's for

Good for:

• "What values does this table's status have?"
• "Try last 30 days of GMV, and check the NULL ratio while you're at it"
• "Write me a PIVOT—I'll check whether the syntax is right"
• Analysis still diverging, metrics not yet settled

You'll see: the Agent creating SQL tabs, running queries, and explaining results in the conversation. You can watch every step in real time (if you chose foreground-related behavior).

You won't have: the Approve & Execute button in the Plan toolbar—because you haven't yet entered the "approved formal analysis plan" flow.

Common pitfall: asking in Quick "make me a full funnel report for the weekly meeting" while expecting the Execute / Report flow. You should create a project and focus it, or choose Project Analysis when the Agent confirms the mode with you.

Project Analysis: when it enters automatically

Any one of the following conditions enters project mode:

1. A project is focused (the eye icon on the project row in the sidebar turns green)—the Agent no longer asks Quick or Project
2. When nothing is focused, you chose Project Analysis for a "data analysis request"
3. Complexity rises during a Quick session, and the Agent may suggest upgrading to a project

The full path: take the question → explore → draft Plan → you annotate and revise → you press Execute → the Agent runs SQL step by step → produces a Report.

When nothing is focused: the Agent asks first

If you haven't focused a project but make a data-analysis-type request (e.g., "analyze the retention trend," "find the reasons for order drop-off"), the Agent asks first:

• Quick Analysis — query directly in the IDE and give results in the conversation
• Project Analysis — create a project, write a Plan, you review, then Execute, and finally a Report

When it won't ask about the mode: pure SQL syntax, feature explanations, explaining an error message—the Agent answers directly.

Choosing Quick doesn't mean "low-grade"; choosing Project doesn't mean "it must be slow." What you're choosing is whether to lock the metrics and delivery into project files.

Execution modes

Quick Analysis (no project)

After choosing Quick Analysis, the Agent asks once more how to run it (pick one of three):

Plan Executing (inside a project)

After a Plan enters Executing, the Agent reads the Plan first, then asks once more how to run it (pick one of two; separate from Quick's background option):

This only affects how it runs after Execute; it does not replace the rule that "Execute must be pressed by you." If you press Continue after an interruption, it won't re-ask the execution mode.

Decision table (analyst edition)

Next steps

• Plan → annotate → Execute → Report
• USER_GUIDE §1.2–1.3, §12.5
• Analyst introduction