diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml
index 184909a36a..85402f86d9 100644
--- a/.github/workflows/daily-observability-report.lock.yml
+++ b/.github/workflows/daily-observability-report.lock.yml
@@ -975,18 +975,12 @@ jobs:
           
           Create a summary table of all runs analyzed with their observability status.
           
-          ## Phase 6: Close Previous Reports
-          
-          Before creating the new discussion, find and close previous observability reports:
-          
-          1. Search for discussions with title prefix "[observability]"
-          2. Close each found discussion with reason "OUTDATED"
-          3. Add a closing comment: "This report has been superseded by a newer observability report."
-          
-          ## Phase 7: Create Discussion Report
+          ## Phase 6: Create Discussion Report
           
           Create a new discussion with the comprehensive observability report.
           
+          **Note**: Previous observability reports with the same `[observability]` prefix will be automatically closed when the new discussion is created. This is handled by the `close-older-discussions: true` setting in the safe-outputs configuration - you don't need to manually close them.
+          
           ### Discussion Format
           
           **Title**: `[observability] Observability Coverage Report - YYYY-MM-DD`
@@ -1123,12 +1117,9 @@ jobs:
           - ✅ Check all MCP-enabled runs for gateway.jsonl presence
           - ✅ Calculate coverage percentages and identify gaps
           - ✅ Flag any runs missing critical logs as CRITICAL
-          - ✅ Close previous observability discussions
-          - ✅ Create a new discussion with comprehensive report
+          - ✅ Create a new discussion with comprehensive report (previous discussions automatically closed)
           - ✅ Include actionable recommendations
           
-          PROMPT_EOF
-          cat << 'PROMPT_EOF' >> "$GH_AW_PROMPT"
           Begin your analysis now. Download the logs, analyze observability coverage, and create the discussion report.
           
           PROMPT_EOF
diff --git a/.github/workflows/daily-observability-report.md b/.github/workflows/daily-observability-report.md
index 01a29f4739..34ca3faa95 100644
--- a/.github/workflows/daily-observability-report.md
+++ b/.github/workflows/daily-observability-report.md
@@ -273,18 +273,12 @@ runs_with_missing_logs = (firewall_enabled_workflows - firewall_logs_present) +
 
 Create a summary table of all runs analyzed with their observability status.
 
-## Phase 6: Close Previous Reports
-
-Before creating the new discussion, find and close previous observability reports:
-
-1. Search for discussions with title prefix "[observability]"
-2. Close each found discussion with reason "OUTDATED"
-3. Add a closing comment: "This report has been superseded by a newer observability report."
-
-## Phase 7: Create Discussion Report
+## Phase 6: Create Discussion Report
 
 Create a new discussion with the comprehensive observability report.
 
+**Note**: Previous observability reports with the same `[observability]` prefix will be automatically closed when the new discussion is created. This is handled by the `close-older-discussions: true` setting in the safe-outputs configuration - you don't need to manually close them.
+
 ### Discussion Format
 
 **Title**: `[observability] Observability Coverage Report - YYYY-MM-DD`
@@ -421,8 +415,7 @@ A successful run will:
 - ✅ Check all MCP-enabled runs for gateway.jsonl presence
 - ✅ Calculate coverage percentages and identify gaps
 - ✅ Flag any runs missing critical logs as CRITICAL
-- ✅ Close previous observability discussions
-- ✅ Create a new discussion with comprehensive report
+- ✅ Create a new discussion with comprehensive report (previous discussions automatically closed)
 - ✅ Include actionable recommendations
 
 Begin your analysis now. Download the logs, analyze observability coverage, and create the discussion report.