做本地AI部署或隐私敏感应用的开发者,OpenJarvis 提供了一种不牺牲性能就能在设备上运行个人AI的方案,值得深入研究其架构和优化方法。
OpenJarvis 是一种新的个人AI系统架构,旨在解决现有AI堆栈(如OpenClaw、Hermes Agent)严重依赖云端模型的问题。当前,将本地模型直接替换云端模型会导致准确率下降25-39个百分点。OpenJarvis 将个人AI系统分解为五个可独立优化的原语(智能、引擎、智能体、工具与记忆、学习),并引入LLM引导的规范搜索,让云端模型在搜索时提出编辑建议,但只接受不降低性能的修改,最终推理完全在设备上运行。实验表明,OpenJarvis 在8个基准测试中的4个上匹配或超越云端准确率,平均仅落后3.2个百分点,同时将API成本降低约800倍,端到端延迟降低4倍。
OpenJarvis: Personal AI, On Personal Devices
Personal AI stacks, like OpenClaw and Hermes Agent, are becoming central to daily work, yet they route nearly every query (often over sensitive local data) to cloud-hosted frontier models. Replacing frontier models with local models inside existing stacks does not work: swapping Claude Opus 4.6 for Qwen3.5-9B drops accuracy by 25-39 pp across personal AI tasks like PinchBench and GAIA. Existing stacks bundle agentic prompts, tool descriptions, memory configuration, and runtime settings around a specific cloud model. Only the prompts can be tuned, and state-of-the-art prompt optimizers close just 5 pp of the local-cloud gap on their own. This motivates a decomposed personal AI stack: one that exposes individual primitives which can be optimized individually or jointly to close the local-cloud gap. We present OpenJarvis, an architecture that represents a personal AI system as a typed spec over five primitives: Intelligence, Engine, Agents, Tools & Memory, and Learning. Each primitive is an independently editable field, making the stack end-to-end optimizable and measurable against accuracy, cost, and latency. Towards closing the local-cloud gap without surrendering local-model properties, OpenJarvis introduces LLM-guided spec search, a local-cloud collaboration in which frontier cloud models propose edits across the spec at search time, only non-regressing edits are accepted, and the resulting spec runs entirely on-device at inference time. With LLM-guided spec search, on-device specs match or exceed cloud accuracy on 4 of 8 benchmarks and land within 3.2 pp of the best cloud baseline on average. They also reduce marginal API cost by ~800x and end-to-end latency by 4x.
- shao__meng05-17 00:48原文