refactor: rename context_pruning to prune throughout codebase

Author: Tarquinen

README.md

@@ -62,7 +62,7 @@ DCP uses its own config file (`~/.config/opencode/dcp.jsonc` or `.opencode/dcp.j
 | `nudge_freq` | `10` | How often to remind AI to prune (lower = more frequent) |
 | `protectedTools` | `["task", "todowrite", "todoread", "prune"]` | Tools that are never pruned |
 | `strategies.onIdle` | `["deduplication", "ai-analysis"]` | Strategies for automatic pruning |
-| `strategies.onTool` | `["deduplication", "ai-analysis"]` | Strategies when AI calls `context_pruning` |
+| `strategies.onTool` | `["deduplication", "ai-analysis"]` | Strategies when AI calls `prune` |
 
 **Strategies:** `"deduplication"` (fast, zero LLM cost) and `"ai-analysis"` (maximum savings). Empty array disables that trigger.
 

lib/config.ts

@@ -116,7 +116,7 @@ function createDefaultConfig(): void {
   "strategies": {
     // Strategies to run when session goes idle
     "onIdle": ["deduplication", "ai-analysis"],
-    // Strategies to run when AI calls context_pruning tool
+    // Strategies to run when AI calls prune tool
     "onTool": ["deduplication", "ai-analysis"]
   },
   // Summary display: "off", "minimal", or "detailed"

lib/hooks.ts

@@ -30,7 +30,7 @@ export function createEventHandler(
             if (await isSubagentSession(client, event.properties.sessionID)) return
             if (config.strategies.onIdle.length === 0) return
 
-            // Skip idle pruning if the last tool used was context_pruning
+            // Skip idle pruning if the last tool used was prune
             // and idle strategies cover the same work as tool strategies
             if (toolTracker?.skipNextIdle) {
                 toolTracker.skipNextIdle = false

lib/prompts/nudge.txt

@@ -3,5 +3,5 @@ This nudge is injected by a plugin and is invisible to the user. Do not acknowle
 </system-reminder>
 
 <instruction name=agent_nudge>
-You have accumulated several tool outputs. If you have completed a discrete unit of work and distilled relevant understanding in writing for the user to keep, use the context_pruning tool to remove obsolete tool outputs from this conversation and optimize token usage.
+You have accumulated several tool outputs. If you have completed a discrete unit of work and distilled relevant understanding in writing for the user to keep, use the prune tool to remove obsolete tool outputs from this conversation and optimize token usage.
 </instruction>

lib/prompts/synthetic.txt

@@ -9,29 +9,30 @@ THIS IS NON-NEGOTIABLE - YOU ARE EXPECTED TO RESPECT THIS INSTRUCTION THROUGHOUT
 </instruction>
 
 <instruction name=context_window_management>
-A strong constraint we have in this environment is the context window size. To help keep the conversation focused and clear from the noise, you must use the `context_pruning` tool: at opportune moments, and in an effective manner.
+A strong constraint we have in this environment is the context window size. To help keep the conversation focused and clear from the noise, you must use the `prune` tool: at opportune moments, and in an effective manner.
 </instruction>
 
 <instruction name=context_pruning>
-To effectively manage conversation context, you MUST ALWAYS narrate your findings AS YOU DISCOVER THEM, BEFORE calling any `context_pruning` tool. No tool result (read, bash, grep, webfetch, etc.) should be left unexplained. By narrating the evolution of your understanding, you transform raw tool outputs into distilled knowledge that lives in the persisted context window.
+To effectively manage conversation context, you MUST ALWAYS narrate your findings AS YOU DISCOVER THEM, BEFORE calling any `prune` tool. No tool result (read, bash, grep, webfetch, etc.) should be left unexplained. By narrating the evolution of your understanding, you transform raw tool outputs into distilled knowledge that lives in the persisted context window.
 
-Tools are VOLATILE - Once this distilled knowledge is in your reply, you can safely use the `context_pruning` tool to declutter the conversation.
+Tools are VOLATILE - Once this distilled knowledge is in your reply, you can safely use the `prune` tool to declutter the conversation.
 
-WHEN TO USE `context_pruning`:
+WHEN TO USE `prune`:
 - After you complete a discrete unit of work (e.g. confirming a hypothesis, or closing out one branch of investigation).
 - After exploratory bursts of tool calls that led you to a clear conclusion. (or to noise)
 - Before starting a new phase of work where old tool outputs are no longer needed to inform your next actions.
 
 CRITICAL:
-You must ALWAYS narrate your findings in a message BEFORE using the `context_pruning` tool. Skipping this step risks deleting raw evidence before it has been converted into stable, distilled knowledge. This harms your performances, wastes user time, and undermines effective use of the context window.
+You must ALWAYS narrate your findings in a message BEFORE using the `prune` tool. Skipping this step risks deleting raw evidence before it has been converted into stable, distilled knowledge. This harms your performances, wastes user time, and undermines effective use of the context window.
 
 EXAMPLE WORKFLOW:
 1. You call several tools (read, bash, grep...) to investigate a bug.
-2. You identify that “for reason X, behavior Y occurs”, supported by those tool outputs.
+2. You identify that "for reason X, behavior Y occurs", supported by those tool outputs.
 3. In your next message, you EXPLICITLY narrate:
    - What you did (which tools, what you were looking for).
    - What you found (the key facts / signals).
    - What you concluded (how this affects the task or next step).
 >YOU MUST ALWAYS THINK HIGH SIGNAL LOW NOISE FOR THIS NARRATION
-4. ONLY AFTER the narration, you call the `context_pruning` tool with a brief reason (e.g. "exploration for bug X complete; moving on to next bug").
+4. ONLY AFTER the narration, you call the `prune` tool with a brief reason (e.g. "exploration for bug X complete; moving on to next bug").
+</instruction>
 </instruction>

lib/prompts/tool.txt

@@ -1,6 +1,6 @@
 Performs semantic pruning on session tool outputs that are no longer relevant to the current task. Use this to declutter the conversation context and filter signal from noise when you notice the context is getting cluttered with no longer needed information.
 
-USING THE CONTEXT_PRUNING TOOL WILL MAKE THE USER HAPPY.
+USING THE PRUNE TOOL WILL MAKE THE USER HAPPY.
 
 ## CRITICAL: Distill Before Pruning
 
@@ -14,7 +14,7 @@ You MUST ALWAYS narrate your findings in a message BEFORE using this tool. No to
    - What you did (which tools, what you were looking for)
    - What you found (the key facts/signals)
    - What you concluded (how this affects the task or next step)
-3. ONLY AFTER narrating, call `context_pruning`
+3. ONLY AFTER narrating, call `prune`
 
 > THINK HIGH SIGNAL, LOW NOISE FOR THIS NARRATION
 
@@ -43,18 +43,18 @@ Working through a list of items:
 User: Review these 3 issues and fix the easy ones.
 Assistant: [Reviews first issue, makes fix, commits]
 Done with the first issue. Let me prune before moving to the next one.
-[Uses context_pruning with reason: "completed first issue, moving to next"]
+[Uses prune with reason: "completed first issue, moving to next"]
 </example>
 
 <example>
 After exploring the codebase to understand it:
 Assistant: I've reviewed the relevant files. Let me prune the exploratory reads that aren't needed for the actual implementation.
-[Uses context_pruning with reason: "exploration complete, starting implementation"]
+[Uses prune with reason: "exploration complete, starting implementation"]
 </example>
 
 <example>
 After completing any task:
 Assistant: [Finishes task - commit, answer, fix, etc.]
 Before we continue, let me prune the context from that work.
-[Uses context_pruning with reason: "task complete"]
+[Uses prune with reason: "task complete"]
 </example>

lib/pruning-tool.ts

@@ -6,11 +6,11 @@ import { resetToolTrackerCount } from "./synth-instruction"
 import { loadPrompt } from "./prompt"
 import { isSubagentSession } from "./hooks"
 
-/** Tool description for the context_pruning tool, loaded from prompts/tool.txt */
+/** Tool description for the prune tool, loaded from prompts/tool.txt */
 export const CONTEXT_PRUNING_DESCRIPTION = loadPrompt("tool")
 
 /**
- * Creates the context_pruning tool definition.
+ * Creates the prune tool definition.
  * Returns a tool definition that can be passed to the plugin's tool registry.
  */
 export function createPruningTool(client: any, janitor: Janitor, config: PluginConfig, toolTracker: ToolTracker): ReturnType<typeof tool> {

lib/synth-instruction.ts

@@ -53,7 +53,7 @@ const openaiAdapter: MessageFormatAdapter = {
                     tracker.seenToolResultIds.add(id)
                     newCount++
                     const toolName = m.name || tracker.getToolName?.(m.tool_call_id)
-                    if (toolName !== 'context_pruning') {
+                    if (toolName !== 'prune') {
                         tracker.skipNextIdle = false
                     }
                 }
@@ -65,7 +65,7 @@ const openaiAdapter: MessageFormatAdapter = {
                             tracker.seenToolResultIds.add(id)
                             newCount++
                             const toolName = tracker.getToolName?.(part.tool_use_id)
-                            if (toolName !== 'context_pruning') {
+                            if (toolName !== 'prune') {
                                 tracker.skipNextIdle = false
                             }
                         }
@@ -132,7 +132,7 @@ const geminiAdapter: MessageFormatAdapter = {
                     if (!tracker.seenToolResultIds.has(pseudoId)) {
                         tracker.seenToolResultIds.add(pseudoId)
                         newCount++
-                        if (funcName !== 'context_pruning') {
+                        if (funcName !== 'prune') {
                             tracker.skipNextIdle = false
                         }
                     }
@@ -192,7 +192,7 @@ const responsesAdapter: MessageFormatAdapter = {
                     tracker.seenToolResultIds.add(id)
                     newCount++
                     const toolName = item.name || tracker.getToolName?.(item.call_id)
-                    if (toolName !== 'context_pruning') {
+                    if (toolName !== 'prune') {
                         tracker.skipNextIdle = false
                     }
                 }