Skip to content

docs: capture non-persistent run cache oracle #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bingran-you merged 1 commit into from
Apr 9, 2026
Merged

docs: capture non-persistent run cache oracle #163

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...guardrails/verification-and-native-test-oracles/real-cli-e2e-scenario-corpus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,7 @@ Soft assertions should avoid overfitting to:

- Entry: in a brand-new directory, run one headless prompt with `--no-session-persistence`, then immediately run `claude -p -c ...`.
- Expect: the second command behaves like no saved session exists for that directory.
- Observed reality: that non-persistent mode only severs local session save and later continuation semantics. It does not imply a cold provider-side prompt cache. Repeating the same headless command, even with an explicit `--session-id`, can still shift usage from cache-creation into cache-read fields across independent invocations.
- Failure signal: ephemeral sessions still leak into the resume index or can be discovered by `-c`.
- Why it matters: automation-grade ephemeral runs need a true non-persistent mode.

Expand Down
Loading