This page explains the words you'll meet in these docs. Select a term to read the page that covers it.
| Term |
What it means |
| Conversation |
Your one ongoing chat with nod. The app, Telegram and WhatsApp all show the same conversation, which engineering pages call the thread. |
| Task |
A piece of work nod is doing for you. The Tasks page shows each one with its status, such as working or needs you. |
| Turn |
One run of nod's work, started by your message, a schedule, a background check or your answer to a question. Your chat runs one turn at a time, while scheduled runs and background checks run alongside it. |
| Schedule |
Work that runs at a set time or on repeat, such as every Friday at 5 pm. You set one up by asking nod in plain words. |
| Background check |
Work nod starts on its own when something happens in a connected app, such as a new email, once you've told nod what's worth interrupting you for. Until then, nod starts no run. It reads, drafts and does only what you told it to do on its own. Anything else waits for you. |
| Memory |
What nod remembers about you from what you tell it. You can see and edit it in Settings → Memory. |
| Skill |
A built-in guide for one kind of work, such as travel, research or spreadsheets, or a learned skill nod wrote after doing a task. nod reads the one that fits the task. |
| Term |
What it means |
| Workspace |
nod's private Linux computer, where it runs commands and keeps files. It never receives your model provider keys. |
| Browser |
nod's own web browser, separate from yours and from the workspace. |
| Browser handoff |
When a website needs you, nod sends an Open browser link to a live view of its browser. You take over, then select Done to hand it back. |
| Term |
What it means |
| Model connection |
How nod reaches a model: an OpenAI, Anthropic or OpenRouter API key, a ChatGPT or OpenRouter account, or a local model server. A paid provider bills you for use. |
| Connected app |
An account nod can use for you, such as Gmail, Calendar or Slack. |
| Composio |
The service nod uses to connect many apps for you. Managed connections use an allowed Google account; you can also use a personal key. |
| MCP |
Model Context Protocol, a standard way for an app to offer tools to an assistant. Notion and Linear connect through their own MCP servers. |
| Channel |
Another place to chat with nod besides the app: Telegram or WhatsApp. |
| Term |
What it means |
| Trust check |
The server check that runs before every connected app action. It decides whether the action runs now or waits for you. |
| Approval |
nod's yes or no question about one exact action. If you reply yes, the action runs once. |
| Standing instruction |
What you told nod to do on its own when something arrives, such as "whenever Ana sends an invoice, forward it to accounting". Background work does it without asking. You see and change it in Trust. |
| Vault |
nod's encrypted store for your saved logins, cards and browser sessions. The model never sees the saved values. |
| Saved login |
A website username and password in Vault. nod enters it privately, and only on that exact website. |
| Saved browser session |
A signed-in browser profile that nod can reuse on the websites you allow. |
| Private form |
A secure form where you enter a password, code or card for a task. What you type goes to the website, not to the model. |
| Uncertain outcome |
An approved action that was interrupted, so nod can't tell if it happened. nod checks the result instead of running it again. |
| Term |
What it means |
| Owner access key |
The secret that opens a source install of nod. The access link nod prints when it starts saves it in your browser. |
