@tarquinen/opencode-dcp 1.3.0-beta.1 → 1.3.1-beta1

package/dist/lib/prompts/system/both.d.ts

@@ -0,0 +1,2 @@
+export declare const SYSTEM_PROMPT_BOTH = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\n\nENVIRONMENT\nYou are operating in a context-constrained environment and thus must proactively manage your context window using the `discard` and `extract` tools. The environment calls the `context_info` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to prune.\n\nIMPORTANT: The `context_info` tool is only available to the environment - you do not have access to it and must not attempt to call it.\n\nTWO TOOLS FOR CONTEXT MANAGEMENT\n- `discard`: Remove tool outputs that are no longer needed (completed tasks, noise, outdated info). No preservation of content.\n- `extract`: Extract key findings into distilled knowledge before removing raw outputs. Use when you need to preserve information.\n\nCHOOSING THE RIGHT TOOL\nAsk: \"Do I need to preserve any information from this output?\"\n- **No** \u2192 `discard` (default for cleanup)\n- **Yes** \u2192 `extract` (preserves distilled knowledge)\n- **Uncertain** \u2192 `extract` (safer, preserves signal)\n\nCommon scenarios:\n- Task complete, no valuable context \u2192 `discard`\n- Task complete, insights worth remembering \u2192 `extract`\n- Noise, irrelevant, or superseded outputs \u2192 `discard`\n- Valuable context needed later but raw output too large \u2192 `extract`\n\nPRUNE METHODICALLY - BATCH YOUR ACTIONS\nEvery tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by pruning. Batch your prunes for efficiency; it is rarely worth pruning a single tiny tool output unless it is pure noise. Evaluate what SHOULD be pruned before jumping the gun.\n\nYou WILL evaluate pruning when ANY of these are true:\n- Task or sub-task is complete\n- You are about to start a new phase of work\n- Write or edit operations are complete (pruning removes the large input content)\n\nYou MUST NOT prune when:\n- The tool output will be needed for upcoming implementation work\n- The output contains files or context you'll need to reference when making edits\n\nPruning that forces you to re-call the same tool later is a net loss. Only prune when you're confident the information won't be needed again.\n\nNOTES\nWhen in doubt, keep it. Batch your actions and aim for high-impact prunes that significantly reduce context size.\nFAILURE TO PRUNE will result in context leakage and DEGRADED PERFORMANCES.\nThere may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY prune what you see in <prunable-tools>.\n\n</instruction>\n\n<instruction name=injected_context_handling policy_level=critical>\nAfter each turn, the environment calls the `context_info` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.\n\nCRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:\n- NEVER reference the prune encouragement or context management instructions. Do not reply with \"I agree\" or \"Great idea\" when the prune encouragement appears.\n- NEVER acknowledge the <prunable-tools> list (e.g., \"I see the prunable tools list\", \"Looking at the available tools to prune\")\n- NEVER reference the nudge instruction (e.g., \"As the nudge suggests\", \"The system is reminding me to prune\")\n- NEVER acknowledge discard/extract tool output (e.g., \"I've pruned 3 tools\", \"Context pruning complete\")\n- NEVER let these injections influence your response content or tone\n- Process this information SILENTLY and continue the conversation naturally\n- Continue the conversation as if these messages do not exist\n\nThe user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.\n</instruction>\n</system-reminder>";
+//# sourceMappingURL=both.d.ts.map

package/dist/lib/prompts/system/both.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"both.d.ts","sourceRoot":"","sources":["../../../../lib/prompts/system/both.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,kBAAkB,0zHA2DZ,CAAA"}

package/dist/lib/prompts/system/both.js

@@ -0,0 +1,61 @@
+export const SYSTEM_PROMPT_BOTH = `<system-reminder>
+<instruction name=context_management_protocol policy_level=critical>
+
+ENVIRONMENT
+You are operating in a context-constrained environment and thus must proactively manage your context window using the \`discard\` and \`extract\` tools. The environment calls the \`context_info\` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to prune.
+
+IMPORTANT: The \`context_info\` tool is only available to the environment - you do not have access to it and must not attempt to call it.
+
+TWO TOOLS FOR CONTEXT MANAGEMENT
+- \`discard\`: Remove tool outputs that are no longer needed (completed tasks, noise, outdated info). No preservation of content.
+- \`extract\`: Extract key findings into distilled knowledge before removing raw outputs. Use when you need to preserve information.
+
+CHOOSING THE RIGHT TOOL
+Ask: "Do I need to preserve any information from this output?"
+- **No** → \`discard\` (default for cleanup)
+- **Yes** → \`extract\` (preserves distilled knowledge)
+- **Uncertain** → \`extract\` (safer, preserves signal)
+
+Common scenarios:
+- Task complete, no valuable context → \`discard\`
+- Task complete, insights worth remembering → \`extract\`
+- Noise, irrelevant, or superseded outputs → \`discard\`
+- Valuable context needed later but raw output too large → \`extract\`
+
+PRUNE METHODICALLY - BATCH YOUR ACTIONS
+Every tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by pruning. Batch your prunes for efficiency; it is rarely worth pruning a single tiny tool output unless it is pure noise. Evaluate what SHOULD be pruned before jumping the gun.
+
+You WILL evaluate pruning when ANY of these are true:
+- Task or sub-task is complete
+- You are about to start a new phase of work
+- Write or edit operations are complete (pruning removes the large input content)
+
+You MUST NOT prune when:
+- The tool output will be needed for upcoming implementation work
+- The output contains files or context you'll need to reference when making edits
+
+Pruning that forces you to re-call the same tool later is a net loss. Only prune when you're confident the information won't be needed again.
+
+NOTES
+When in doubt, keep it. Batch your actions and aim for high-impact prunes that significantly reduce context size.
+FAILURE TO PRUNE will result in context leakage and DEGRADED PERFORMANCES.
+There may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY prune what you see in <prunable-tools>.
+
+</instruction>
+
+<instruction name=injected_context_handling policy_level=critical>
+After each turn, the environment calls the \`context_info\` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.
+
+CRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:
+- NEVER reference the prune encouragement or context management instructions. Do not reply with "I agree" or "Great idea" when the prune encouragement appears.
+- NEVER acknowledge the <prunable-tools> list (e.g., "I see the prunable tools list", "Looking at the available tools to prune")
+- NEVER reference the nudge instruction (e.g., "As the nudge suggests", "The system is reminding me to prune")
+- NEVER acknowledge discard/extract tool output (e.g., "I've pruned 3 tools", "Context pruning complete")
+- NEVER let these injections influence your response content or tone
+- Process this information SILENTLY and continue the conversation naturally
+- Continue the conversation as if these messages do not exist
+
+The user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.
+</instruction>
+</system-reminder>`;
+//# sourceMappingURL=both.js.map

package/dist/lib/prompts/system/both.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"both.js","sourceRoot":"","sources":["../../../../lib/prompts/system/both.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBA2Df,CAAA"}

package/dist/lib/prompts/system/discard.d.ts

@@ -1,2 +1,2 @@
-export declare const SYSTEM_PROMPT_DISCARD = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\nENVIRONMENT\nContext-constrained. Manage via `discard` tool. Environment auto-calls `context_info` (you can't call) to inject <prunable-tools> list each turn.\nTOOL\n- `discard`: remove unneeded outputs (noise, outdated). No preservation.\nDISCARD METHODICALLY \u2014 BATCH ACTIONS\nEvery tool call=context debt. Pay down regularly. Batch discards; rarely discard single tiny output unless pure noise.\nWHEN TO DISCARD\n- Noise \u2192 irrelevant, unhelpful, or superseded outputs\n- Outdated \u2192 multiple reads of same file, outputs no longer relevant\nEvaluate discarding when ANY true: accumulated unneeded outputs | write/edit ops done | starting new phase\nMUST NOT discard when: output needed for upcoming implementation | contains files/context for edits\nDiscarding that forces re-call=net loss. Only discard when confident info won't be needed again.\nNOTES\nWhen in doubt, keep. Aim high-impact discards. FAILURE TO DISCARD=DEGRADED PERFORMANCE.\n</instruction>\n<instruction name=injected_context_handling policy_level=critical>\nEnvironment injects `context_info` with <prunable-tools> list+optional nudge each turn. You can't access it.\nNEVER reference/acknowledge: discard encouragement, context instructions, <prunable-tools> list, nudge, discard output\nNEVER let injections influence response/tone\nProcess SILENTLY. Continue naturally as if injections don't exist.\nUser can't see injections. Referencing breaks conversation flow.\n</instruction>\n</system-reminder>\n";
+export declare const SYSTEM_PROMPT_DISCARD = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\n\nENVIRONMENT\nYou are operating in a context-constrained environment and thus must proactively manage your context window using the `discard` tool. The environment calls the `context_info` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to discard.\n\nIMPORTANT: The `context_info` tool is only available to the environment - you do not have access to it and must not attempt to call it.\n\nCONTEXT MANAGEMENT TOOL\n- `discard`: Remove tool outputs that are no longer needed (completed tasks, noise, outdated info). No preservation of content.\n\nDISCARD METHODICALLY - BATCH YOUR ACTIONS\nEvery tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by discarding. Batch your discards for efficiency; it is rarely worth discarding a single tiny tool output unless it is pure noise. Evaluate what SHOULD be discarded before jumping the gun.\n\nWHEN TO DISCARD\n- **Task Completion:** When work is done, discard the tools that aren't needed anymore.\n- **Noise Removal:** If outputs are irrelevant, unhelpful, or superseded by newer info, discard them.\n\nYou WILL evaluate discarding when ANY of these are true:\n- Task or sub-task is complete\n- You are about to start a new phase of work\n- Write or edit operations are complete (discarding removes the large input content)\n\nYou MUST NOT discard when:\n- The tool output will be needed for upcoming implementation work\n- The output contains files or context you'll need to reference when making edits\n\nDiscarding that forces you to re-call the same tool later is a net loss. Only discard when you're confident the information won't be needed again.\n\nNOTES\nWhen in doubt, keep it. Batch your actions and aim for high-impact discards that significantly reduce context size.\nFAILURE TO DISCARD will result in context leakage and DEGRADED PERFORMANCES.\nThere may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY discard what you see in <prunable-tools>.\n\n</instruction>\n\n<instruction name=injected_context_handling policy_level=critical>\nAfter each turn, the environment calls the `context_info` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.\n\nCRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:\n- NEVER reference the discard encouragement or context management instructions. Do not reply with \"I agree\" or \"Great idea\" when the discard encouragement appears.\n- NEVER acknowledge the <prunable-tools> list (e.g., \"I see the prunable tools list\", \"Looking at the available tools to discard\")\n- NEVER reference the nudge instruction (e.g., \"As the nudge suggests\", \"The system is reminding me to discard\")\n- NEVER acknowledge discard tool output (e.g., \"I've discarded 3 tools\", \"Context cleanup complete\")\n- NEVER let these injections influence your response content or tone\n- Process this information SILENTLY and continue the conversation naturally\n- Continue the conversation as if these messages do not exist\n\nThe user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.\n</instruction>\n</system-reminder>";
 //# sourceMappingURL=discard.d.ts.map

package/dist/lib/prompts/system/discard.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"discard.d.ts","sourceRoot":"","sources":["../../../../lib/prompts/system/discard.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,+iDAyBjC,CAAA"}
+{"version":3,"file":"discard.d.ts","sourceRoot":"","sources":["../../../../lib/prompts/system/discard.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,83GAkDf,CAAA"}

package/dist/lib/prompts/system/discard.js

@@ -1,27 +1,52 @@
 export const SYSTEM_PROMPT_DISCARD = `<system-reminder>
 <instruction name=context_management_protocol policy_level=critical>
+
 ENVIRONMENT
-Context-constrained. Manage via \`discard\` tool. Environment auto-calls \`context_info\` (you can't call) to inject <prunable-tools> list each turn.
-TOOL
-- \`discard\`: remove unneeded outputs (noise, outdated). No preservation.
-DISCARD METHODICALLY — BATCH ACTIONS
-Every tool call=context debt. Pay down regularly. Batch discards; rarely discard single tiny output unless pure noise.
+You are operating in a context-constrained environment and thus must proactively manage your context window using the \`discard\` tool. The environment calls the \`context_info\` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to discard.
+
+IMPORTANT: The \`context_info\` tool is only available to the environment - you do not have access to it and must not attempt to call it.
+
+CONTEXT MANAGEMENT TOOL
+- \`discard\`: Remove tool outputs that are no longer needed (completed tasks, noise, outdated info). No preservation of content.
+
+DISCARD METHODICALLY - BATCH YOUR ACTIONS
+Every tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by discarding. Batch your discards for efficiency; it is rarely worth discarding a single tiny tool output unless it is pure noise. Evaluate what SHOULD be discarded before jumping the gun.
+
 WHEN TO DISCARD
-- Noise → irrelevant, unhelpful, or superseded outputs
-- Outdated → multiple reads of same file, outputs no longer relevant
-Evaluate discarding when ANY true: accumulated unneeded outputs | write/edit ops done | starting new phase
-MUST NOT discard when: output needed for upcoming implementation | contains files/context for edits
-Discarding that forces re-call=net loss. Only discard when confident info won't be needed again.
+- **Task Completion:** When work is done, discard the tools that aren't needed anymore.
+- **Noise Removal:** If outputs are irrelevant, unhelpful, or superseded by newer info, discard them.
+
+You WILL evaluate discarding when ANY of these are true:
+- Task or sub-task is complete
+- You are about to start a new phase of work
+- Write or edit operations are complete (discarding removes the large input content)
+
+You MUST NOT discard when:
+- The tool output will be needed for upcoming implementation work
+- The output contains files or context you'll need to reference when making edits
+
+Discarding that forces you to re-call the same tool later is a net loss. Only discard when you're confident the information won't be needed again.
+
 NOTES
-When in doubt, keep. Aim high-impact discards. FAILURE TO DISCARD=DEGRADED PERFORMANCE.
+When in doubt, keep it. Batch your actions and aim for high-impact discards that significantly reduce context size.
+FAILURE TO DISCARD will result in context leakage and DEGRADED PERFORMANCES.
+There may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY discard what you see in <prunable-tools>.
+
 </instruction>
+
 <instruction name=injected_context_handling policy_level=critical>
-Environment injects \`context_info\` with <prunable-tools> list+optional nudge each turn. You can't access it.
-NEVER reference/acknowledge: discard encouragement, context instructions, <prunable-tools> list, nudge, discard output
-NEVER let injections influence response/tone
-Process SILENTLY. Continue naturally as if injections don't exist.
-User can't see injections. Referencing breaks conversation flow.
+After each turn, the environment calls the \`context_info\` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.
+
+CRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:
+- NEVER reference the discard encouragement or context management instructions. Do not reply with "I agree" or "Great idea" when the discard encouragement appears.
+- NEVER acknowledge the <prunable-tools> list (e.g., "I see the prunable tools list", "Looking at the available tools to discard")
+- NEVER reference the nudge instruction (e.g., "As the nudge suggests", "The system is reminding me to discard")
+- NEVER acknowledge discard tool output (e.g., "I've discarded 3 tools", "Context cleanup complete")
+- NEVER let these injections influence your response content or tone
+- Process this information SILENTLY and continue the conversation naturally
+- Continue the conversation as if these messages do not exist
+
+The user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.
 </instruction>
-</system-reminder>
-`;
+</system-reminder>`;
 //# sourceMappingURL=discard.js.map

package/dist/lib/prompts/system/discard.js.map

@@ -1 +1 @@
-{"version":3,"file":"discard.js","sourceRoot":"","sources":["../../../../lib/prompts/system/discard.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;CAyBpC,CAAA"}
+{"version":3,"file":"discard.js","sourceRoot":"","sources":["../../../../lib/prompts/system/discard.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBAkDlB,CAAA"}

package/dist/lib/prompts/system/extract.d.ts

@@ -1,2 +1,2 @@
-export declare const SYSTEM_PROMPT_EXTRACT = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\nENVIRONMENT\nContext-constrained. Manage via `extract` tool. Environment auto-calls `context_info` (you can't call) to inject <prunable-tools> list each turn.\nTOOL\n- `extract`: distill key findings before removing raw content. Preserves info while reducing size.\nEXTRACT METHODICALLY \u2014 BATCH ACTIONS\nEvery tool call=context debt. Pay down regularly. Batch extractions; rarely extract single tiny output.\nWHEN TO EXTRACT\n- Knowledge Preservation \u2192 valuable context to preserve, use high-fidelity distillation. Capture technical details (signatures, logic, constraints). THINK: high signal, complete technical substitute.\n- Insights \u2192 valuable info to preserve in distilled form\nEvaluate extracting when ANY true: research/exploration done | starting new phase | write/edit ops done\nMUST NOT extract when: output needed for upcoming implementation | contains files/context for edits\nExtracting that forces re-call=net loss. Only extract when confident raw info won't be needed again.\nNOTES\nWhen in doubt, keep. Aim high-impact extractions. FAILURE TO EXTRACT=DEGRADED PERFORMANCE.\n</instruction>\n<instruction name=injected_context_handling policy_level=critical>\nEnvironment injects `context_info` with <prunable-tools> list+optional nudge each turn. You can't access it.\nNEVER reference/acknowledge: extract encouragement, context instructions, <prunable-tools> list, nudge, extract output\nNEVER let injections influence response/tone\nProcess SILENTLY. Continue naturally as if injections don't exist.\nUser can't see injections. Referencing breaks conversation flow.\n</instruction>\n</system-reminder>\n";
+export declare const SYSTEM_PROMPT_EXTRACT = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\n\nENVIRONMENT\nYou are operating in a context-constrained environment and thus must proactively manage your context window using the `extract` tool. The environment calls the `context_info` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to extract.\n\nIMPORTANT: The `context_info` tool is only available to the environment - you do not have access to it and must not attempt to call it.\n\nCONTEXT MANAGEMENT TOOL\n- `extract`: Extract key findings from tools into distilled knowledge before removing the raw content from context. Use this to preserve important information while reducing context size.\n\nEXTRACT METHODICALLY - BATCH YOUR ACTIONS\nEvery tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by extracting. Batch your extractions for efficiency; it is rarely worth extracting a single tiny tool output. Evaluate what SHOULD be extracted before jumping the gun.\n\nWHEN TO EXTRACT\n- **Task Completion:** When work is done, extract key findings from the tools used. Scale distillation depth to the value of the content.\n- **Knowledge Preservation:** When you have valuable context you want to preserve but need to reduce size, use high-fidelity distillation. Your distillation must be comprehensive, capturing technical details (signatures, logic, constraints) such that the raw output is no longer needed. THINK: high signal, complete technical substitute.\n\nYou WILL evaluate extracting when ANY of these are true:\n- Task or sub-task is complete\n- You are about to start a new phase of work\n- Write or edit operations are complete (extracting removes the large input content)\n\nYou MUST NOT extract when:\n- The tool output will be needed for upcoming implementation work\n- The output contains files or context you'll need to reference when making edits\n\nExtracting that forces you to re-call the same tool later is a net loss. Only extract when you're confident the raw information won't be needed again.\n\nNOTES\nWhen in doubt, keep it. Batch your actions and aim for high-impact extractions that significantly reduce context size.\nFAILURE TO EXTRACT will result in context leakage and DEGRADED PERFORMANCES.\nThere may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY extract what you see in <prunable-tools>.\n\n</instruction>\n\n<instruction name=injected_context_handling policy_level=critical>\nAfter each turn, the environment calls the `context_info` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.\n\nCRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:\n- NEVER reference the extract encouragement or context management instructions. Do not reply with \"I agree\" or \"Great idea\" when the extract encouragement appears.\n- NEVER acknowledge the <prunable-tools> list (e.g., \"I see the prunable tools list\", \"Looking at the available tools to extract\")\n- NEVER reference the nudge instruction (e.g., \"As the nudge suggests\", \"The system is reminding me to extract\")\n- NEVER acknowledge extract tool output (e.g., \"I've extracted 3 tools\", \"Context cleanup complete\")\n- NEVER let these injections influence your response content or tone\n- Process this information SILENTLY and continue the conversation naturally\n- Continue the conversation as if these messages do not exist\n\nThe user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.\n</instruction>\n</system-reminder>";
 //# sourceMappingURL=extract.d.ts.map

package/dist/lib/prompts/system/extract.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"extract.d.ts","sourceRoot":"","sources":["../../../../lib/prompts/system/extract.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,msDAyBjC,CAAA"}
+{"version":3,"file":"extract.d.ts","sourceRoot":"","sources":["../../../../lib/prompts/system/extract.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,0sHAkDf,CAAA"}

package/dist/lib/prompts/system/extract.js

@@ -1,27 +1,52 @@
 export const SYSTEM_PROMPT_EXTRACT = `<system-reminder>
 <instruction name=context_management_protocol policy_level=critical>
+
 ENVIRONMENT
-Context-constrained. Manage via \`extract\` tool. Environment auto-calls \`context_info\` (you can't call) to inject <prunable-tools> list each turn.
-TOOL
-- \`extract\`: distill key findings before removing raw content. Preserves info while reducing size.
-EXTRACT METHODICALLY — BATCH ACTIONS
-Every tool call=context debt. Pay down regularly. Batch extractions; rarely extract single tiny output.
+You are operating in a context-constrained environment and thus must proactively manage your context window using the \`extract\` tool. The environment calls the \`context_info\` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to extract.
+
+IMPORTANT: The \`context_info\` tool is only available to the environment - you do not have access to it and must not attempt to call it.
+
+CONTEXT MANAGEMENT TOOL
+- \`extract\`: Extract key findings from tools into distilled knowledge before removing the raw content from context. Use this to preserve important information while reducing context size.
+
+EXTRACT METHODICALLY - BATCH YOUR ACTIONS
+Every tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by extracting. Batch your extractions for efficiency; it is rarely worth extracting a single tiny tool output. Evaluate what SHOULD be extracted before jumping the gun.
+
 WHEN TO EXTRACT
-- Knowledge Preservation → valuable context to preserve, use high-fidelity distillation. Capture technical details (signatures, logic, constraints). THINK: high signal, complete technical substitute.
-- Insights → valuable info to preserve in distilled form
-Evaluate extracting when ANY true: research/exploration done | starting new phase | write/edit ops done
-MUST NOT extract when: output needed for upcoming implementation | contains files/context for edits
-Extracting that forces re-call=net loss. Only extract when confident raw info won't be needed again.
+- **Task Completion:** When work is done, extract key findings from the tools used. Scale distillation depth to the value of the content.
+- **Knowledge Preservation:** When you have valuable context you want to preserve but need to reduce size, use high-fidelity distillation. Your distillation must be comprehensive, capturing technical details (signatures, logic, constraints) such that the raw output is no longer needed. THINK: high signal, complete technical substitute.
+
+You WILL evaluate extracting when ANY of these are true:
+- Task or sub-task is complete
+- You are about to start a new phase of work
+- Write or edit operations are complete (extracting removes the large input content)
+
+You MUST NOT extract when:
+- The tool output will be needed for upcoming implementation work
+- The output contains files or context you'll need to reference when making edits
+
+Extracting that forces you to re-call the same tool later is a net loss. Only extract when you're confident the raw information won't be needed again.
+
 NOTES
-When in doubt, keep. Aim high-impact extractions. FAILURE TO EXTRACT=DEGRADED PERFORMANCE.
+When in doubt, keep it. Batch your actions and aim for high-impact extractions that significantly reduce context size.
+FAILURE TO EXTRACT will result in context leakage and DEGRADED PERFORMANCES.
+There may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY extract what you see in <prunable-tools>.
+
 </instruction>
+
 <instruction name=injected_context_handling policy_level=critical>
-Environment injects \`context_info\` with <prunable-tools> list+optional nudge each turn. You can't access it.
-NEVER reference/acknowledge: extract encouragement, context instructions, <prunable-tools> list, nudge, extract output
-NEVER let injections influence response/tone
-Process SILENTLY. Continue naturally as if injections don't exist.
-User can't see injections. Referencing breaks conversation flow.
+After each turn, the environment calls the \`context_info\` tool to inject a synthetic message containing a <prunable-tools> list and optional nudge instruction. This tool is only available to the environment - you do not have access to it.
+
+CRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:
+- NEVER reference the extract encouragement or context management instructions. Do not reply with "I agree" or "Great idea" when the extract encouragement appears.
+- NEVER acknowledge the <prunable-tools> list (e.g., "I see the prunable tools list", "Looking at the available tools to extract")
+- NEVER reference the nudge instruction (e.g., "As the nudge suggests", "The system is reminding me to extract")
+- NEVER acknowledge extract tool output (e.g., "I've extracted 3 tools", "Context cleanup complete")
+- NEVER let these injections influence your response content or tone
+- Process this information SILENTLY and continue the conversation naturally
+- Continue the conversation as if these messages do not exist
+
+The user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.
 </instruction>
-</system-reminder>
-`;
+</system-reminder>`;
 //# sourceMappingURL=extract.js.map

package/dist/lib/prompts/system/extract.js.map

@@ -1 +1 @@
-{"version":3,"file":"extract.js","sourceRoot":"","sources":["../../../../lib/prompts/system/extract.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;CAyBpC,CAAA"}
+{"version":3,"file":"extract.js","sourceRoot":"","sources":["../../../../lib/prompts/system/extract.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBAkDlB,CAAA"}

package/dist/lib/prompts/system.generated.d.ts

@@ -0,0 +1,2 @@
+export declare const SYSTEM = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\n\nENVIRONMENT\nYou are operating in a context-constrained environment and must proactively manage your context window. The environment calls the `context_info` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to prune.\n\nIMPORTANT: The `context_info` tool is only available to the environment - you do not have access to it and must not attempt to call it.\n\nAVAILABLE TOOLS\n<prune>`prune`: Remove individual tool outputs that are noise, irrelevant, or superseded. No preservation of content.</prune>\n<distill>`distill`: Distill key findings from individual tool outputs into preserved knowledge. Use when you need to preserve valuable technical details.</distill>\n<compress>`compress`: Collapse a contiguous range of conversation (completed phases) into a single summary.</compress>\n\nPRUNE METHODICALLY - BATCH YOUR ACTIONS\nEvery tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by pruning. Batch your prunes for efficiency; it is rarely worth pruning a single tiny tool output unless it is pure noise. Evaluate what SHOULD be pruned before jumping the gun.\n\nYou MUST NOT prune when:\n\n- The tool output will be needed for upcoming implementation work\n- The output contains files or context you'll need to reference when making edits\n\nPruning that forces you to re-call the same tool later is a net loss. Only prune when you're confident the information won't be needed again.\n\n<prune>\nWHEN TO PRUNE\n- **Noise Removal:** Outputs that are irrelevant, unhelpful, or superseded by newer info.\n- **Wrong Files:** You read or accessed something that turned out to be irrelevant to the current work.\n- **Outdated Info:** Outputs that have been superseded by newer information.\n\nYou WILL evaluate pruning when ANY of these are true:\n\nYou accessed something that turned out to be irrelevant\nInformation has been superseded by newer outputs\nYou are about to start a new phase of work\n</prune>\n\n<distill>\nWHEN TO DISTILL\n**Large Outputs:** The raw output is too large but contains valuable technical details worth keeping.\n**Knowledge Preservation:** Valuable context you want to preserve but need to reduce size. Your distillation must be comprehensive, capturing technical details (signatures, logic, constraints) such that the raw output is no longer needed. THINK: high signal, complete technical substitute.\n\nYou WILL evaluate distilling when ANY of these are true:\n\n- You have large tool outputs with valuable technical details\n- You need to preserve specific information but reduce context size\n- You are about to start a new phase of work and want to retain key insights\n  </distill>\n  <compress>\n  WHEN TO COMPRESS\n- **Phase Completion:** When a phase is complete, condense the entire sequence (research, tool calls, implementation) into a summary.\n- **Exploration Done:** When you've explored multiple files or ran multiple commands and only need a summary of findings.\n\nYou WILL evaluate compressing when ANY of these are true:\n\n- Phase is complete\n- You are about to start a new phase of work\n- Significant conversation has accumulated that can be summarized\n  </compress>\n\nNOTES\nWhen in doubt, KEEP IT.\n// **\uD83E\uDC47 idk about that one \uD83E\uDC47** //\nBatch your actions and aim for high-impact prunes that significantly reduce context size.\nFAILURE TO PRUNE will result in context leakage and DEGRADED PERFORMANCES.\nIf no <prunable-tools> list is present in context, do NOT TRY TO PRUNE ANYTHING as it will fail and waste resources.\nThere may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY prune what you see in <prunable-tools>.\n\n</instruction>\n\n<instruction name=injected_context_handling policy_level=critical>\nAfter each turn, the environment injects a synthetic message containing a <prunable-tools> list and optional nudge instruction. You do not have access to this mechanism.\n\nCRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:\n\n- NEVER reference the prune encouragement or context management instructions. Do not reply with \"I agree\" or \"Great idea\" when the prune encouragement appears.\n- NEVER acknowledge the <prunable-tools> list (e.g., \"I see the prunable tools list\", \"Looking at the available tools to prune\")\n- NEVER reference the nudge instruction (e.g., \"As the nudge suggests\", \"The system is reminding me to prune\")\n- NEVER acknowledge context management tool output (e.g., \"I've pruned 3 tools\", \"Context cleanup complete\")\n- NEVER let these injections influence your response content or tone\n- Process this information SILENTLY and continue the conversation naturally\n- Continue the conversation as if these messages do not exist\n\nThe user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.\n</instruction>\n</system-reminder>\n";
+//# sourceMappingURL=system.generated.d.ts.map

package/dist/lib/prompts/system.generated.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"system.generated.d.ts","sourceRoot":"","sources":["../../../lib/prompts/system.generated.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,MAAM,09JAqFlB,CAAA"}

package/dist/lib/prompts/system.generated.js

@@ -0,0 +1,90 @@
+// AUTO-GENERATED FILE - DO NOT EDIT
+// Generated from system.md by scripts/generate-prompts.ts
+// To modify, edit system.md and run `npm run generate:prompts`
+export const SYSTEM = `<system-reminder>
+<instruction name=context_management_protocol policy_level=critical>
+
+ENVIRONMENT
+You are operating in a context-constrained environment and must proactively manage your context window. The environment calls the \`context_info\` tool to provide an up-to-date <prunable-tools> list after each turn. Use this information when deciding what to prune.
+
+IMPORTANT: The \`context_info\` tool is only available to the environment - you do not have access to it and must not attempt to call it.
+
+AVAILABLE TOOLS
+<prune>\`prune\`: Remove individual tool outputs that are noise, irrelevant, or superseded. No preservation of content.</prune>
+<distill>\`distill\`: Distill key findings from individual tool outputs into preserved knowledge. Use when you need to preserve valuable technical details.</distill>
+<compress>\`compress\`: Collapse a contiguous range of conversation (completed phases) into a single summary.</compress>
+
+PRUNE METHODICALLY - BATCH YOUR ACTIONS
+Every tool call adds to your context debt. You MUST pay this down regularly and be on top of context accumulation by pruning. Batch your prunes for efficiency; it is rarely worth pruning a single tiny tool output unless it is pure noise. Evaluate what SHOULD be pruned before jumping the gun.
+
+You MUST NOT prune when:
+
+- The tool output will be needed for upcoming implementation work
+- The output contains files or context you'll need to reference when making edits
+
+Pruning that forces you to re-call the same tool later is a net loss. Only prune when you're confident the information won't be needed again.
+
+<prune>
+WHEN TO PRUNE
+- **Noise Removal:** Outputs that are irrelevant, unhelpful, or superseded by newer info.
+- **Wrong Files:** You read or accessed something that turned out to be irrelevant to the current work.
+- **Outdated Info:** Outputs that have been superseded by newer information.
+
+You WILL evaluate pruning when ANY of these are true:
+
+You accessed something that turned out to be irrelevant
+Information has been superseded by newer outputs
+You are about to start a new phase of work
+</prune>
+
+<distill>
+WHEN TO DISTILL
+**Large Outputs:** The raw output is too large but contains valuable technical details worth keeping.
+**Knowledge Preservation:** Valuable context you want to preserve but need to reduce size. Your distillation must be comprehensive, capturing technical details (signatures, logic, constraints) such that the raw output is no longer needed. THINK: high signal, complete technical substitute.
+
+You WILL evaluate distilling when ANY of these are true:
+
+- You have large tool outputs with valuable technical details
+- You need to preserve specific information but reduce context size
+- You are about to start a new phase of work and want to retain key insights
+  </distill>
+  <compress>
+  WHEN TO COMPRESS
+- **Phase Completion:** When a phase is complete, condense the entire sequence (research, tool calls, implementation) into a summary.
+- **Exploration Done:** When you've explored multiple files or ran multiple commands and only need a summary of findings.
+
+You WILL evaluate compressing when ANY of these are true:
+
+- Phase is complete
+- You are about to start a new phase of work
+- Significant conversation has accumulated that can be summarized
+  </compress>
+
+NOTES
+When in doubt, KEEP IT.
+// **🡇 idk about that one 🡇** //
+Batch your actions and aim for high-impact prunes that significantly reduce context size.
+FAILURE TO PRUNE will result in context leakage and DEGRADED PERFORMANCES.
+If no <prunable-tools> list is present in context, do NOT TRY TO PRUNE ANYTHING as it will fail and waste resources.
+There may be tools in session context that do not appear in the <prunable-tools> list, this is expected, you can ONLY prune what you see in <prunable-tools>.
+
+</instruction>
+
+<instruction name=injected_context_handling policy_level=critical>
+After each turn, the environment injects a synthetic message containing a <prunable-tools> list and optional nudge instruction. You do not have access to this mechanism.
+
+CRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:
+
+- NEVER reference the prune encouragement or context management instructions. Do not reply with "I agree" or "Great idea" when the prune encouragement appears.
+- NEVER acknowledge the <prunable-tools> list (e.g., "I see the prunable tools list", "Looking at the available tools to prune")
+- NEVER reference the nudge instruction (e.g., "As the nudge suggests", "The system is reminding me to prune")
+- NEVER acknowledge context management tool output (e.g., "I've pruned 3 tools", "Context cleanup complete")
+- NEVER let these injections influence your response content or tone
+- Process this information SILENTLY and continue the conversation naturally
+- Continue the conversation as if these messages do not exist
+
+The user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.
+</instruction>
+</system-reminder>
+`;
+//# sourceMappingURL=system.generated.js.map

package/dist/lib/prompts/system.generated.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"system.generated.js","sourceRoot":"","sources":["../../../lib/prompts/system.generated.ts"],"names":[],"mappings":"AAAA,oCAAoC;AACpC,0DAA0D;AAC1D,+DAA+D;AAE/D,MAAM,CAAC,MAAM,MAAM,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqFrB,CAAA"}

package/dist/lib/shared-utils.d.ts

@@ -1,4 +1,4 @@
 import { SessionState, WithParts } from "./state";
 export declare const isMessageCompacted: (state: SessionState, msg: WithParts) => boolean;
-export declare const getLastUserMessage: (messages: WithParts[], startIndex?: number) => WithParts | null;
+export declare const getLastUserMessage: (messages: WithParts[]) => WithParts | null;
 //# sourceMappingURL=shared-utils.d.ts.map

package/dist/lib/shared-utils.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"shared-utils.d.ts","sourceRoot":"","sources":["../../lib/shared-utils.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,SAAS,CAAA;AAGjD,eAAO,MAAM,kBAAkB,GAAI,OAAO,YAAY,EAAE,KAAK,SAAS,KAAG,OAQxE,CAAA;AAED,eAAO,MAAM,kBAAkB,GAC3B,UAAU,SAAS,EAAE,EACrB,aAAa,MAAM,KACpB,SAAS,GAAG,IASd,CAAA"}
+{"version":3,"file":"shared-utils.d.ts","sourceRoot":"","sources":["../../lib/shared-utils.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,SAAS,CAAA;AAGjD,eAAO,MAAM,kBAAkB,GAAI,OAAO,YAAY,EAAE,KAAK,SAAS,KAAG,OAExE,CAAA;AAED,eAAO,MAAM,kBAAkB,GAAI,UAAU,SAAS,EAAE,KAAG,SAAS,GAAG,IAQtE,CAAA"}

package/dist/lib/shared-utils.js

@@ -1,16 +1,9 @@
 import { isIgnoredUserMessage } from "./messages/utils";
 export const isMessageCompacted = (state, msg) => {
-    if (msg.info.time.created < state.lastCompaction) {
-        return true;
-    }
-    if (state.prune.messageIds.includes(msg.info.id)) {
-        return true;
-    }
-    return false;
+    return msg.info.time.created < state.lastCompaction;
 };
-export const getLastUserMessage = (messages, startIndex) => {
-    const start = startIndex ?? messages.length - 1;
-    for (let i = start; i >= 0; i--) {
+export const getLastUserMessage = (messages) => {
+    for (let i = messages.length - 1; i >= 0; i--) {
         const msg = messages[i];
         if (msg.info.role === "user" && !isIgnoredUserMessage(msg)) {
             return msg;

package/dist/lib/shared-utils.js.map

@@ -1 +1 @@
-{"version":3,"file":"shared-utils.js","sourceRoot":"","sources":["../../lib/shared-utils.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAA;AAEvD,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,KAAmB,EAAE,GAAc,EAAW,EAAE;IAC/E,IAAI,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,OAAO,GAAG,KAAK,CAAC,cAAc,EAAE,CAAC;QAC/C,OAAO,IAAI,CAAA;IACf,CAAC;IACD,IAAI,KAAK,CAAC,KAAK,CAAC,UAAU,CAAC,QAAQ,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,EAAE,CAAC;QAC/C,OAAO,IAAI,CAAA;IACf,CAAC;IACD,OAAO,KAAK,CAAA;AAChB,CAAC,CAAA;AAED,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAC9B,QAAqB,EACrB,UAAmB,EACH,EAAE;IAClB,MAAM,KAAK,GAAG,UAAU,IAAI,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAA;IAC/C,KAAK,IAAI,CAAC,GAAG,KAAK,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC;QAC9B,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,CAAA;QACvB,IAAI,GAAG,CAAC,IAAI,CAAC,IAAI,KAAK,MAAM,IAAI,CAAC,oBAAoB,CAAC,GAAG,CAAC,EAAE,CAAC;YACzD,OAAO,GAAG,CAAA;QACd,CAAC;IACL,CAAC;IACD,OAAO,IAAI,CAAA;AACf,CAAC,CAAA"}
+{"version":3,"file":"shared-utils.js","sourceRoot":"","sources":["../../lib/shared-utils.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAA;AAEvD,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,KAAmB,EAAE,GAAc,EAAW,EAAE;IAC/E,OAAO,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,OAAO,GAAG,KAAK,CAAC,cAAc,CAAA;AACvD,CAAC,CAAA;AAED,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,QAAqB,EAAoB,EAAE;IAC1E,KAAK,IAAI,CAAC,GAAG,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC;QAC5C,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,CAAA;QACvB,IAAI,GAAG,CAAC,IAAI,CAAC,IAAI,KAAK,MAAM,IAAI,CAAC,oBAAoB,CAAC,GAAG,CAAC,EAAE,CAAC;YACzD,OAAO,GAAG,CAAA;QACd,CAAC;IACL,CAAC;IACD,OAAO,IAAI,CAAA;AACf,CAAC,CAAA"}

package/dist/lib/state/persistence.d.ts

@@ -3,12 +3,11 @@
  * Persists pruned tool IDs across sessions so they survive OpenCode restarts.
  * Storage location: ~/.local/share/opencode/storage/plugin/dcp/{sessionId}.json
  */
-import type { SessionState, SessionStats, Prune, SquashSummary } from "./types";
+import type { SessionState, SessionStats, Prune } from "./types";
 import type { Logger } from "../logger";
 export interface PersistedSessionState {
     sessionName?: string;
     prune: Prune;
-    squashSummaries: SquashSummary[];
     stats: SessionStats;
     lastUpdated: string;
 }

package/dist/lib/state/persistence.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"persistence.d.ts","sourceRoot":"","sources":["../../../lib/state/persistence.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAMH,OAAO,KAAK,EAAE,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,aAAa,EAAE,MAAM,SAAS,CAAA;AAC/E,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,WAAW,CAAA;AAEvC,MAAM,WAAW,qBAAqB;IAClC,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,KAAK,EAAE,KAAK,CAAA;IACZ,eAAe,EAAE,aAAa,EAAE,CAAA;IAChC,KAAK,EAAE,YAAY,CAAA;IACnB,WAAW,EAAE,MAAM,CAAA;CACtB;AAcD,wBAAsB,gBAAgB,CAClC,YAAY,EAAE,YAAY,EAC1B,MAAM,EAAE,MAAM,EACd,WAAW,CAAC,EAAE,MAAM,GACrB,OAAO,CAAC,IAAI,CAAC,CA8Bf;AAED,wBAAsB,gBAAgB,CAClC,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,MAAM,GACf,OAAO,CAAC,qBAAqB,GAAG,IAAI,CAAC,CA8BvC;AAED,MAAM,WAAW,eAAe;IAC5B,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;IAClB,YAAY,EAAE,MAAM,CAAA;CACvB;AAED,wBAAsB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,eAAe,CAAC,CAqClF"}
+{"version":3,"file":"persistence.d.ts","sourceRoot":"","sources":["../../../lib/state/persistence.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAMH,OAAO,KAAK,EAAE,YAAY,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,SAAS,CAAA;AAChE,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,WAAW,CAAA;AAEvC,MAAM,WAAW,qBAAqB;IAClC,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,KAAK,EAAE,KAAK,CAAA;IACZ,KAAK,EAAE,YAAY,CAAA;IACnB,WAAW,EAAE,MAAM,CAAA;CACtB;AAcD,wBAAsB,gBAAgB,CAClC,YAAY,EAAE,YAAY,EAC1B,MAAM,EAAE,MAAM,EACd,WAAW,CAAC,EAAE,MAAM,GACrB,OAAO,CAAC,IAAI,CAAC,CA6Bf;AAED,wBAAsB,gBAAgB,CAClC,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,MAAM,GACf,OAAO,CAAC,qBAAqB,GAAG,IAAI,CAAC,CA8BvC;AAED,MAAM,WAAW,eAAe;IAC5B,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;IAClB,YAAY,EAAE,MAAM,CAAA;CACvB;AAED,wBAAsB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,eAAe,CAAC,CAqClF"}

package/dist/lib/state/persistence.js

@@ -25,7 +25,6 @@ export async function saveSessionState(sessionState, logger, sessionName) {
         const state = {
             sessionName: sessionName,
             prune: sessionState.prune,
-            squashSummaries: sessionState.squashSummaries,
             stats: sessionState.stats,
             lastUpdated: new Date().toISOString(),
         };

package/dist/lib/state/persistence.js.map

@@ -1 +1 @@
-{"version":3,"file":"persistence.js","sourceRoot":"","sources":["../../../lib/state/persistence.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,KAAK,EAAE,MAAM,aAAa,CAAA;AACjC,OAAO,EAAE,UAAU,EAAE,MAAM,IAAI,CAAA;AAC/B,OAAO,EAAE,OAAO,EAAE,MAAM,IAAI,CAAA;AAC5B,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAA;AAY3B,MAAM,WAAW,GAAG,IAAI,CAAC,OAAO,EAAE,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,CAAC,CAAA;AAE9F,KAAK,UAAU,gBAAgB;IAC3B,IAAI,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;QAC3B,MAAM,EAAE,CAAC,KAAK,CAAC,WAAW,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAA;IACpD,CAAC;AACL,CAAC;AAED,SAAS,kBAAkB,CAAC,SAAiB;IACzC,OAAO,IAAI,CAAC,WAAW,EAAE,GAAG,SAAS,OAAO,CAAC,CAAA;AACjD,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAClC,YAA0B,EAC1B,MAAc,EACd,WAAoB;IAEpB,IAAI,CAAC;QACD,IAAI,CAAC,YAAY,CAAC,SAAS,EAAE,CAAC;YAC1B,OAAM;QACV,CAAC;QAED,MAAM,gBAAgB,EAAE,CAAA;QAExB,MAAM,KAAK,GAA0B;YACjC,WAAW,EAAE,WAAW;YACxB,KAAK,EAAE,YAAY,CAAC,KAAK;YACzB,eAAe,EAAE,YAAY,CAAC,eAAe;YAC7C,KAAK,EAAE,YAAY,CAAC,KAAK;YACzB,WAAW,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACxC,CAAA;QAED,MAAM,QAAQ,GAAG,kBAAkB,CAAC,YAAY,CAAC,SAAS,CAAC,CAAA;QAC3D,MAAM,OAAO,GAAG,IAAI,CAAC,SAAS,CAAC,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,CAAA;QAC9C,MAAM,EAAE,CAAC,SAAS,CAAC,QAAQ,EAAE,OAAO,EAAE,OAAO,CAAC,CAAA;QAE9C,MAAM,CAAC,IAAI,CAAC,6BAA6B,EAAE;YACvC,SAAS,EAAE,YAAY,CAAC,SAAS;YACjC,gBAAgB,EAAE,KAAK,CAAC,KAAK,CAAC,gBAAgB;SACjD,CAAC,CAAA;IACN,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,KAAK,CAAC,8BAA8B,EAAE;YACzC,SAAS,EAAE,YAAY,CAAC,SAAS;YACjC,KAAK,EAAE,KAAK,EAAE,OAAO;SACxB,CAAC,CAAA;IACN,CAAC;AACL,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAClC,SAAiB,EACjB,MAAc;IAEd,IAAI,CAAC;QACD,MAAM,QAAQ,GAAG,kBAAkB,CAAC,SAAS,CAAC,CAAA;QAE9C,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;YACxB,OAAO,IAAI,CAAA;QACf,CAAC;QAED,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAA;QACpD,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAA0B,CAAA;QAE1D,IAAI,CAAC,KAAK,IAAI,CAAC,KAAK,CAAC,KAAK,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC;YAChF,MAAM,CAAC,IAAI,CAAC,sCAAsC,EAAE;gBAChD,SAAS,EAAE,SAAS;aACvB,CAAC,CAAA;YACF,OAAO,IAAI,CAAA;QACf,CAAC;QAED,MAAM,CAAC,IAAI,CAAC,gCAAgC,EAAE;YAC1C,SAAS,EAAE,SAAS;SACvB,CAAC,CAAA;QAEF,OAAO,KAAK,CAAA;IAChB,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,IAAI,CAAC,8BAA8B,EAAE;YACxC,SAAS,EAAE,SAAS;YACpB,KAAK,EAAE,KAAK,EAAE,OAAO;SACxB,CAAC,CAAA;QACF,OAAO,IAAI,CAAA;IACf,CAAC;AACL,CAAC;AAQD,MAAM,CAAC,KAAK,UAAU,mBAAmB,CAAC,MAAc;IACpD,MAAM,MAAM,GAAoB;QAC5B,WAAW,EAAE,CAAC;QACd,UAAU,EAAE,CAAC;QACb,YAAY,EAAE,CAAC;KAClB,CAAA;IAED,IAAI,CAAC;QACD,IAAI,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;YAC3B,OAAO,MAAM,CAAA;QACjB,CAAC;QAED,MAAM,KAAK,GAAG,MAAM,EAAE,CAAC,OAAO,CAAC,WAAW,CAAC,CAAA;QAC3C,MAAM,SAAS,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC,CAAA;QAE1D,KAAK,MAAM,IAAI,IAAI,SAAS,EAAE,CAAC;YAC3B,IAAI,CAAC;gBACD,MAAM,QAAQ,GAAG,IAAI,CAAC,WAAW,EAAE,IAAI,CAAC,CAAA;gBACxC,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAA;gBACpD,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAA0B,CAAA;gBAE1D,IAAI,KAAK,EAAE,KAAK,EAAE,gBAAgB,IAAI,KAAK,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC;oBAC1D,MAAM,CAAC,WAAW,IAAI,KAAK,CAAC,KAAK,CAAC,gBAAgB,CAAA;oBAClD,MAAM,CAAC,UAAU,IAAI,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAA;oBAC/C,MAAM,CAAC,YAAY,EAAE,CAAA;gBACzB,CAAC;YACL,CAAC;YAAC,MAAM,CAAC;gBACL,qBAAqB;YACzB,CAAC;QACL,CAAC;QAED,MAAM,CAAC,KAAK,CAAC,uBAAuB,EAAE,MAAM,CAAC,CAAA;IACjD,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,IAAI,CAAC,+BAA+B,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC,CAAA;IAC3E,CAAC;IAED,OAAO,MAAM,CAAA;AACjB,CAAC"}
+{"version":3,"file":"persistence.js","sourceRoot":"","sources":["../../../lib/state/persistence.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,KAAK,EAAE,MAAM,aAAa,CAAA;AACjC,OAAO,EAAE,UAAU,EAAE,MAAM,IAAI,CAAA;AAC/B,OAAO,EAAE,OAAO,EAAE,MAAM,IAAI,CAAA;AAC5B,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAA;AAW3B,MAAM,WAAW,GAAG,IAAI,CAAC,OAAO,EAAE,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,CAAC,CAAA;AAE9F,KAAK,UAAU,gBAAgB;IAC3B,IAAI,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;QAC3B,MAAM,EAAE,CAAC,KAAK,CAAC,WAAW,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAA;IACpD,CAAC;AACL,CAAC;AAED,SAAS,kBAAkB,CAAC,SAAiB;IACzC,OAAO,IAAI,CAAC,WAAW,EAAE,GAAG,SAAS,OAAO,CAAC,CAAA;AACjD,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAClC,YAA0B,EAC1B,MAAc,EACd,WAAoB;IAEpB,IAAI,CAAC;QACD,IAAI,CAAC,YAAY,CAAC,SAAS,EAAE,CAAC;YAC1B,OAAM;QACV,CAAC;QAED,MAAM,gBAAgB,EAAE,CAAA;QAExB,MAAM,KAAK,GAA0B;YACjC,WAAW,EAAE,WAAW;YACxB,KAAK,EAAE,YAAY,CAAC,KAAK;YACzB,KAAK,EAAE,YAAY,CAAC,KAAK;YACzB,WAAW,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACxC,CAAA;QAED,MAAM,QAAQ,GAAG,kBAAkB,CAAC,YAAY,CAAC,SAAS,CAAC,CAAA;QAC3D,MAAM,OAAO,GAAG,IAAI,CAAC,SAAS,CAAC,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,CAAA;QAC9C,MAAM,EAAE,CAAC,SAAS,CAAC,QAAQ,EAAE,OAAO,EAAE,OAAO,CAAC,CAAA;QAE9C,MAAM,CAAC,IAAI,CAAC,6BAA6B,EAAE;YACvC,SAAS,EAAE,YAAY,CAAC,SAAS;YACjC,gBAAgB,EAAE,KAAK,CAAC,KAAK,CAAC,gBAAgB;SACjD,CAAC,CAAA;IACN,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,KAAK,CAAC,8BAA8B,EAAE;YACzC,SAAS,EAAE,YAAY,CAAC,SAAS;YACjC,KAAK,EAAE,KAAK,EAAE,OAAO;SACxB,CAAC,CAAA;IACN,CAAC;AACL,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAClC,SAAiB,EACjB,MAAc;IAEd,IAAI,CAAC;QACD,MAAM,QAAQ,GAAG,kBAAkB,CAAC,SAAS,CAAC,CAAA;QAE9C,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;YACxB,OAAO,IAAI,CAAA;QACf,CAAC;QAED,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAA;QACpD,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAA0B,CAAA;QAE1D,IAAI,CAAC,KAAK,IAAI,CAAC,KAAK,CAAC,KAAK,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC;YAChF,MAAM,CAAC,IAAI,CAAC,sCAAsC,EAAE;gBAChD,SAAS,EAAE,SAAS;aACvB,CAAC,CAAA;YACF,OAAO,IAAI,CAAA;QACf,CAAC;QAED,MAAM,CAAC,IAAI,CAAC,gCAAgC,EAAE;YAC1C,SAAS,EAAE,SAAS;SACvB,CAAC,CAAA;QAEF,OAAO,KAAK,CAAA;IAChB,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,IAAI,CAAC,8BAA8B,EAAE;YACxC,SAAS,EAAE,SAAS;YACpB,KAAK,EAAE,KAAK,EAAE,OAAO;SACxB,CAAC,CAAA;QACF,OAAO,IAAI,CAAA;IACf,CAAC;AACL,CAAC;AAQD,MAAM,CAAC,KAAK,UAAU,mBAAmB,CAAC,MAAc;IACpD,MAAM,MAAM,GAAoB;QAC5B,WAAW,EAAE,CAAC;QACd,UAAU,EAAE,CAAC;QACb,YAAY,EAAE,CAAC;KAClB,CAAA;IAED,IAAI,CAAC;QACD,IAAI,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;YAC3B,OAAO,MAAM,CAAA;QACjB,CAAC;QAED,MAAM,KAAK,GAAG,MAAM,EAAE,CAAC,OAAO,CAAC,WAAW,CAAC,CAAA;QAC3C,MAAM,SAAS,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC,CAAA;QAE1D,KAAK,MAAM,IAAI,IAAI,SAAS,EAAE,CAAC;YAC3B,IAAI,CAAC;gBACD,MAAM,QAAQ,GAAG,IAAI,CAAC,WAAW,EAAE,IAAI,CAAC,CAAA;gBACxC,MAAM,OAAO,GAAG,MAAM,EAAE,CAAC,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAA;gBACpD,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAA0B,CAAA;gBAE1D,IAAI,KAAK,EAAE,KAAK,EAAE,gBAAgB,IAAI,KAAK,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC;oBAC1D,MAAM,CAAC,WAAW,IAAI,KAAK,CAAC,KAAK,CAAC,gBAAgB,CAAA;oBAClD,MAAM,CAAC,UAAU,IAAI,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAA;oBAC/C,MAAM,CAAC,YAAY,EAAE,CAAA;gBACzB,CAAC;YACL,CAAC;YAAC,MAAM,CAAC;gBACL,qBAAqB;YACzB,CAAC;QACL,CAAC;QAED,MAAM,CAAC,KAAK,CAAC,uBAAuB,EAAE,MAAM,CAAC,CAAA;IACjD,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QAClB,MAAM,CAAC,IAAI,CAAC,+BAA+B,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC,CAAA;IAC3E,CAAC;IAED,OAAO,MAAM,CAAA;AACjB,CAAC"}

package/dist/lib/state/state.d.ts

@@ -4,4 +4,5 @@ export declare const checkSession: (client: any, state: SessionState, logger: Lo
 export declare function createSessionState(): SessionState;
 export declare function resetSessionState(state: SessionState): void;
 export declare function ensureSessionInitialized(client: any, state: SessionState, sessionId: string, logger: Logger, messages: WithParts[]): Promise<void>;
+export declare function countTurns(state: SessionState, messages: WithParts[]): number;
 //# sourceMappingURL=state.d.ts.map

package/dist/lib/state/state.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"state.d.ts","sourceRoot":"","sources":["../../../lib/state/state.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAsB,SAAS,EAAE,MAAM,SAAS,CAAA;AAC1E,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,WAAW,CAAA;AAUvC,eAAO,MAAM,YAAY,GACrB,QAAQ,GAAG,EACX,OAAO,YAAY,EACnB,QAAQ,MAAM,EACd,UAAU,SAAS,EAAE,KACtB,OAAO,CAAC,IAAI,CA2Bd,CAAA;AAED,wBAAgB,kBAAkB,IAAI,YAAY,CAoBjD;AAED,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,YAAY,GAAG,IAAI,CAkB3D;AAED,wBAAsB,wBAAwB,CAC1C,MAAM,EAAE,GAAG,EACX,KAAK,EAAE,YAAY,EACnB,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,SAAS,EAAE,GACtB,OAAO,CAAC,IAAI,CAAC,CAgCf"}
+{"version":3,"file":"state.d.ts","sourceRoot":"","sources":["../../../lib/state/state.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAsB,SAAS,EAAE,MAAM,SAAS,CAAA;AAC1E,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,WAAW,CAAA;AAKvC,eAAO,MAAM,YAAY,GACrB,QAAQ,GAAG,EACX,OAAO,YAAY,EACnB,QAAQ,MAAM,EACd,UAAU,SAAS,EAAE,KACtB,OAAO,CAAC,IAAI,CA4Bd,CAAA;AAED,wBAAgB,kBAAkB,IAAI,YAAY,CAkBjD;AAED,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,YAAY,GAAG,IAAI,CAgB3D;AAED,wBAAsB,wBAAwB,CAC1C,MAAM,EAAE,GAAG,EACX,KAAK,EAAE,YAAY,EACnB,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,SAAS,EAAE,GACtB,OAAO,CAAC,IAAI,CAAC,CA8Bf;AAYD,wBAAgB,UAAU,CAAC,KAAK,EAAE,YAAY,EAAE,QAAQ,EAAE,SAAS,EAAE,GAAG,MAAM,CAc7E"}

package/dist/lib/state/state.js

@@ -1,6 +1,6 @@
 import { loadSessionState } from "./persistence";
-import { isSubAgentSession, findLastCompactionTimestamp, countTurns, resetOnCompaction, } from "./utils";
-import { getLastUserMessage } from "../shared-utils";
+import { isSubAgentSession } from "./utils";
+import { getLastUserMessage, isMessageCompacted } from "../shared-utils";
 export const checkSession = async (client, state, logger, messages) => {
     const lastUserMessage = getLastUserMessage(messages);
     if (!lastUserMessage) {
@@ -19,8 +19,9 @@ export const checkSession = async (client, state, logger, messages) => {
     const lastCompactionTimestamp = findLastCompactionTimestamp(messages);
     if (lastCompactionTimestamp > state.lastCompaction) {
         state.lastCompaction = lastCompactionTimestamp;
-        resetOnCompaction(state);
-        logger.info("Detected compaction - reset stale state", {
+        state.toolParameters.clear();
+        state.prune.toolIds = [];
+        logger.info("Detected compaction from messages - cleared tool cache", {
             timestamp: lastCompactionTimestamp,
         });
     }
@@ -32,9 +33,7 @@ export function createSessionState() {
         isSubAgent: false,
         prune: {
             toolIds: [],
-            messageIds: [],
         },
-        squashSummaries: [],
         stats: {
             pruneTokenCounter: 0,
             totalPruneTokens: 0,
@@ -52,9 +51,7 @@ export function resetSessionState(state) {
     state.isSubAgent = false;
     state.prune = {
         toolIds: [],
-        messageIds: [],
     };
-    state.squashSummaries = [];
     state.stats = {
         pruneTokenCounter: 0,
         totalPruneTokens: 0,
@@ -85,12 +82,34 @@ export async function ensureSessionInitialized(client, state, sessionId, logger,
     }
     state.prune = {
         toolIds: persisted.prune.toolIds || [],
-        messageIds: persisted.prune.messageIds || [],
     };
-    state.squashSummaries = persisted.squashSummaries || [];
     state.stats = {
         pruneTokenCounter: persisted.stats?.pruneTokenCounter || 0,
         totalPruneTokens: persisted.stats?.totalPruneTokens || 0,
     };
 }
+function findLastCompactionTimestamp(messages) {
+    for (let i = messages.length - 1; i >= 0; i--) {
+        const msg = messages[i];
+        if (msg.info.role === "assistant" && msg.info.summary === true) {
+            return msg.info.time.created;
+        }
+    }
+    return 0;
+}
+export function countTurns(state, messages) {
+    let turnCount = 0;
+    for (const msg of messages) {
+        if (isMessageCompacted(state, msg)) {
+            continue;
+        }
+        const parts = Array.isArray(msg.parts) ? msg.parts : [];
+        for (const part of parts) {
+            if (part.type === "step-start") {
+                turnCount++;
+            }
+        }
+    }
+    return turnCount;
+}
 //# sourceMappingURL=state.js.map