You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/prompts/nudge.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,13 @@ The context window is filling-up. You've reached a point where performance may i
18
18
19
19
Avoid unnecessary context build-up with targeted uses of the `compress` tool. Start with low hanging fruits and clearly identified ranges that can be compressed with minimal risk of losing critical information. Look BACK on the conversation history and avoid compressing the newest ranges until you have exhausted older ones
20
20
21
+
SCALE PRIORITY (MANDATORY)
22
+
Use MICRO first.
23
+
Escalate to MESO when MICRO is insufficient.
24
+
Use MACRO only as a last resort when a larger chapter is truly closed and bounded.
25
+
Do not jump directly to MACRO when independent MICRO/MESO ranges are available.
26
+
When multiple independent stale ranges are ready, batch MICRO/MESO compressions in parallel.
27
+
21
28
If you are performing a critical atomic operation, do not interrupt it, but make sure to perform context management rapidly
22
29
23
30
Be mindful of the startString and endString you use for compression and prefer using `muid` and `uid` strings for reliable boundary matching. Ensure your summaries are inclusive of all parts of the range.
0 commit comments