Metis

September 17, 2026 · View on GitHub

A Python library and CLI for issue triage powered by TypeSafe AI's Jev model, with a reusable GitHub Action for automatic labeling and follow-up replies. Python 3.10+, no runtime dependencies.

Python package

Distribution name: metis-triage. Import name: metis_triage. The initial PyPI release is pending; installation from this checkout is available with python -m pip install .. After publication:

pip install metis-triage

Set TYPESAFE_API_KEY in your environment, then use the library:

from metis_triage import classify_issue

result = classify_issue(
    title="App crashes when exporting a report",
    body="Clicking Export closes the app. Expected a PDF download.",
    repository="owner/repo",
)

print(result.category)
print(result.suggested_label)
print(result.needs_review)
print(result.missing_details)

classify_issue calls TypeSafe and returns a TriageResult. It makes no GitHub requests and never posts comments or applies labels. You can also pass api_key, model, and a complete config dictionary from load_config() or load_config("path/to/config.json"). With the library API, suggested labels are recommendations; the caller checks whether they exist before applying them.

The CLI prints the result as JSON:

metis-triage classify --title "Export crashes" --body-file issue.md

python -m metis_triage supports the same commands. metis-triage github runs the GitHub integration using GITHUB_EVENT_PATH, GITHUB_EVENT_NAME, GITHUB_REPOSITORY, GITHUB_TOKEN, and TYPESAFE_API_KEY from the environment. That command may apply labels and post a comment, using the same rules as the Action.

GitHub Action setup

Add the workflow below as .github/workflows/metis.yml on your repository's default branch. No script copying or checkout is needed for the default setup.
In Settings → Secrets and variables → Actions, add the repository secret TYPESAFE_API_KEY. GitHub supplies GITHUB_TOKEN automatically.
Make sure the repository has the bug, enhancement, documentation, and question labels, or provide a custom configuration as described below.
Once you are ready to run it, open an issue. Check Actions → Metis issue triage for the result. Existing issues and comments do not trigger it.

name: Metis issue triage
on:
  issues:
    types: [opened]

permissions:
  issues: write

concurrency:
  group: metis-${{ github.repository }}-${{ github.event.issue.number }}
  cancel-in-progress: false

jobs:
  triage:
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
      - uses: Ayush0054/metis@main
        with:
          typesafe-api-key: ${{ secrets.TYPESAFE_API_KEY }}

main is the initial development version; pin a commit SHA for reproducible use. The action requires Bash and Python 3.10+, available on GitHub-hosted Ubuntu runners.

The workflow requests issues: write. Organization policies must permit those permissions. Issue titles and descriptions are sent to TypeSafe for classification. Store the API key only in GitHub Secrets or your local ignored environment file.

Behavior

Classifies the primary issue purpose as bug, feature, documentation, question, or other.
Applies the corresponding existing label when both confidence thresholds pass.
Leaves unrelated labels intact and defers to conflicting existing category labels.
For clear bug reports, checks reproduction steps, expected/actual behavior, and relevant environment details in the same TypeSafe request.
Posts a fixed template listing only details judged missing. Jev selects typed decisions; it does not generate the reply text.
Skips uncertain classifications, bot-authored issues, closed issues, and oversized reports. Skips writes if the issue title or body changed during classification.
Avoids duplicate bot replies on reruns and avoids asking for information once a person has already commented. Reapplying the same label is unnecessary and skipped.
Fails the workflow on API errors or invalid responses. It never executes issue text, creates labels, assigns people, closes issues, or changes code.

Configuration

Copy the default configuration to your repository to change label names, disable missing-detail comments, or adjust thresholds. Add a checkout step before Metis, grant contents: read alongside issues: write, and pass config-path: .github/metis.json. The entire configuration file is required.

Defaults are 0.8 for Choice confidence, 0.85 for the selected category's probability, and 0.9 for each missing-detail probability. These are initial policy settings, not evaluated accuracy guarantees; tune them on your own issues when you are ready to test.

Set the action's model input to pin a model. The default is jev-latest. The optional github-token input defaults to GitHub's automatic token. Local .envrc and .env files are not loaded by the workflow.

An HTTP error during a write can leave a label applied without a reply. Rerun the failed job after resolving the error; it checks current labels and previous bot comments. Edits to the issue body do not automatically retrigger triage.

Implementation references

Publishing to PyPI

The package version is in pyproject.toml. The initial version is 0.1.0. The .github/workflows/publish.yml workflow builds the wheel and source distribution, then publishes them using PyPI Trusted Publishing. No PyPI API token is needed.

Create a pending publisher in PyPI with these exact values:

Field	Value
PyPI Project Name	`metis-triage`
Owner	`Ayush0054`
Repository name	`metis`
Workflow name	`publish.yml`
Environment name	`pypi`

Use a GitHub environment named pypi in the repository settings. After configuring the publisher and completing your desired validation, publish a GitHub release with tag v0.1.0 to trigger the first upload, or manually run Publish to PyPI on main. Later releases need a new package version and matching tag. Merely pushing commits does not run the publishing workflow.

The package has not been built, installed, or tested yet. No release has been triggered.