Resume can report which session it resolved against an expected id, but the flag is off.
Precomputed session resolution on resume is behind tengu_hover_rest, which defaults off.
tengu_hover_rest Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Resuming a session can now hand in a callback that reports which session was resolved, checked against an expected session id. It is behind the tengu_hover_rest flag, which defaults to off, and is skipped when you are forking a session rather than resuming one.
- Nothing in this build turns the flag on, so whether it runs is decided by server-side configuration.
onSessionResolved
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
CLAUDE_CODE_HOVER_RESTgives a local override for the new credential and settings storageBoth mention hover rest
-
v2.1.238
The v5 storage choice reads the environment variable first
Both mention hover rest
-
v2.1.238
Plaintext credential store gained an in-process cache
Both mention hover rest