fix: added summary to tangent and showed correct display label for introspect (#2725)

Author: abhraina-aws

crates/chat-cli/src/cli/agent/mod.rs

@@ -814,6 +814,7 @@ impl Agents {
             "execute_cmd" => "trust read-only commands".dark_grey(),
             "use_aws" => "trust read-only commands".dark_grey(),
             "report_issue" => "trusted".dark_green().bold(),
+            "introspect" => "trusted".dark_green().bold(),
             "thinking" => "trusted (prerelease)".dark_green().bold(),
             "todo_list" => "trusted".dark_green().bold(),
             _ if self.trust_all_tools => "trusted".dark_grey().bold(),

crates/chat-cli/src/cli/chat/conversation.rs

@@ -147,6 +147,8 @@ struct ConversationCheckpoint {
     main_next_message: Option<UserMessage>,
     /// Main conversation transcript
     main_transcript: VecDeque<String>,
+    /// Main conversation summary
+    main_latest_summary: Option<(String, RequestMetadata)>,
     /// Timestamp when tangent mode was entered (milliseconds since epoch)
     #[serde(default = "time::OffsetDateTime::now_utc")]
     tangent_start_time: time::OffsetDateTime,
@@ -240,6 +242,7 @@ impl ConversationState {
             main_history: self.history.clone(),
             main_next_message: self.next_message.clone(),
             main_transcript: self.transcript.clone(),
+            main_latest_summary: self.latest_summary.clone(),
             tangent_start_time: time::OffsetDateTime::now_utc(),
         }
     }
@@ -249,6 +252,7 @@ impl ConversationState {
         self.history = checkpoint.main_history;
         self.next_message = checkpoint.main_next_message;
         self.transcript = checkpoint.main_transcript;
+        self.latest_summary = checkpoint.main_latest_summary;
         self.valid_history_range = (0, self.history.len());
     }
 

crates/chat-cli/src/cli/chat/tools/introspect.rs

@@ -81,7 +81,10 @@ impl Introspect {
             "\nNOTE: Settings are managed via `q settings` command from terminal, not slash commands in chat.\n",
         );
 
-        documentation.push_str("\n\n--- GitHub References ---\n");
+        documentation.push_str("\n\n--- CRITICAL INSTRUCTION ---\n");
+        documentation.push_str("YOU MUST ONLY provide information that is explicitly documented in the sections above. If specific details about any tool, feature, or command are not documented, you MUST clearly state that the information is not available in the documentation. DO NOT generate plausible-sounding information or make assumptions about undocumented features.\n\n");
+
+        documentation.push_str("--- GitHub References ---\n");
         documentation.push_str("INSTRUCTION: When your response uses information from any of these documentation files, include the relevant GitHub link(s) at the end:\n");
         documentation.push_str("• README.md: https://github.com/aws/amazon-q-developer-cli/blob/main/README.md\n");
         documentation.push_str(

crates/chat-cli/src/cli/chat/tools/tool_index.json

@@ -10,7 +10,7 @@
   },
   "introspect": {
     "name": "introspect",
-    "description": "ALWAYS use this tool when users ask ANY question about Q CLI itself, its capabilities, features, commands, or functionality. This includes questions like 'Can you...', 'Do you have...', 'How do I...', 'What can you do...', or any question about Q's abilities. When mentioning commands in your response, always prefix them with '/' (e.g., '/save', '/load', '/context').",
+    "description": "ALWAYS use this tool when users ask ANY question about Q CLI itself, its capabilities, features, commands, or functionality. This includes questions like 'Can you...', 'Do you have...', 'How do I...', 'What can you do...', or any question about Q's abilities. When mentioning commands in your response, always prefix them with '/' (e.g., '/save', '/load', '/context'). CRITICAL: Only provide information explicitly documented in Q CLI documentation. If details about any tool, feature, or command are not documented, clearly state the information is not available rather than generating assumptions.",
     "input_schema": {
       "type": "object",
       "properties": {