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
14 lines
494 B
Plaintext
14 lines
494 B
Plaintext
# LoggingAdvisor: a call and a stream
|
|
|
|
call, content logging off (the default):
|
|
[LoggingAdvisor] request messages=2 roles=SU
|
|
[LoggingAdvisor] response chars=14 tokens=12+3 took 5 ms
|
|
|
|
stream:
|
|
[LoggingAdvisor] request messages=2 roles=SU
|
|
[LoggingAdvisor] complete 3 chunks, 14 chars tokens=12+3 took 5 ms
|
|
|
|
call, content logging on:
|
|
[LoggingAdvisor] request messages=1 roles=U last="Where is my refund?"
|
|
[LoggingAdvisor] response chars=14 tokens=5+3 text="Refund issued." took 5 ms
|