role-model:混合本地与云端AI的智能路由协议
评分
49精选理由
开创性地将路由概念引入AI模型调度,实用性强且设计简洁,但生态尚处早期,评分85。
AI 点评
「随着AI模型爆发式增长,企业需要灵活协调本地与云端资源,role-model以极简的协议解决了模型选择与路由的痛点,降低混合部署门槛。」
速览
role-model 是一个开源协议,用于在本地和云端AI模型之间智能分配任务,支持混合使用或跨多个云提供商路由。它通过配置角色(role)定义任务需求,并自动选择最合适的模型(本地或云端),实现成本、隐私与性能的平衡。适合希望灵活调用多种AI资源的开发者。
- 提供统一的配置接口,将本地LLM(如Llama)与云端API(如OpenAI)无缝结合
- 支持基于角色(role)的声明式路由,每个角色可绑定多个模型及权重
- 内置故障转移和负载均衡,避免单点依赖
- 零依赖、轻量级,易于集成到现有工作流
正文
role-model
role-model is an open protocol for capability-aware AI routing, plus a reference router that implements
that protocol.
It gives a router a durable contract for describing what a request needs, what an endpoint can do, what policy allows, and why a final routing decision was made.
What role-model does
Every AI workload eventually faces the same question: which model should handle this request? The answer
depends on task type, required capabilities, cost, latency, and whether the model is running locally or in
the cloud. role-model makes that decision explicit, explainable, and portable.
At a high level, role-model separates AI routing into a few stable pieces:
- Requests describe task type, required capabilities, modalities, tool needs, and constraints.
- Endpoint identities and profiles describe concrete routable endpoints rather than abstract model names.
- Routing policy applies hard denies, preferences, budgets, and tie-break rules.
- Observability artifacts record the decision, trace, usage, and observed performance.
The reference router supports hybrid routing across three deployment shapes:
- Local / Local - route between local models (e.g., llama-swap peers) based on role, task, and capability
- Local / Cloud - route between a local model and a cloud provider based on cost, latency, and task difficulty
- Cloud / Cloud - route between cloud providers (e.g., OpenAI, DeepSeek, Moonshot) based on capability and economics
This means a single runtime can serve a quick chat request from a fast local model, route a complex coding task to a capable cloud model, and fall back to a cheaper cloud endpoint when the primary is degraded, all under one explainable routing contract.
Install the runtime
For end users, prefer the packaged standalone runtime over a source build.
macOS and Linux
curl -fsSL https://raw.githubusercontent.com/try-works/role-model/main/scripts/install.sh | sh
The installer downloads the latest GitHub Release archive, installs it under
~/.local/share/role-model-router/<version>/<target>/, and exposes a role-model-router launcher in
~/.local/bin.
Windows
irm https://raw.githubusercontent.com/try-works/role-model/main/scripts/install.ps1 | iex
The installer downloads the latest GitHub Release archive, installs it under
%LOCALAPPDATA%\Programs\RoleModelRouter\<version>\<target>\, and creates a role-model-router.cmd
launcher.
Manual downloads
If you do not want to use installer scripts, download the matching archive from GitHub Releases.
| Platform | Archive | Launch |
|---|---|---|
| Windows | role-model-router-win32-x64.zip |
Role-Model.bat or role-model-runtime.exe |
| macOS x64 | role-model-router-darwin-x64.tar.gz |
role-model-runtime |
| macOS arm64 | role-model-router-darwin-arm64.tar.gz |
role-model-runtime |
| Linux x64 | role-model-router-linux-x64.tar.gz |
role-model-runtime |
Installation for Pi
The pi-role-model package connects Pi to an externally running Role-Model runtime.
Start the Role-Model runtime first, then install the public Pi package:
pi install npm:@try-works/pi-role-model
For local checkout testing from this repository, install the package directly:
pi install ./packages/pi-role-model
Inside Pi, run:
/role-model setup
/role-model doctor
/role-model alias list
/role-model alias choose
/role-model alias use <alias>
/role-model requests
/role-model explain latest
By default the package connects to http://127.0.0.1:3456 and registers Role-Model as the
role-model provider using /api/role-model/downstream/openai. Set ROLE_MODEL_ENDPOINT
before starting Pi to use a different local runtime. Remote endpoints require explicit
trusted allowRemote behavior, and runtimes that report authentication.required fail
closed unless a future supported token source is configured. For local development installs
and the full command reference, see
packages/pi-role-model/README.md.
Develop from source
Prerequisites
- Node.js 24 (required for
node:sqliteand SEA support) - pnpm 10.x (via
corepack enable) - Go 1.24+ (for llama-swap vendor binary and Windows launcher)
corepack enable corepack pnpm install
Smoke test
corepack pnpm run smoke
For a fuller walkthrough, see docs/public/quickstart.md.
Development build
Run the bridge and UI in development mode (separate processes):
# Terminal 1: bridge server cd role-model-router/apps/runtime-host-bridge corepack pnpm exec tsx scripts/start-for-qa.ts # Terminal 2: UI dev server cd role-model-router/apps/runtime-ui corepack pnpm exec react-router dev --port 5173 --host 127.0.0.1
Then open http://127.0.0.1:5173 in your browser.
Production build (all platforms)
Build the UI and package the SEA runtime:
# Build UI static files corepack pnpm --filter @role-model-router/runtime-ui run build # Package the bridge as a single executable corepack pnpm run runtime:package-sea
Output: role-model-router/dist/release/<platform-arch>/role-model-runtime
Windows desktop launcher
Build a complete Windows package with dedicated browser window:
# 1. Build UI corepack pnpm --filter @role-model-router/runtime-ui run build # 2. Package bridge SEA runtime corepack pnpm run runtime:package-sea # 3. Build Go launcher cd role-model-router/apps/launcher go build -o ../../dist/release/win32-x64/role-model-launcher.exe main.go # 4. Bundle UI files cp -r ../runtime-ui/build/client ../../dist/release/win32-x64/
Then double-click role-model-launcher.exe in dist/release/win32-x64/. It will:
- Start the bridge server on port 3456
- Open Microsoft Edge in app mode (dedicated window)
- Serve the UI directly from the bridge (no separate dev server)
Documentation
| Read this | If you want |
|---|---|
docs/public/README.md |
the docs hub |
docs/public/introduction.md |
what role-model is and why it exists |
docs/public/quickstart.md |
a real end-to-end smoke run |
docs/public/concepts/how-role-model-works.md |
the system flow |
docs/public/concepts/protocol-overview.md |
the protocol surface |
docs/public/concepts/routing-overview.md |
how routing decisions happen |
protocol/README.md |
canonical schemas and fixtures |
role-model-router/README.md |
reference router packages and runtime apps |
docs/protocol/routing-policy.md |
routing policy reference |
docs/protocol/taxonomy-v1.md |
taxonomy V1 groups, roles, tasks, and Pi classification |
docs/protocol/roles.md |
role metadata reference |
docs/protocol/tasks.md |
task metadata reference |
docs/operations/02-ci-and-release-flow.md |
CI, release automation, and workflow ownership |
CHANGELOG.md |
release history |
Acknowledgements
role-model builds on the work of several open-source projects:
- llama-swap - the vendored local model lifecycle manager that handles process supervision, request forwarding, and model swapping for local endpoints
- LiteLLM - the unified LLM API abstraction whose provider catalog, model metadata, and pricing data inform the routing-compatible provider inventory
License
This repository is licensed under BUSL-1.1 with a project-specific
Additional Use Grant. Internal production use, evaluation, development,
modification, and non-production redistribution are permitted under the root
license. Hosted or managed third-party services, paid product embedding, and
third-party commercialization require a separate commercial license.
See LICENSE for the full terms. Contributions require acceptance of the Contributor License Agreement before they can be merged.
Only individual contributions are accepted. Please do not submit work owned by an employer, client, company, or other entity unless you personally have the right to contribute it under this project's terms.
相关条目
精选DeepSeek V4 在 OpenRouter 上的代币份额翻倍,智能体工作负载成主要驱动力
DeepSeek V4 的快速采用表明市场对高性能、低成本推理模型的强烈偏好,尤其是智能体场景将重塑 AI 部署格局。
91
精选启用两项设置使ARC-AGI-3基准测试分数提升三倍
这项发现太关键了!它表明模型的性能不仅取决于训练,还取决于推理时的配置。对于AI工程师和研究者来说,这是一个必须注意的优化方向。特别是那些在资源受限设备上部署模型的团队,可能会因此找到低成本提升能力的方法。
91
精选GPT-5.6:前沿智能与前沿效率的融合
这条消息值得关注,因为它标志着大模型竞争从单纯拼参数转向拼效率。对于AI开发者和企业决策者来说,GPT-5.6意味着可以用更少预算获得更高性能,尤其适合那些被推理成本挡在门外的长上下文或Agent场景。OpenAI这一步,可能重新定义‘前沿’的标准。
91
精选LFM2.5-Encoder:面向CPU快速长上下文推理的新模型
这篇博文让我眼前一亮,因为它直接解决了大模型在CPU上跑长上下文的痛点。对于没有高端GPU的团队或个人开发者,LFM2.5-Encoder系列提供了可立即使用的开源方案。尤其推荐给做RAG、文档搜索或代码分析的朋友——现在用普通服务器就能处理百万级token的文档了。
91
精选GPT-Red:OpenAI通过自我对弈实现AI红队自动化,提升模型鲁棒性
GPT-Red 是红队测试从人工到自动化的里程碑,特别适合安全工程师和对齐研究者关注。它直接降低了测试成本,但也引发了对“自动攻击”本身的伦理讨论——值得所有关注AI治理的人深入思考。
91
精选OpenAI推出GPT-5.5生物漏洞赏金计划
这个计划值得关注,因为它首次将AI漏洞赏金制度拓展到生物安全领域,不仅为安全社区提供了新的研究方向,也为AI风险治理提供了实际演练场。对模型安全研究者、生物安全专家以及关心AI双重用途的从业者尤其重要。
91
精选vLLM推出原生速度Transformers建模后端,大幅提升推理性能
这项更新对于AI工程团队非常关键:无需格式转换意味着能更快地迭代模型,而2-5倍的速度提升直接降低GPU成本。如果你正在做LLM在线服务或者批量推理,这几乎是必读的技术更新。
90
精选Google DeepMind 发布手语转文本模型 SL2T,助力聋人用户
这则消息的意义不仅在于技术突破,更在于AI开始真正关注边缘群体的需求。对开发者而言,SL2T的架构思路和技术路径值得深入研究;对无障碍倡导者来说,这是推动行业标准的重要案例。

