Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
  • 哪裡不對？
#162 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 5 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
一週以上
新手友好度
12/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
go
領域
desktop

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
Go
星號
1.6k
分支
266
平均合併
3 天 6 小時
30 天內合併 PR
22

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

NVIDIA/Personal-AI-Router 的其他 Issue

查看 NVIDIA/Personal-AI-Router 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。