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

# List slash commands

> Lists every command file that can be expanded for work in this repository — an installed package's declared commands, the person's own under $NARYA_HOME/commands and ~/.claude/commands, and, only in a trusted repository, the project's own .claude/commands and .narya/commands. Name, description, argument hint, and where the file came from; never the body, which expandCommand is for. Notices carries the loaders' own complaints.



## OpenAPI

````yaml /en/openapi/v3-current/narya.yaml get /v1/commands
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/commands:
    get:
      tags:
        - ladder
      summary: List slash commands
      description: >-
        Lists every command file that can be expanded for work in this
        repository — an installed package's declared commands, the person's own
        under $NARYA_HOME/commands and ~/.claude/commands, and, only in a
        trusted repository, the project's own .claude/commands and
        .narya/commands. Name, description, argument hint, and where the file
        came from; never the body, which expandCommand is for. Notices carries
        the loaders' own complaints.
      operationId: listCommands
      parameters:
        - $ref: '#/components/parameters/LadderRepositoryParam'
        - $ref: '#/components/parameters/CursorParam'
        - $ref: '#/components/parameters/LimitParam'
      responses:
        '200':
          description: One page of command files.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommandPage'
        '400':
          $ref: '#/components/responses/BadRequest'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    LadderRepositoryParam:
      name: repository
      in: query
      required: false
      description: >-
        Absolute path of the repository to resolve skills and command files for.
        A repository's own .claude and .narya directories are read only when it
        is named here AND it has been trusted; with no repository named, the
        answer carries the user's own files and the installed packages' only. It
        also decides where a command's shell blocks run.
      schema:
        type: string
        maxLength: 4096
    CursorParam:
      name: cursor
      in: query
      required: false
      description: >-
        Opaque pagination cursor from a previous page's nextCursor or
        prevCursor.
      schema:
        type: string
        maxLength: 1024
    LimitParam:
      name: limit
      in: query
      required: false
      description: Maximum items per page.
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 25
  schemas:
    CommandPage:
      type: object
      description: >-
        One page of command files, plus whatever the loaders complained about
        while reading them.
      required:
        - items
        - limit
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/Command'
        limit:
          type: integer
          minimum: 1
        nextCursor:
          type: string
        notices:
          type: array
          description: >-
            Standing facts about the COMMAND files on this machine's disk, in
            the words a person reads — scoped to this listing, the way
            SkillPage.notices is scoped to that one.
          items:
            type: string
      examples:
        - items:
            - name: review
              description: Review the working tree for correctness.
          limit: 25
    Command:
      type: object
      description: >-
        One command file as a client renders it: what "/" reaches it by, the
        author's description, the hint for what to type after the name, and
        where the file came from. The body is absent — expandCommand is what
        turns this into text.
      required:
        - name
      properties:
        name:
          type: string
          pattern: ^[^\s/\\]+$
          maxLength: 128
        description:
          type: string
          maxLength: 4096
        argumentHint:
          type: string
          description: >-
            A human sketch of what to type after the name, e.g. "<file>
            [--fix]".
          maxLength: 4096
        path:
          type: string
          description: >-
            The file this was read from. It is what a refusal names when two
            files claim one command name: for a package's own file the package
            name says enough, but for two files somebody wrote themselves the
            path is the only thing they can act on.
          maxLength: 4096
        sourcePackage:
          type: string
          description: >-
            The installed package that shipped the file; absent for the person's
            own and a trusted repository's. A package's command never runs shell
            blocks, whatever the repository's trust answer says. Spelled as
            Skill.sourcePackage and Agent.sourcePackage are: the three are read
            off one resolution order and mean one thing, so a client rendering
            them reads one name for it.
      examples:
        - name: review
          description: Review the working tree for correctness.
          argumentHint: '[path]'
          path: /home/dev/.claude/commands/review.md
    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'
    InternalServerError:
      description: The host failed — including a store that refuses writes (NRY-0012).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'

````