Skip to content

Commit 6bdbd95

Browse files
remove uid refs
1 parent 553ca89 commit 6bdbd95

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

lib/prompts/compress.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ BOUNDARY MATCHING
3939
You specify boundaries by matching unique text strings in the conversation. CRITICAL: In code-centric conversations, strings repeat often. Provide sufficiently unique text to match exactly once. If a match fails (not found or found multiple times), the tool will error - extend your boundary string with more surrounding context in order to make SURE the tool does NOT error.
4040

4141
WHERE TO PICK STRINGS FROM (important for reliable matching):
42-
- `muid` and `uid` strings in message and tool output annotations (MOST RELIABLE - guaranteed unique)
42+
4343
- Your own assistant text responses (MOST RELIABLE - always stored verbatim)
4444
- The user's own words in their messages
4545
- Tool result output text (distinctive substrings within the output)

lib/prompts/system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ MACRO: for completed phases, distilling entire chapters of conversation
1414
A strategic and regular use of the `compress` tool is encouraged to maintain a focused context. Be proactive and deliberate in managing your context.
1515

1616
BOUNDARY MATCHING
17-
`compress` uses inclusive string boundaries, matching a string at the start of a message or tool output will consume the entire item. User messages are annotated with `muid`, tool outputs with `uid`, and are intended for you to use as startString and endString anchors to avoid any potential mismatch errors. You can also use unique text from your own reasoning or text outputs, but be sure to provide more than enough surrounding context to ensure a unique match. The preferred way to match is still to use `muid` and `uid` strings.
17+
`compress` uses inclusive string boundaries, matching a string at the start of a message or tool output will consume the entire item. You can use unique text from your own reasoning or text outputs, but be sure to provide more than enough surrounding context to ensure a unique match.
1818

1919
THE SUMMARY STANDARD
2020
Your summary MUST be technical and specific enough to preserve FULL understanding of what transpired, such that NO ambiguity remains about what asked, found, planned, done, or decided - yet noise free

0 commit comments

Comments
 (0)