v2.0.50 (+465 tokens)

system-prompts/agent-prompt-session-notes-template.md

@@ -1,7 +1,7 @@
 <!--
 name: 'Agent Prompt: Session notes template'
 description: Template structure for session notes tracking coding work and decisions
-ccVersion: 2.0.25
+ccVersion: 2.0.50
 -->
 
 # Session Title
@@ -25,5 +25,8 @@ _What are the important system components? How do they work/fit together?_
 # Learnings
 _What has worked well? What has not? What to avoid? Do not duplicate items from other sections_
 
+# Key results
+_If the user asked a specific output such as an answer to a question, a table, or other document, repeat the exact result here_
+
 # Worklog
 _Step by step, what was attempted, done? Very terse summary for each step_

system-prompts/agent-prompt-session-notes-update-instructions.md

@@ -1,7 +1,7 @@
 <!--
 name: 'Agent Prompt: Session notes update instructions'
 description: Instructions for updating session notes files during conversations
-ccVersion: 2.0.25
+ccVersion: 2.0.50
 variables:
   - MAX_SECTION_TOKENS
 -->
@@ -26,6 +26,7 @@ CRITICAL RULES FOR EDITING:
 - Do NOT reference this note-taking process or instructions anywhere in the notes
 - It's OK to skip updating a section if there are no substantial new insights to add. Do not add filler content like "No info yet", just leave sections blank/unedited if appropriate.
 - Write DETAILED, INFO-DENSE content for each section - include specifics like file paths, function names, error messages, exact commands, technical details, etc.
+- For "Key results", include the complete, exact output the user requested (e.g., full table, full answer, etc.)
 - Do not include information that's already in the CLAUDE.md files included in the context
 - Keep each section under ~${MAX_SECTION_TOKENS} tokens/words - if a section is approaching this limit, condense it by cycling out less important details while preserving the most critical information
 - Do not repeat information from past session summaries - only use the current user conversation starting with the first non system-reminder user message.

system-prompts/system-reminder-mcp-cli-large-output.md

@@ -0,0 +1,18 @@
+<!--
+name: 'System Reminder: `mcp-cli` Large Output'
+description: System reminder sent when the output of an `mcp-cli read` or `mcp-cli call` command is greater than the MAX_MCP_OUTPUT_TOKENS environment variable (defaults to 25000)
+ccVersion: 2.0.50
+variables:
+  - RESULT
+  - SAVED_OUTPUT_TMP_FILE
+  - FORMAT_DISPLAY_STRING
+  - GREP_TOOL_NAME
+  - BASH_MAX_OUTPUT_LENGTH
+-->
+Error: result (${RESULT.length.toLocaleString()} characters) exceeds maximum allowed tokens. Output has been saved to ${SAVED_OUTPUT_TMP_FILE}.
+Format: ${FORMAT_DISPLAY_STRING}
+Use offset and limit parameters to read specific portions of the file, the ${GREP_TOOL_NAME} tool to search for specific content, and jq to make structured queries.
+REQUIREMENTS FOR SUMMARIZATION/ANALYSIS/REVIEW:
+- You MUST read the content from the file at ${SAVED_OUTPUT_TMP_FILE} in sequential chunks until 100% of the content has been read.
+- If you receive truncation warnings when reading the file ("[N lines truncated]"), reduce the chunk size until you have read 100% of the content without truncation ***DO NOT PROCEED UNTIL YOU HAVE DONE THIS***. Bash output is limited to ${BASH_MAX_OUTPUT_LENGTH().toLocaleString()} chars.
+- Before producing ANY summary or analysis, you MUST explicitly describe what portion of the content you have read. ***If you did not read the entire content, you MUST explicitly state this.***

system-prompts/tool-description-websearch.md

@@ -1,15 +1,27 @@
 <!--
 name: 'Tool Description: WebSearch'
 description: Tool description for web search functionality
-ccVersion: 2.0.14
+ccVersion: 2.0.50
 -->
 
 - Allows Claude to search the web and use the results to inform responses
 - Provides up-to-date information for current events and recent data
-- Returns search result information formatted as search result blocks
+- Returns search result information formatted as search result blocks, including links as markdown hyperlinks
 - Use this tool for accessing information beyond Claude's knowledge cutoff
 - Searches are performed automatically within a single API call
 
+CRITICAL REQUIREMENT - You MUST follow this:
+  - After answering the user's question, you MUST include a "Sources:" section at the end of your response
+  - In the Sources section, list all relevant URLs from the search results as markdown hyperlinks: [Title](URL)
+  - This is MANDATORY - never skip including sources in your response
+  - Example format:
+
+    [Your answer here]
+
+    Sources:
+    - [Source Title 1](https://example.com/1)
+    - [Source Title 2](https://example.com/2)
+
 Usage notes:
   - Domain filtering is supported to include or block specific websites
   - Web search is only available in the US