From b18c536b11fedea86a33bfef0d040a8132558015 Mon Sep 17 00:00:00 2001 From: wassname <1103714+wassname@users.noreply.github.com> Date: Thu, 16 Apr 2026 15:35:19 +0800 Subject: [PATCH] fix: add 'do not narrate' instruction to all nudge prompts Agents were generating visible messages like 'Almost there, will check again on next trigger' when nudged but deciding not to compress. This is because the nudges tell the agent to evaluate and act, but when it decides not to act, it narrates that decision instead of continuing silently. --- prompts.ts | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/prompts.ts b/prompts.ts index e106e8b..5bc985a 100644 --- a/prompts.ts +++ b/prompts.ts @@ -135,6 +135,8 @@ When multiple independent ranges are ready and their boundaries do not overlap, export const CONTEXT_LIMIT_NUDGE_STRONG = ` CRITICAL WARNING: MAX CONTEXT LIMIT REACHED +Do not narrate your compression decision. Either compress or continue silently — never output a message explaining why you are not compressing. + You are at or beyond the configured max context threshold. This is an emergency context-recovery moment. You MUST use the \`compress\` tool now. Do not continue normal exploration until compression is handled. @@ -163,6 +165,8 @@ If the compressed range includes user messages, preserve user intent exactly. Pr export const CONTEXT_LIMIT_NUDGE_SOFT = ` NOTICE: Context usage is high. +Do not narrate your compression decision. Either compress or continue silently — never output a message explaining why you are not compressing. + Look for a closed, self-contained range that no longer needs to stay raw and compress it now. RANGE SELECTION @@ -180,6 +184,8 @@ If nothing is cleanly closed yet, continue — but compress at the earliest oppo export const TURN_NUDGE = ` Evaluate the conversation for compressible ranges. +Do not narrate your compression decision. Either compress or continue silently — never output a message explaining why you are not compressing. + If any range is cleanly closed and unlikely to be needed again, use the compress tool on it. If direction has shifted, compress earlier ranges that are now less relevant. @@ -194,6 +200,8 @@ Keep active context uncompressed. export const ITERATION_NUDGE = ` You've been iterating for a while after the last user message. +Do not narrate your compression decision. Either compress or continue silently — never output a message explaining why you are not compressing. + If there is a closed portion that is unlikely to be referenced immediately (for example, finished research before implementation), use the compress tool on it now. Prefer multiple short, closed ranges over one large range when several independent slices are ready.