List this home's registered extensions
Every extension this home has registered, in name order, with where it points, which points it sits on, which slots it claims, what was granted on it, whether it is enabled and who registered it when. No response here ever carries a secret — only the registration and the rotation that mint one do. Any member of the organisation may read this: the registry is what makes “what is reading our conversations” answerable, and one only its author could read would disclose nothing to the people whose prompts are crossing. An extension Lerian installed on a home it hosts is marked installedByOperator, which is how a customer learns it happened. Client-side extensions (pure TUI components) do not appear here — they live in the client binary.
Autorizações
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.
Resposta
Every registered extension, in one answer.
Every extension this home has registered, in one answer. It is not paged, and that is deliberate: a reader who saw a page of what reads their conversations would believe they had seen all of it, and a home with more registered extensions than one answer holds is not a shape this product has. limit and the cursors are therefore absent rather than filled with a number that would mean nothing.

