Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Feature]: PAIR feedback: model-level routing toggles, controlled test runs, and concurrency controls

Ouverte
  • Quelque chose ne va pas ?
#162 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 5 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
go
Domaine
desktop

Piste de recherche

This is a broad feature request covering several separate controls: per-model routing toggles, keep-loaded, concurrency limits, and test-runner scope. No files, tests or entry points are named in the payload, so start by locating the model load/eject actions and the test runner in the desktop UI. Done would mean the request is split into smaller issues with agreed scope.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement
Area

Desktop experience

User problem

Hi NVIDIA PAIR team,

First, thank you for building and releasing Personal AI Router. I’m genuinely excited about the product. I love NVIDIA’s local AI direction, and PAIR is exactly the kind of tool I want to use across my RTX machines.

After setting up PAIR across two Windows systems, I ran into a few workflow issues that I think could be improved with some model-level controls.

Right now, PAIR appears to expose model actions like load and eject, but I could not find a clean way to decide which installed models are eligible for routing. That makes the routing behavior feel too automatic. I would love to see controls such as:

  • Enable/disable routing per model
  • Keep-loaded toggle per model
  • Max concurrent models per node
  • Preferred node per model
  • “Test selected model only”
  • “Test selected node only”
  • A safer “test all” mode that runs one model at a time, or with a visible concurrency limit
  • Time Based Scheduled Loading of Model or Models and Model Grouping

In my setup, the broad test behavior appeared to launch many workload checks across many models at once. Some tests passed, but many failed with messages like “client disconnected before completion” or “context canceled.” When I tested specific models one at a time, the routes worked much more reliably. So the issue seemed less like every model was broken and more like the test runner was overloading the environment or timing out before queued model loads could complete.

I think PAIR would be much easier to trust if installed models, loaded models, and routing-eligible models were treated as separate states in the UI.

Thank you again for the work on PAIR. I’m excited about where this is going, and I hope this feedback is useful.

Best,
Chris

Desired outcome
  • Enable/disable routing per model
  • Keep-loaded toggle per model
  • Max concurrent models per node
  • Preferred node per model
  • “Test selected model only”
  • “Test selected node only”
  • A safer “test all” mode that runs one model at a time, or with a visible concurrency limit
  • Time Based Scheduled Loading of Model or Models and Model Grouping
Alternatives considered

No response

Compatibility and security implications

No response

Validation approach

No response

Confirmations
  • I searched existing issues for duplicates.
  • I agree to follow the Code of Conduct.
Langage dominant
Go
Étoiles
1.6k
Forks
266
Merge moyen
3 j 15 h
PR mergées (30 j)
23

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de NVIDIA/Personal-AI-Router

Toutes les issues de NVIDIA/Personal-AI-Router

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.