Hacker News 熱門精选66

Show HN:CUA-S1 – 用于计算机使用的 System One Model

Show HN: CUA-S1 – A System One Model for Computer Use

· 24天前
跳到正文

精选理由

展示小模型替代通用LLM处理表单的可行路径

AI 摘要

Hello HN!我们是来自 Cua 的 Dillon 和 Francesco。 我们一直在想,有多少计算机使用任务实际上需要一个完整的通用 LLM(例如 gpt-6-astra、claude-opus-5 等)来思考它们的所有决策和步骤。有些任务需要思考计划、探索不同路径、从失败中恢复。另一些任务则是做出局部决策的问题,比如这个值应该填进这个框,或者我是否应该勾选这个复选框,或者这个元素应该被忽略。 我们想知道,如果训练一个小模型只做这类决策,能走多远。 我们的灵感来自 Typesafe 的 Jev 及其 System One Model 的框架。这是在致敬 Daniel Kahneman 所描述的二分法:快速、自动、直觉式思考(系统 1)与缓慢、分析式思考(系统 2)。 对我们来说,有趣的问题是:如果给模型一个包含当前上下文的接口,以及一组可能的选择,并要求它为每个选择返回一个概率,会发生什么?这类模型不像大多数 LLM 那样逐 token 生成输出,而是对你给它的选项打分;你可以检查、信任并使用这些分数来驱动你的应用行为。 CUA-S1 是我们面向计算机使用场景中狭窄、专用决策模型的答案。我们的第一个发布版本是 CUA-S1-FORMS。我们基于 jevlike 中的想法和代码构建了它,然后训练了第二个模型,专门处理表单交互。它有 706k 个参数,原始 checkpoint 为 2.8 MB。 第一次训练迭代在合成数据上耗时不到 30 分钟。给定一组从文档中提取的结构化元素和值,它会为每个元素预测是否使用给定值、CHECK、CLICK 或 SKIP。它不会为文本字段预测新值,也不会考虑截图。元素决策会一起打分,你的代码可以对操作进行排序,而 Cua Driver 会逐一执行它们。 该专用模型与托管版 Jev 在我们的表单任务上的首次评估结果: - 对整个决策集:99.7% 正确 vs 83.6%。 - 对需要执行操作的步骤子集:100% 正确 vs 96%。 - 对只是保持已填写字段不变的步骤子集:100% 正确 vs 74%。 该专用模型是专门针对这个任务和约定(对已经填好的框直接按 skip)训练的,而托管版 Jev 并未为此进行微调,因此这是一次关于限定范围专业化的实验。 我们测得在本地为一个表单打分需要 7-9 ms,而调用托管版 Jev 每次需要 260-280 ms(包括网络延迟),不过这些样本测量的是不同内容,并不是端到端的表单完成时间。 我们在这里感兴趣的是介于脆弱脚本和通用 agent 循环之间的空间。表单字段的内容和布局变化足够大,以至于脚本会变得难以维护,但可用决策集合可以保持狭窄且边界清晰。我们想探索这样一种可能性:通用 agent 遇到新颖情况,并把已被充分理解的决策交给这样的专用模型处理。 这是我们正在研究的方向。当前发布版本仅用于表单。我们已将合成数据生成、训练、评估和 Driver 集成以 MIT 许可证开源在 libs/cua-s1 下。 欢迎评论!尤其是如果你正在构建计算机使用 agent,并且遇到过某种反复出现的决策:它太多变以至于难以脚本化,但又太狭窄以至于不值得调用另一个 LLM。 评论 URL: https://news.ycombinator.com/item?id=49767564 点数:4 评论数:0

正文

Cua logo

Give AI agents computers they can use.
Cua provides open-source desktop automation, isolated cloud desktops, local macOS VMs, specialist decision models, and benchmarks for evaluating computer-use agents.

Try Cua Fleets now at run.cua.ai

cua.ai Discord Twitter Documentation
trycua%2Fcua | Trendshift

Choose your path

Bring your own agent and model, or explore CUA-S1 for specialized decisions. Cua provides the computer and automation tools. Computer-Use 2.0 describes an agent moving between code, APIs, and graphical interfaces within the same task.

See Cua Driver in action

Two Cua Driver sessions select cells in LibreOffice Calc and objects in Inkscape on an Omarchy desktop while a terminal stays in the foreground. Watch the 50-second demo, then explore Omarchy on Fleet.

recording.mp4

Cua Fleets

Provision isolated cloud desktops at run.cua.ai. A Fleet maintains sandbox capacity; your code claims a desktop from a pool and uses the Sandbox SDK to run commands, capture screenshots, and interact with apps inside it.

Your first result: provision a Linux desktop, run uname -a, save a screenshot, and delete the cloud resources. The tutorial covers Fleet credentials, dependencies, and cleanup. Pools can retain paid capacity after a claim ends, so follow its cleanup steps.

Local sandboxes and Fleets share the Sandbox SDK, but credentials, images, operations, and runtime requirements differ. Use the runtime support reference to choose an environment. For your own hardware, see Manage local sandbox lifecycle.

Your first Cloud Fleet | Fleet overview | Sandbox SDK reference


Cua Driver

Give your agent tools to inspect and operate native desktop apps and browsers on macOS, Windows, and Linux. Connect through the CLI, MCP, or typed SDKs. Background delivery lets agents work without moving your pointer or taking focus when the app and platform support it; see platform support for the boundaries.

macOS / Linux

/bin/bash -c "$(curl -fsSL https://cua.ai/driver/install.sh)"

Windows (PowerShell)

irm https://cua.ai/driver/install.ps1 | iex

Your first result: connect your agent, ask it to compute 6 × 7 in Calculator, and have it verify that the app displays 42. The tutorial covers platform setup, permissions, and agent connection.

Drive your first app | Installation | CLI Reference

Using Claude Code, Codex, Cursor, OpenClaw, or another agent? Find your integration. Source documentation and architecture notes live in libs/cua-driver/README.md.


CUA-S1

CUA-S1 is our family of small, specialized System 1 models for computer use. We use "System 1" as an engineering analogy for fast, bounded decisions, such as choosing which value belongs in a field or whether to leave an element alone. It is not a strict classification of model architectures or a replacement for a general-purpose agent's planning and reasoning.

The first research profile focuses on forms: scoring decisions from structured interface elements and document values rather than generating a response token by token. Application code orders the actions, and the optional Cua Driver integration handles execution with explicit action boundaries.

The project includes Python model code, synthetic-data generation, training, and evaluation. The GitHub component is an early, source-only research release; model weights are hosted separately on Hugging Face. The source is MIT-licensed. Check each model and dataset card for its scope, limitations, and artifact-specific license.

Explore CUA-S1 | Model card | Safety and deployment guidance

CUA-S1-FORMS on Hugging Face: Model weights | Dataset


Lume

Create and manage local macOS and Linux VMs on Apple Silicon using Apple's Virtualization.Framework.

/bin/bash -c "$(curl -fsSL https://cua.ai/lume/install.sh)"

Your first result: create a vanilla macOS Tahoe VM from an Apple restore image, start it, and connect over SSH. The tutorial uses the Lume CLI directly and explains the unattended setup defaults.

Create your first Lume VM | Installation | CLI reference


Cua Bench

Build computer-use tasks, evaluate agents, and export trajectories for training. Start with a simulated task that requires no VM, Docker, or model API key.

With Python 3.12 or 3.13 and uv installed:

uv tool install 'cua-bench[browser]'
uv tool run --from 'cua-bench[browser]' playwright install chromium

Your first result: create a small task, run its reference solution, and verify that its evaluator reports a reward of 1.0. Then try the same task yourself.

Build your first task | What is Cua-Bench? | CLI reference | Partner with us


Resources

  • Documentation — Guides, examples, and API reference
  • Blog — Tutorials, updates, and research
  • Discord — Community support and discussions
  • GitHub Issues — Bug reports and feature requests
  • Security — Private vulnerability reporting

Citation

If Cua supports your research, please cite the software:

@software{cua2025,
  author  = {{Cua AI, Inc.}},
  title   = {Cua},
  year    = {2025},
  url     = {https://github.com/trycua/cua},
  license = {MIT}
}

For reproducibility, include the Cua release or commit used in your experiments. Citation metadata is also available in CITATION.cff.

Contributing

We welcome contributions! See our Contributing Guidelines for details.

License

MIT License — see LICENSE for details.

Third-party components have their own licenses:

  • Kasm (MIT)
  • OmniParser (CC-BY-4.0)
  • Optional cua-agent[omni] includes ultralytics (AGPL-3.0)

Trademarks

Apple, macOS, Ubuntu, Canonical, and Microsoft are trademarks of their respective owners. This project is not affiliated with or endorsed by these companies.


Sponsors

查看原文(Hacker News 熱門)