Session metadata gains hostSessionId and outsideOrgReader fields

Session metadata and permission info now include new hostSessionId and outsideOrgReader fields

Under the hood No documentation found Internal Changes

JSON All of v2.1.274

Under the hoodTier: how much it should matter to you

2Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

Session ManagementArea: what it touches

Internal ChangesKind: in v2.1.274, 16 Sep 26

Internal ChangesSection of the release

Unclear What hostSessionId and outsideOrgReader are used for is not stated.

What

Session data now carries two small additions:

hostSessionId is included in the session snapshot output.
outsideOrgReader is included in the role/permission information built for a session.

Why

The finding doesn't say what these fields are used for, but their presence means session snapshots and permission checks now carry more information than before.

Read from

Names in the bundlehostSessionIdoutsideOrgReader

How sure we are

Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.

The writer flagged doubtWhat hostSessionId and outsideOrgReader are used for is not stated.

See this entry in the whole of v2.1.274 →

The build it came inv2.1.274

16 Sep 2026 · 324 entries, this one is #318.

Use it now23
You'll notice109
Nothing to try yet25
Under the hood167

Either side of it

v2.1.273Older
v2.1.275Newer

Open the release →

Names in this entry

settinghostSessionId
Session registration now reports a hostSessionId read from the CLAUDE_CODE_HOST_SESSION_ID environment variable
settingoutsideOrgReader
Reading a file from an artifact now supports a public-read path for requesters outside the artifact owner's organization

Is this right?