Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

Retrieve a local session changedapi/compliance/apps/sessions/local/retrieve

Nearest release: v2.1.242, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+6added
Lines−1removed
From line 44 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits11to this page, all time

The whole hunk

from line 44, old and new numbered
/
lines
from line 44
4444 
4545 - `"compliance_local_session"`
4646 
47- `updated_at: string`
48 
49 Timestamp of the session's last retained inference call (RFC 3339, UTC). Always at or after `created_at`. When a session's activity spans the child organization's retention boundary, calls older than the boundary are no longer reflected — but because retention removes only the oldest calls, this value (unlike `created_at`) is unaffected until the entire session has aged out. On the list endpoint this value is a lower bound: for a session still active at a page or `created_at.lt` window boundary it can momentarily lag the session's true last activity. Retrieving the session, or its messages, always reflects the exact latest retained call.
50 
4751- `user: object { id, email_address }`
4852 
4953 The authenticated user at the time of the session. Always set; `user.id` is always populated. `user.email_address` is null when the user's account has been deleted or the user is no longer a member of an organization the key may read.
from line 84
8084 "email_address": "[email protected]"
8185 },
8286 "product_surface": "cowork",
83 "created_at": "2026-07-09T14:02:11Z"
87 "created_at": "2026-07-09T14:02:11Z",
88 "updated_at": "2026-07-09T15:47:33Z"
8489}
8590```
8691 
Feedback