Add advisors module: custom logging, PII redaction and token-budget advisors
Tests pin down chain ordering (including ties), BaseAdvisor stream behaviour, redaction order versus memory and logging, the tool loop, and how a refusal surfaces on calls, streams and over HTTP. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Ja4jkzrbQ4LQZBNrb5mkZE
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
# Placeholders across two turns with memory
|
||||
|
||||
turn 1: My email is [email protected]
|
||||
turn 2: Also cc [email protected]
|
||||
|
||||
numbering restarts on every request:
|
||||
model was sent on turn 2: U:My email is <EMAIL_1> | A:You said: My email is <EMAIL_1> | U:Also cc <EMAIL_1>
|
||||
caller receives: You said: Also cc [email protected]
|
||||
|
||||
numbering kept per conversation (the default):
|
||||
model was sent on turn 2: U:My email is <EMAIL_1> | A:You said: My email is <EMAIL_1> | U:Also cc <EMAIL_2>
|
||||
caller receives: You said: Also cc [email protected]
|
||||
|
||||
what the memory stores (placeholders, never the addresses):
|
||||
USER My email is <EMAIL_1>
|
||||
ASSISTANT You said: My email is <EMAIL_1>
|
||||
USER Also cc <EMAIL_2>
|
||||
ASSISTANT You said: Also cc <EMAIL_2>
|
||||
Reference in New Issue
Block a user