Not switched on
Useful2 Signal3
/context can render without the memory-files section under an unnamed condition.
Both context views support an emptied memory list chosen per session.
What's wrong with this entry?
Anonymous. No account, no email.
/context
What
Both the local and remote /context views can now render with the memory-files list emptied and the collapse status skipped, chosen by a per-session condition.
Details
- The remote path re-checks the condition after its async render and re-renders if it changed mid-flight.
- The condition is computed inline and does not correspond to a named flag or setting in this build, so what turns it on is not visible here.
Evidence
skipCollapseStatus
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.229
Session context is built lazily and cached per project root
Both mention context
-
v2.1.232
/context returns a structured breakdown of token usage
Both mention context
-
v2.1.232
/context returns machine-readable usage alongside the table
Both mention context