> ## 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.

# Decide a permission ask

> Allows or denies a pending ask, optionally remembering the decision for the session or permanently. A denial is reported to the agent with its reason and the agent continues rather than crashing. Every decision is recorded in the audit. Deciding an already-decided ask is a conflict.



## OpenAPI

````yaml /en/openapi/v3-current/narya.yaml post /v1/permissions/{permissionId}/decision
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
    runs on your machine and serves this API over a Unix socket in your Narya
    home. Narya creates the socket owner-only, and file permissions are the
    whole authorization. There is no password, no token and no TLS. The terminal
    client and the one-shot command that Lerian ships drive this API, and a
    client you write drives the same one.


    Results never arrive on the response of the request that caused them.
    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, message, and fields on 422. Codes are NRY-
    followed by four digits. A paged list answers items, limit and a nextCursor
    when more remains. Cursors are opaque.
servers: []
security: []
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: 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: 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.
paths:
  /v1/permissions/{permissionId}/decision:
    parameters:
      - $ref: '#/components/parameters/PermissionIdParam'
    post:
      tags:
        - permissions
      summary: Decide a permission ask
      description: >-
        Allows or denies a pending ask, optionally remembering the decision for
        the session or permanently. A denial is reported to the agent with its
        reason and the agent continues rather than crashing. Every decision is
        recorded in the audit. Deciding an already-decided ask is a conflict.
      operationId: decidePermission
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PermissionDecisionRequest'
      responses:
        '200':
          description: >-
            The recorded decision. This operation answers a PENDING ask and 409s
            anything else, so `decidedBy` and `decidedAt` are always present in
            this response. They are optional on the shared schema because the
            audit listing reports `expired` entries too, which nobody decided —
            a client reading only this operation may treat both as guaranteed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PermissionDecisionRecord'
        '400':
          $ref: '#/components/responses/BadRequest'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
        '422':
          $ref: '#/components/responses/UnprocessableEntity'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    PermissionIdParam:
      name: permissionId
      in: path
      required: true
      description: The permission ask's id.
      schema:
        type: string
        format: uuid
  schemas:
    PermissionDecisionRequest:
      type: object
      description: >-
        A decision on a pending permission ask. A denial is never remembered:
        remember must be none (or absent) whenever decision is deny, and any
        other combination is refused with 400. The host offers four answers —
        allow once, allow always in this project, allow always globally, and
        deny with a message — so a remembered refusal is not one of them, and
        the prompt states before the answer exists that remembering would grant
        an allow rule.
      required:
        - decision
      properties:
        decision:
          type: string
          enum:
            - allow
            - deny
        remember:
          type: string
          enum:
            - none
            - session
            - project
            - global
          default: none
          description: >-
            Scope to remember the decision at — none decides only this ask,
            session remembers for this session, project appends a rule scoped to
            this repository, global appends a rule to the user's own
            configuration. Two "always" scopes rather than one because "fine in
            THIS repository" and "fine everywhere I work" are different claims,
            and a single "always" forces everybody to over-grant. Only an allow
            is remembered; any scope other than none alongside decision=deny is
            a 400.
        message:
          type: string
          maxLength: 4096
          description: >-
            Optional correction shown to the agent, useful on deny. It reaches
            the model verbatim as something it can act on: a denial saying only
            "denied" teaches nothing, so the model tries a variant and burns the
            turn, while "do not push to main, open a PR branch instead" ends the
            exchange.
      examples:
        - decision: deny
          remember: none
          message: Do not push; open a PR branch instead.
    PermissionDecisionRecord:
      type: object
      description: >-
        One entry of the decision audit. There is exactly one decision per ask,
        so the decision's id IS the ask's id: id and permissionId carry the same
        identifier.


        WHAT IS RECORDED, stated here because it is narrower than "every
        decision" and deliberately so: every ASK and its answer, whoever
        answered it, and every DENY — including the ones taken without asking
        anybody, which is the shape almost every denial has in unattended work.
        A rule-derived ALLOW on a free action is NOT a row. Recording every
        permitted read would write thousands of rows per session and bury the
        two questions this audit exists to answer — what was denied and why, and
        what did I approve.


        AND A DECISION IS NOT A RECORD OF EXECUTION. It says what was decided,
        not what ran: a call interrupted in the same instant its decision was
        released can leave an `allow` here for something that never happened.
        Read it as the trail of judgements, and the transcript for what
        followed.
      required:
        - id
        - permissionId
        - decision
        - requestedAt
      properties:
        id:
          type: string
          format: uuid
        permissionId:
          type: string
          format: uuid
        sessionId:
          type: string
          format: uuid
        action:
          type: string
          maxLength: 128
        resource:
          type: string
          maxLength: 4096
        decision:
          type: string
          enum:
            - allow
            - deny
            - expired
          description: >-
            `expired` is an ask nobody answered before the call it was blocking
            ended. It carries no decider and no decidedAt, because "nobody
            answered" is itself the finding when somebody asks why an action did
            not happen.
        decidedBy:
          type: string
          enum:
            - user
            - policy
            - hook
          description: >-
            Who decided — a human, the policy deciding without asking (which
            includes a rule that landed after the ask was raised and covered
            it), or the configured executable at the permission-ask decision
            point. Absent on an expired entry.
        reason:
          type: string
          maxLength: 4096
          description: >-
            Why, in the decider's own words: a person's message on a
            deny-with-message, the rule a policy refusal names, or the hook that
            decided — a hook denial that does not say which hook is an audit
            trail ending in a shrug. Absent when the outcome speaks for itself.
        remember:
          type: string
          enum:
            - none
            - session
            - project
            - global
        requestedAt:
          type: string
          format: date-time
          description: >-
            When the decision was raised. It is what the audit is ordered and
            paged by, so a page boundary is stable while new decisions land.
        decidedAt:
          type: string
          format: date-time
          description: Absent on an expired entry, which nobody decided.
      examples:
        - id: 3f1e5d7c-2b4a-4c6e-8d0f-9a1b3c5d7e9f
          permissionId: 7e5d3c1b-9a8f-4e6d-b2c4-0f1a3b5c7d9e
          sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d
          action: shell
          resource: git push origin main
          decision: deny
          decidedBy: user
          reason: do not push to main, open a PR branch instead
          remember: none
          requestedAt: '2026-08-08T12:20:58.000Z'
          decidedAt: '2026-08-08T12:21:00.000Z'
    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. fields appears only on 422 validation errors,
        mapping each offending property to its problem.
      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. Present on 422 only.
          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:
    BadRequest:
      description: Malformed request — invalid parameter, cursor, or JSON body.
      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'
    Conflict:
      description: >-
        The resource's current state rejects the request — archived session,
        busy lane, slot conflict, failed build, already-final state.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    UnprocessableEntity:
      description: >-
        The request was well-formed but failed validation. The error's fields
        map names each offending property.
      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'

````