Unverified50% confidenceFactExact time
In each task pair of EpiSEM-Bench, the tasks share the same user request, tool interface, and most of the environment state, with the only controlled difference being whether a certain key safety fact is included in the tool response.
1
Sources
50%
Confidence
Long-term
Relevance
10/23/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen a user's custom system prompt conflicts with security-level instructions injected by the platform, the platform instructions generally take higher priority.66% similarUnverifiedA successful tool connection only means it can be called; whether memories are automatically saved each round or automatically recalled each session depends on the specific integration configuration.66% similarUnverifiedThe non-determinism in tool call ordering causes cache keys based on request body hashes to identify functionally identical requests as different requests, resulting in cache misses.66% similarUnverifiedEvery exposed tool consumes context Tokens on every request; information such as tool definitions, parameter descriptions, and return value formats all needs to be stuffed into the model context.65% similarUnverifiedAfter the tool list is pinned, the set of available tools is locked for the entire session, ensuring the model sees the same tool declarations in every interaction round.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1088278API
curl https://kongchang.com/api/v1/knowledge/claims/1088278MCP
get_claim(id=1088278)