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 天 15 小时
30 天内合并 PR
23

环境准备

从这里开始

  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 摘要。