Yutori introduced Navigator n2 on August 26, 2026, describing a 27B computer-use model that operates across desktop applications, browsers, and command-line tools. The change extends its earlier browser-focused Navigator line into full desktop environments.
The announcement lists input pricing of $0.50 per million tokens, cached input at $0.05, and output at $4. The API documentation separates product interfaces. A model’s computer-use capability should not be confused with unrestricted hosted access to a person’s accounts.
Desktop reach makes the task boundary more important
A desktop agent can move between a file, an application, and a browser. That can reduce integration effort when a workflow lacks a suitable API. It also creates more ways for an agent to interact with information unrelated to its task.
Start with a dedicated environment and the smallest set of accounts and files required. Define which changes are permitted and which require review. Permission to inspect a spreadsheet should not automatically grant permission to send it to an outside recipient or change the original data.
Benchmark results depend on the environment
Yutori reports results across desktop evaluations and presents a cost-performance argument. These are useful evidence about the evaluated system, with the benchmark and score type preserved. A partial-credit metric should not be rewritten as a percentage of fully completed business tasks.
For an internal trial, use a reproducible desktop state and specific final checks. Confirm the final file contents or application record directly. Screenshots and the agent’s narrative can support review, but should not be the only proof that a mutation succeeded.
Model access and browser infrastructure are different products
Yutori offers several interfaces around models and agents. Identify whether the chosen service supplies only a model response or also runs the environment, authentication, and task orchestration. Those differences affect cost and who owns a failure.
Before using a hosted environment, check credential storage, session lifetime, data handling, and how a human can inspect or resume work. A complete workflow needs a recovery path when a page changes, a session expires, or an application asks for an unexpected confirmation.
What to evaluate first
Choose a bounded task with a reversible result, such as extracting information into a new file. Then add cases with changed layouts, missing records, and conflicting inputs. Measure successful outcomes, intervention time, and total cost.
Nerova’s view is that n2 is a meaningful option for desktop-oriented automation. Its practical value comes from completing a controlled task across software boundaries while leaving inspectable evidence. Full desktop reach makes that discipline more necessary, not less.