CUA-S1 – A System One Model for Computer Use

Hello HN! We're Dillon and Francesco from Cua.We were wondering how many computer use tasks actually need a full general purpose LLM (e.g. gpt-6-astra, claude-opus-5 etc.) to think through all their decisions and steps. Some tasks require thinking about a plan, exploring different paths, recovering from failure. Other tasks are a question of making local decisions, like this value should go in this box, or should I check this box, or this element should be ignored.We wondered how far we could go with a small model trained to only make these kinds of decisions.Our inspiration was Typesafe's Jev and its System One Model framing. This is a nod to the dichotomy between thinking quickly, automatically, and intuitively (system 1) vs. thinking slowly, analytically (system 2), as described by Daniel Kahneman.The interesting question for us was: what happens if you give a model an interface of current context, and a set of possible choices, and you ask it to return a probability for each choice? This kind of model does not generate output token by token like most LLMs do, but rather scores the options you give it, which you can check, trust, and use to drive your app's behavior.CUA-S1 is our answer for narrow, specialized decision models for computer use. Our first release is CUA-S1-FORMS. We built this from ideas and code in jevlike, and then trained a second model just to handle form interactions. It has 706k parameters, and the original checkpoint is 2.8 MB.The first training iteration took less than 30 minutes on synthetic data. Given a set of structured elements and values extracted from a document, it predicts whether to use the given value, CHECK, CLICK, or SKIP for each element. It does not predict new values for text fields, and does not consider screenshots. Element decisions are scored together, and your code can order the actions, and Cua Driver will execute them one at a time.A first evaluation of this specialist vs. hosted Jev on our form task:-

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

A 2.8 MB specialized model that scores form field decisions instead of generating tokens, targeting cost and speed gains in RPA and automation workflows.

The pain

Current computer use automation relies on large LLMs (Claude, GPT-4) for every decision, including trivial ones like whether to fill a text field or click a checkbox. This is slow, expensive, and wasteful for tasks that need local pattern matching, not reasoning.

The gap

No existing tool separates high-cognition decisions (plan a multi-step workflow) from low-cognition decisions (should this field be filled). General LLMs do both. Specialized routing models do not exist at production scale.

Build angle

Train small, task-specific models on synthetic data to handle narrow decision types. Start with forms because they are structured, measurable, and common in enterprise automation. Prove 10x cost and latency gains, then expand to other UI patterns.

Strengths

  • Founders understand the efficiency frontier: most computer use tasks do not need reasoning, just pattern matching.
  • Execution is tight: 706k parameters, 2.8 MB, trained in under 30 minutes on synthetic data.
  • Measurable claim: faster and cheaper than Jev on form tasks, with concrete evaluation methodology.
  • Narrow scope reduces risk: forms are well-defined, labeled data is easy to generate, success is easy to measure.
  • Built on proven ideas: Typesafe's Jev and System One framing provide intellectual foundation.

Risks

  • Market size unclear: how many customers actually run enough form automation to justify a new tool versus using Claude at scale.
  • Commoditization risk: if Claude or GPT-5 adds routing logic or becomes cheap enough, the cost advantage disappears.
  • Customer acquisition unknown: no evidence of inbound demand, partnerships, or sales channel.
  • Generalization unproven: forms are easy, but expanding to other UI patterns (tables, dropdowns, dynamic content) may require retraining for each task.
  • Competitive response: Anthropic, OpenAI, or Typesafe could add this capability to their own products within months.
  • Adoption friction: customers must integrate a new model into their stack and trust its decisions on unfamiliar tasks.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “CUA-S1 – A System One Model for Computer Use”.

Open FlyBot