How Nuvvi works

A calmer way to work with AI.

Nuvvi stays available on the Windows desktop, carries only the context the product is allowed to use, and keeps important boundaries visible.

Controlled beta accounts are open

Nuvvi desktop · Project workspace
Nuvvi’s desktop workspace showing project context, selected memory, and Work Awareness controls.
Project context, explicit memory, and awareness controls stay visible.

01 — Context

The moment and the long view are not the same thing.

Current Work Context

A bounded, short-lived view of the active task—assembled from permitted product signals and occasional consent-controlled observation.

Durable Memory

Inspectable project facts, decisions, tasks, and preferences that you explicitly choose to keep. No hidden memory mining.

02

02 — Manual Look

Ask Nuvvi to look once.

Select a visible application window and confirm it for each request. Nuvvi captures one transient frame, sends it for that review, and does not store it in product-controlled systems. Provider processing follows the configured provider terms.

03

03 — Work Awareness

Awareness is a mode, not a hidden permission.

It starts off and requires account-local consent. When aware, Nuvvi may occasionally review the current eligible window and keep a compact context. Pause, exclude an app, clear the context, or turn it off whenever you choose.

No continuous recording. No keystrokes or clipboard. No background repository scans.

04

04 — Project continuity

Give decisions somewhere useful to live.

Each local project keeps its current conversation, profile, and explicit memories together in an encrypted, account-isolated namespace. A folder reference remains only a label until you deliberately attach a workspace for coding help.

05

05 — Coding workflow

A handoff you can inspect before it leaves.

When you ask, Nuvvi reads bounded, relevant evidence from an attached workspace and prepares a task package. You manually copy or export it to Codex. Returned results are manually supplied and checked against current repository evidence.

Read-only inspection. Manual handoff. No autonomous executor.

06

06 — Private Mode

One control that means stop.

Private Mode overrides companion reactions, awareness, screen review, workspace inspection, and proactive suggestions. Your local projects and saved memory remain yours; ambient work pauses.

07 — Make the presence yours

Five companions. One clear contract.

Orbit is steady. Miso is curious. Flick is resourceful. Nori is observant. Pip is optimistic. Their expression changes; the product boundaries do not.

Orbit, Miso, Flick, Nori, and Pip standing together.

Explore the product story. Join the controlled beta when you are ready.

Create a free account to request manual beta approval. Active accounts can download the Windows x64 installer from the account portal.

Controlled beta accounts are open