Group of 2 Under the hood
The memory-context system adds a not-yet-active laptop path and parses a new guidance field that isn't used yet
What
- The memory-context fetch logic, previously built only for "ccr"/cowork sessions, was rewritten to support two paths ("legs"): the existing "ccr" leg and a new "laptop" leg, currently inactive. This adds its own telemetry, org-policy handling (open/pending/denied/closed states), and etag/withdrawal handling.
- The
/memory_contextresponse format now accepts an optionalguidancestring (up to 4096 characters) alongside the existingversion,content, andversionsfields. It's parsed out of the response but not yet stored or used anywhere.
Why These are groundwork changes: the laptop leg is currently dark (disabled) and the guidance field is parsed but discarded, so nothing changes for users yet, but the pieces are in place for memory context to eventually work on more session types and carry additional guidance.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what `guidance` is intended to be used for once it is wired up.