Saved browser sessions
A saved browser session keeps a website signed in inside nod's private browser, so later tasks can reuse it. Use one for sign-ins a saved login can't handle, such as a magic link or a code on your phone.
Save a session
Section titled “Save a session”- In Trust → Logins and cards, select Add, then Website session.
- Enter the Website address and, if you like, an Account name. Select Continue in chat.
- nod opens the website in a new private browser profile. Sign in through the secure form, or take over the browser yourself.
- nod saves the session once it sees you're signed in.
You can also ask nod in chat to connect to a website and save the session.
Use a session
Section titled “Use a session”When a task needs the website, nod opens the saved profile. It's the same permission check as a saved login: the server checks that your task needs this website and account, or nod asks "Use your saved session on example.com?". The check also considers the website the saved session belongs to, not only the page being opened; if a task needs a different site but not the saved-session website, nod asks you first and shows both.
Opening a profile doesn't prove it's still signed in, so nod checks the page. If opening it lands on another website, such as a sign-in service, Vault shows Sign-in needed and a Sign in again button.
A session opens in one browser at a time. While you're still signing in to it in the chat, other tasks can't open it, and they visit public pages without it.
When the browser stays signed in
Section titled “When the browser stays signed in”| Situation | What happens |
|---|---|
| The chat | Its browser stays signed in. Each new sign-in or saved-session use is checked again |
| A scheduled run, background work or a subagent | Starts in its own fresh browser, signed out. It signs in again with a saved login or session, checked as usual; background work is checked against your standing instruction |
Sign out
Section titled “Sign out”Open the session in Trust → Logins and cards and select Sign out. This deletes the saved profile. If a task is using it, stop the task first.
Deleting a saved login keeps its browser session. The session remains available in Trust so you can sign out separately.
Passkeys and manual sign-in
Section titled “Passkeys and manual sign-in”Passkeys are turned off in nod's browser, because your passkeys live on your own devices. A passkey request fails right away, so use another sign-in method. For a magic link or any step nod can't finish, nod asks you to take over its browser. See nod's browser.
Saved session or saved login?
Section titled “Saved session or saved login?”| Saved login | Saved session | |
|---|---|---|
| What's stored | Username and password, encrypted by Vault | The browser profile: cookies and site storage |
| How you add it | Add → Login, an import or the private form | Sign in once in nod's browser |
| How nod uses it | The server types the values into the fields nod picks | nod opens the signed-in profile |
| Where it works | Fields on the login's exact origin | Any public website, never your local network |
| Best for | Username and password sign-in | Sign-ins you do by hand, such as magic links |
Like the rest of nod's browser, a saved profile reaches only public addresses: never your computer, your local network or other containers.
Where this is enforced
Section titled “Where this is enforced”src/server/browser-connections.ts (sessions) · src/server/vault-access.ts (permission and sign-out for background work) · src/providers/agent-browser/network.ts (public addresses only)