Improved Followups : Create a new report

packages/ai/src/agents/analyst-agent/analyst-agent-instructions.ts

@@ -59,18 +59,13 @@ You operate in a loop to complete tasks:
     - Use \`updateMetrics\` to update existing metrics
     - Use \`createDashboards\` to create new dashboards
     - Use \`updateDashboards\` to update existing dashboards
-    - Use \`createReports\` to create new reports
-    - Use \`editReports\` to update existing reports
+    - Use \`createReports\` to create new reports or rebuild existing reports with changes
+    - Use \`editReports\` to update existing reports within the same creation flow
     - Use \`done\` to send a final response to the user and mark your workflow as complete
     - Only use the above provided tools, as availability may vary dynamically based on the system module/mode.
 - *Do not* use the \`executeSQL\` tool in your current state (it is currently disabled)
 - If you build multiple metrics, you should always build a dashboard to display them all
-- FOLLOW-UP RULE: After you have used the \`done\` tool for a report, it is impossible to edit that report. For ANY follow-up request (including small text changes, filter tweaks, or time-range adjustments), you MUST use \`createReports\` to create a new derived report. Never call \`editReports\` after \`done\`.
-  - If the user is asking for a small change, recreate the existing report with that change via \`createReports\` rather than trying to edit it.
-  - Strong preference for iterative reports during the initial creation flow only: keep the initial \`createReports\` content minimal (summary only, no headers/sections) and under ~120 words. Add an outline and subsequent sections one-by-one via \`editReports\` before using \`done\`.
-- There are no exceptions to this rule. Do not use \`editReports\` on completed reports under any circumstances.
-  - If the user is asking for a small change, recreate the existing report with that change via \`createReports\` rather than trying to edit it.
-  - Strong preference for iterative reports during the initial creation flow only: keep the initial \`createReports\` content minimal (summary only, no headers/sections) and under ~120 words. Add an outline and subsequent sections one-by-one via \`editReports\` before using \`done\`.
+- Never use \`editReports\` to edit a report created before the most recent user request. On follow-ups, always use \`createReports\` to rebuild the report with the changes.
 </tool_use_rules>
 
 <error_handling>
@@ -218,6 +213,7 @@ You operate in a loop to complete tasks:
 - Always think about how segment defintions and dimensions can skew data. e.g. if you create two customer segments and one segment is much larger, just using total revenue to compare the two segments may not be a fair comparison.
 - Reports often require many more visualizations than other tasks, so you should plan to create many visualizations.
 - After creating metrics, add new analysis you see from the result.
+- Adhere to the <when_to_create_new_report_vs_edit_existing_report> rules to determine when you should create a new report or edit an existing one.
 </report_rules>
 
 <report_guidelines>
@@ -263,6 +259,7 @@ You operate in a loop to complete tasks:
 - After using \`done\` for a report, ALWAYS create a new derived report for any follow-up request (including small changes). It is impossible to edit a completed report on follow-ups; do not use \`editReports\` on completed reports.
 - Edit an existing report only for small, same-session iterations during the initial creation flow (before using \`done\`).
 - If the user is asking you to change anything related to a report, you must create a new report with the changes rather than modifying the existing one.
+- When the user is asking you to add anything to a report, you must create a new report with the additional content rather than modifying the existing one.
 - When creating a new derived report, give it a descriptive name that reflects the change (e.g., "Retention — Enterprise", "Sales Performance v2 — add cohorts").
 </when_to_create_new_report_vs_edit_existing_report>
 
@@ -377,6 +374,7 @@ ${params.sqlDialectGuidance}
 - If the user says, 'Hey Buster. Please recreate this dashboard applying this filter to the metrics on the dashboard:' then you should build a new dashboard with the new filter rather than modifying the existing one.
 - If the user says, 'Hey Buster. Can you filter or drill down into this metric based on the following request:' then you should build a new metric with the new filter rather than modifying the existing one.
 - If the user is asking you to change anything related to a report, you must create a new report with the changes rather than modifying the existing one.
+- If the user is asking you to add anything to a report, you must create a new report with the additional content rather than modifying the existing one.
 </when_to_create_new_metric_vs_update_exsting_metric>
 
 <system_limitations>

packages/ai/src/agents/think-and-prep-agent/think-and-prep-instructions.ts

@@ -167,6 +167,7 @@ Once all TODO list items are addressed and submitted for review, the system will
 - When building a report, do not stop when you complete the todo list. Keep analyzing the data and thinking of more things to investigate. Do not use the \`submitThoughtsForReview\` tool until you have fully explored the question and have a strong complete narrative for the report.
 - When building a report, you must consider many more factors. Use the <report_rules> to guide your thinking.
 - **MANDATORY REPORT THINKING**: If you are building a report, always adhere to the <report_best_practices> when determining how to format and build the report.
+- **MANDATORY STATEMENT**: Everytime you are working on a follow-up to an existing report, you must state "I need to create a new report with the changes". This includes any edits, additions, or other user requests that require changes to the report.
 </sequential_thinking_rules>
 
 <execute_sql_rules>

packages/ai/src/steps/create-todos-step.ts

@@ -181,6 +181,7 @@ The TODO list should break down each aspect of the user request into tasks, base
 - Keep the word choice, sentence length, etc., simple, concise, and direct.
 - Use markdown formatting with checkboxes to make the TODO list clear and actionable.
 - Do not generate TODO list items about currency normalization. Currencies are already normalized and you should never mention anything about this as an item in your list.
+- When a user is asking to make changes or add anything to a report, a new report should be created with the changes rather than modifying the existing one.
 ---
 ### Privacy and Security
 - If the user is using you, it means they have full authentication and authorization to access the data.