From 00af680341fd9e8ae5297c7803d4c6a30fa2cd08 Mon Sep 17 00:00:00 2001 From: Samuel Newman Date: Mon, 3 Aug 2026 16:47:33 +0300 Subject: [PATCH] document the public client labeler asymmetry Co-Authored-By: Claude Fable 5 --- src/state/session/clients.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/state/session/clients.ts b/src/state/session/clients.ts index 58c082893e..ff6a597ac7 100644 --- a/src/state/session/clients.ts +++ b/src/state/session/clients.ts @@ -55,6 +55,13 @@ let publicLexClient: Client | undefined * {@link agentToLexClient}: there is no session to scope it to, so it lives for * the lifetime of the process. Requests go through {@link networkAwareFetch} so * public reads feed the app's reachability signal like authenticated ones do. + * + * Unlike the public agent it parallels, this client sends neither + * `atproto-proxy` nor `atproto-accept-labelers`. `createPublicAgent` configures + * the app labeler and the proxy header, so a logged-out appview *agent* read + * does carry labelers while the same read through this client does not. A + * consumer that needs moderation labels on public reads must configure labelers + * itself before issuing the request. */ export function getPublicLexClient(): Client { return (publicLexClient ??= createLexClient({