Skip to content
Nod

Trust and Vault

Trust decides what Nod can do in your apps and on websites. Vault decides how Nod uses your saved logins and cards, and it never shows them to the model.

Nod can sign in to a website, read a report, prepare a reply and complete a checkout. The model plans that work. A separate check decides which app actions, browser steps and sign-ins can run. It sees your words and the action, never the pages or emails Nod read: for a browser step, that's the website, the control's label and what Nod typed. It asks you when your words don't cover the action. Every payment waits for your approval.

Watch a narrated overview with synthetic data. The scenes show example states from the app. The model check can make mistakes.

Our trust principlesSeven commitments, and how the server keeps them.
How Nod comparesNod next to Instinct, Meta Muse and OpenAI dots.
Security review guideData flows, threats and controls for security teams.

Two jobs, two paths

Section titled “Two jobs, two paths”
flowchart LR
  you([You]):::accent
  model[Nod plans<br/>the task]
  trust{{Trust}}:::accent
  vault{{Vault}}:::accent
  apps[Your apps]
  site[A website]

  you -- asks --> model
  model -- app action --> trust --> apps
  model -- sign in or pay --> vault --> site
  you -. approves .-> trust
  you -. approves .-> vault
  site -- result, secrets masked --> model
Trust Vault
Protects Actions in your connected apps Saved logins, verification codes and cards
Checks The action and its arguments as Nod sends them The task, the saved account and the exact website
Asks you when Your words don't cover an action beyond a read or draft Nod wants an account you haven't allowed for this task
The model sees The action and its result Account names and status, never the secret
You review it in The confirmation in chat and Usage Usage

Three rules behind everything

Section titled “Three rules behind everything”

Authority comes from you

Nod is designed so that only you give it permission, through your messages, approvals and the instructions you set, never a web page, email or file.

Secrets have their own path

The server enters saved values into the website. The model never receives them.

One use, one result

An approved action runs once. If the outcome is unclear, Nod says so. You check the result, or ask Nod to, before any new attempt.

What Nod does in common cases

Section titled “What Nod does in common cases”
You ask Nod to What happens
Read your calendar or inbox It runs.
Draft a reply It runs.
Add an event, send an email or delete files A review checks it matches your request, then it runs. If it doesn't match, Nod asks.
Email a recipient you didn't ask it to contact The review finds no permission for that recipient, so Nod asks.
Sign in to a site with a saved login Vault checks the account and website, then fills in the password privately.
Pay at a checkout You approve that one payment with your card's security code, which Nod never saves.
Do something while it reacts to a new email on its own It does what you told it to do on its own, such as forwarding Ana's invoices to accounting@acme.com, unless a rule says to ask first. Anything else waits for you unless a rule allows it. Separately, it reads your apps and can nudge you about work it prepared, without acting.

Where you see and change things

Section titled “Where you see and change things”
  • Usage in the sidebar (⌘5 in the Mac app, Ctrl+5 in the Windows or Linux app) shows what Nod did and spent: app actions, sign-ins, card uses, questions and held attempts, with the cost of each request. The sentence at the top holds your monthly limit, when a task checks in with you, the standing instruction Nod follows on its own and your rules. Select one to change it.
  • Vault (⌘6 or Ctrl+6) lists your logins, cards and saved browser sessions. Edit or remove logins and cards, and sign out of sessions.
  • Settings → Memory shows what Nod remembers about you and where it learned it.

Usage shows model costs, a $40 monthly limit, the $5 task check-in, a standing instruction, a rule to ask before paying, completed tasks and a sign-in.

In this section

Section titled “In this section”