> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # The live shares of this session, and who each one is for > What this session has been published as, from the publishing end: one row per share that is still live, carrying who it is for. IT IS THE WAY IN TO CHANGING THAT AUDIENCE. A share is retargeted by its id (`PUT /v1/shares/{shareId}/recipients`) and a person has a conversation rather than a 26-character id, so this is where a client learns which shares exist and what each one currently names. A client holds no share id of its own between runs and derives nothing. REVOKED AND EXPIRED SHARES ARE NOT HERE. Their entries have been deleted and their audience can never change again, so a row for one would be an offer to retarget a conversation that no longer exists. WHO MAY READ IT is narrower than who may read the session: whoever opened the session, or a member carrying `members:manage`. A colleague who may read the conversation may not read the list of the colleagues it was addressed to — that list is a statement about people rather than about the work, which is the line the disclosure audit beside it already holds and the reason a recipient's own read of a copy never reports who else was named. A caller who may not is answered 403 NRY-0028. A SHARE THIS CALLER MAY NOT CHANGE IS NOT HERE EITHER, so no row is ever offered that `PUT /v1/shares/{shareId}/recipients` would refuse. The rows are the shares this caller may settle: their own, and every one of them for a member carrying `members:manage`. A session somebody ELSE published — which an unmarked session allows, since it is the organisation's already — therefore lists nothing for the person whose session it is, rather than a row naming the colleagues another member addressed their work to. An empty list is "nothing here for you to change" and not "this was never published". ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml get /v1/sessions/{sessionId}/share openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. One long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. An operation that declares another security scheme also accepts that credential. A request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/sessions/{sessionId}/share: parameters: - $ref: '#/components/parameters/SessionIdParam' get: tags: - sharing summary: The live shares of this session, and who each one is for description: >- What this session has been published as, from the publishing end: one row per share that is still live, carrying who it is for. IT IS THE WAY IN TO CHANGING THAT AUDIENCE. A share is retargeted by its id (`PUT /v1/shares/{shareId}/recipients`) and a person has a conversation rather than a 26-character id, so this is where a client learns which shares exist and what each one currently names. A client holds no share id of its own between runs and derives nothing. REVOKED AND EXPIRED SHARES ARE NOT HERE. Their entries have been deleted and their audience can never change again, so a row for one would be an offer to retarget a conversation that no longer exists. WHO MAY READ IT is narrower than who may read the session: whoever opened the session, or a member carrying `members:manage`. A colleague who may read the conversation may not read the list of the colleagues it was addressed to — that list is a statement about people rather than about the work, which is the line the disclosure audit beside it already holds and the reason a recipient's own read of a copy never reports who else was named. A caller who may not is answered 403 NRY-0028. A SHARE THIS CALLER MAY NOT CHANGE IS NOT HERE EITHER, so no row is ever offered that `PUT /v1/shares/{shareId}/recipients` would refuse. The rows are the shares this caller may settle: their own, and every one of them for a member carrying `members:manage`. A session somebody ELSE published — which an unmarked session allows, since it is the organisation's already — therefore lists nothing for the person whose session it is, rather than a row naming the colleagues another member addressed their work to. An empty list is "nothing here for you to change" and not "this was never published". operationId: listSessionShares responses: '200': description: The live shares of this session, newest first. content: application/json: schema: $ref: '#/components/schemas/SessionShareList' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' components: parameters: SessionIdParam: name: sessionId in: path required: true description: The session's id. schema: type: string format: uuid schemas: SessionShareList: type: object description: >- The live shares of one session, newest first. NO CURSOR AND NO LIMIT. A session is published once, occasionally twice, and every row is one a person may act on — so paging here would be a mechanism guarding a list that is already short. required: - shares properties: shares: type: array items: $ref: '#/components/schemas/SessionShare' examples: - shares: - shareId: K7QX2ZM4YB6PWNRJ5TFHCDA3EV sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d mode: sync state: active createdAt: '2026-09-08T09:15:00.000Z' expiresAt: '2026-10-08T09:15:00.000Z' recipients: - user_grace SessionShare: type: object description: >- One session published to the organisation's home, as this home records it. required: - shareId - sessionId - mode - state - createdAt properties: shareId: type: string description: >- The share's id, which addresses it everywhere outside this home — a URL, the organisation's home, whatever a colleague pastes into a chat. Drawn from a cryptographic source and unrelated to sessionId by construction, so it discloses nothing about the session or the machine it came from. minLength: 26 maxLength: 26 pattern: ^[A-Z2-7]{26}$ sessionId: type: string format: uuid description: >- The session in THIS home that was published. It is provenance: at the organisation's home the same share is addressed by shareId and that session does not exist there. mode: type: string enum: - once - sync description: Where this publish stops. state: type: string enum: - pending - active - revoked description: >- How far it has got. `pending` is a share whose first entry has not reached the organisation's home — which is what a 503 NRY-0029 leaves behind. `active` is a share the organisation's home holds: complete for `once`, still following for `sync`. `revoked` is terminal. Whether a share has EXPIRED is deliberately not a state here: that is a comparison against a clock, and a stored copy of it would go stale on its own. createdAt: type: string format: date-time description: When the person asked for it. expiresAt: type: string format: date-time readOnly: true description: >- When this share stops: the instant the publish named, or the host's configured window from when it was asked for. It is the host's answer and never a client's calculation. A share whose expiry has passed is closed whether or not the sweep that deletes it has run yet — which is why `state` carries no `expired` value. Once the sweep HAS run, the copied entries are deleted and the state reads `revoked`, because that is what happened to it. recipients: type: array readOnly: true items: type: string description: >- Who this share is for, as the host now holds it: the subjects named on it, or ABSENT for the whole organisation. It is the host's record and never a client's copy of what it asked for. examples: - shareId: K7QX2ZM4YB6PWNRJ5TFHCDA3EV sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d mode: sync state: active createdAt: '2026-09-08T09:15:00.000Z' expiresAt: '2026-10-08T09:15:00.000Z' recipients: - user_grace - user_auditor Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. responses: Forbidden: description: >- The caller is authenticated and is not allowed this operation (NRY-0028 or NRY-0030). content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: The addressed resource does not exist on this host. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation. ````