llmx/.github/workflows/issue-labeler.yml

name: Issue Labeler

on:
  issues:
    types:
      - opened
      - labeled

jobs:
  gather-labels:
    name: Generate label suggestions
    if: ${{ github.event.action == 'opened' || (github.event.action == 'labeled' && github.event.label.name == 'llmx-label') }}
    runs-on: ubuntu-latest
    permissions:
      contents: read
    outputs:
      llmx_output: ${{ steps.llmx.outputs.final-message }}
    steps:
      - uses: actions/checkout@v5

      - id: llmx
        uses: openai/llmx-action@main
        with:
          openai-api-key: ${{ secrets.LLMX_OPENAI_API_KEY }}
          allow-users: "*"
          prompt: |
            You are an assistant that reviews GitHub issues for the repository.

            Your job is to choose the most appropriate labels for the issue described later in this prompt.
            Follow these rules:

            - Add one (and only one) of the following three labels to distinguish the type of issue. Default to "bug" if unsure.
            1. bug — Reproducible defects in LLMX products (CLI, VS Code extension, web, auth).
            2. enhancement — Feature requests or usability improvements that ask for new capabilities, better ergonomics, or quality-of-life tweaks.
            3. documentation — Updates or corrections needed in docs/README/config references (broken links, missing examples, outdated keys, clarification requests).

            - If applicable, add one of the following labels to specify which sub-product or product surface the issue relates to.
            1. CLI — the LLMX command line interface.
            2. extension — VS Code (or other IDE) extension-specific issues.
            3. llmx-web — Issues targeting the Llmx web UI/Cloud experience.
            4. github-action — Issues with the LLMX GitHub action.
            5. iOS — Issues with the LLMX iOS app.

            - Additionally add zero or more of the following labels that are relevant to the issue content. Prefer a small set of precise labels over many broad ones.
            1. windows-os — Bugs or friction specific to Windows environments (always when PowerShell is mentioned, path handling, copy/paste, OS-specific auth or tooling failures).
            2. mcp — Topics involving Model Context Protocol servers/clients.
            3. mcp-server — Problems related to the llmx mcp-server command, where llmx runs as an MCP server.
            4. azure — Problems or requests tied to Azure OpenAI deployments.
            5. model-behavior — Undesirable LLM behavior: forgetting goals, refusing work, hallucinating environment details, quota misreports, or other reasoning/performance anomalies.
            6. code-review — Issues related to the code review feature or functionality.
            7. auth - Problems related to authentication, login, or access tokens.
            8. llmx-exec - Problems related to the "llmx exec" command or functionality.
            9. context-management - Problems related to compaction, context windows, or available context reporting.
            10. custom-model - Problems that involve using custom model providers, local models, or OSS models.
            11. rate-limits - Problems related to token limits, rate limits, or token usage reporting.
            12. sandbox - Issues related to local sandbox environments or tool call approvals to override sandbox restrictions.
            13. tool-calls - Problems related to specific tool call invocations including unexpected errors, failures, or hangs.
            14. TUI - Problems with the terminal user interface (TUI) including keyboard shortcuts, copy & pasting, menus, or screen update issues.

            Issue number: ${{ github.event.issue.number }}

            Issue title:
            ${{ github.event.issue.title }}

            Issue body:
            ${{ github.event.issue.body }}

            Repository full name:
            ${{ github.repository }}

          output-schema: |
            {
              "type": "object",
              "properties": {
                "labels": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                }
              },
              "required": ["labels"],
              "additionalProperties": false
            }

  apply-labels:
    name: Apply labels from LLMX output
    needs: gather-labels
    if: ${{ needs.gather-labels.result != 'skipped' }}
    runs-on: ubuntu-latest
    permissions:
      contents: read
      issues: write
    env:
      GH_TOKEN: ${{ github.token }}
      GH_REPO: ${{ github.repository }}
      ISSUE_NUMBER: ${{ github.event.issue.number }}
      LLMX_OUTPUT: ${{ needs.gather-labels.outputs.llmx_output }}
    steps:
      - name: Apply labels
        run: |
          json=${LLMX_OUTPUT//$'\r'/}
          if [ -z "$json" ]; then
            echo "LLMX produced no output. Skipping label application."
            exit 0
          fi

          if ! printf '%s' "$json" | jq -e 'type == "object" and (.labels | type == "array")' >/dev/null 2>&1; then
            echo "LLMX output did not include a labels array. Raw output: $json"
            exit 0
          fi

          labels=$(printf '%s' "$json" | jq -r '.labels[] | tostring')
          if [ -z "$labels" ]; then
            echo "LLMX returned an empty array. Nothing to do."
            exit 0
          fi

          cmd=(gh issue edit "$ISSUE_NUMBER")
          while IFS= read -r label; do
            cmd+=(--add-label "$label")
          done <<< "$labels"

          "${cmd[@]}" || true

      - name: Remove llmx-label trigger
        if: ${{ always() && github.event.action == 'labeled' && github.event.label.name == 'llmx-label' }}
        run: |
          gh issue edit "$ISSUE_NUMBER" --remove-label llmx-label || true
          echo "Attempted to remove label: llmx-label"