If your supplier portal needs a familiar login, Nod’s separate browser is a deliberate trade-off. Nod is designed to do personal tasks in its own local sandbox, but it does not inherit your everyday browser’s tabs, cookies, or saved passwords. And if the laptop sleeps, scheduled jobs stop. For a monthly invoice run, the real choice is between connecting the supplier account to Nod and keeping its host awake, or using an agent that explicitly supports a browser session you already trust.
The n8n launch post describes Nod as a separate app with its own browser; Nod’s browser docs confirm the session boundary.
One commenter in a Reddit discussion about Nod put the uptime concern plainly: “scheduled jobs on a laptop fail exactly when u close it, silently.” That is one person’s concern, not evidence that Nod has failed a particular invoice task. It does point to a practical question worth answering before you schedule one.
Key takeaways
Nod is a standalone personal agent from n8n Labs. Its browser runs in Nod’s own sandbox on the computer running Nod.
Nod’s browser does not reuse your regular browser’s cookies or tabs. You connect accounts or save logins in Nod instead.
Nod can schedule repeat jobs, but the checked n8n launch post says it stops when the laptop sleeps.
“Local” describes where Nod’s app and browser run. The model provider still receives the data needed for a task, according to n8n.
Pick the tool by login requirements and host uptime. A job that can wait until morning may not need a server; a job with a strict deadline does.
Nod and an existing signed-in browser at a glance
| Need | Nod’s isolated browser | Agent connected to an existing browser | What to verify |
|---|---|---|---|
| Keep personal and automation tabs separate | Fits by design; Nod uses its own browser | Depends on the connector and selected profile | Which browser and profile will the agent control? |
| Use an established supplier login | Connect the account or save the login in Nod | May fit if the connector explicitly supports that signed-in profile | Confirm the domain, account, and current signed-in state before the task |
| Run monthly without a prompt | Nod supports scheduled jobs | Varies by product; do not assume a browser connection includes scheduling | Does it run while the host sleeps, and does it report missed runs? |
| Avoid a separate agent browser sign-in | No; Nod’s browser is separate from the user’s browser | Potentially, if session reuse is documented and enabled | Never copy cookies or credentials into a prompt |
| Keep data on your own machine | Nod says its sandbox, memory, and saved logins stay on the Nod machine; task data needed by the model goes to its provider | Depends on the browser tool and model route | Read where browser state, task content, and credentials go |
That table separates three questions people often collapse into one: which login is available, where the browser runs, and whether the computer is awake when the schedule fires. A local agent can still rely on a remote model, and a connected browser can still be isolated to a particular profile. For a wider comparison, see local and cloud browser agents.
What Nod’s browser changes
n8n describes Nod as a standalone research preview, not a new screen inside the n8n workflow editor. You install the app, connect your accounts, and give it a personal job. Nod opens its own browser when a task needs a website. Its browser documentation says it does not share your regular browser’s tabs, cookies, or saved passwords.
That separation helps keep a task away from your open work tabs. It also means a login already active in your normal browser is not automatically available to Nod. You may need to connect the account, save a login in Nod’s Vault, or take over the browser when the task pauses for you. The exact login path depends on the site. Passkeys and approvals on another device can require a human step.
If you are comparing an agent connection to the browser you already use, start with how browser agents connect to existing tabs and how to reuse a login session safely. The main thing to confirm is not merely that the browser is “local.” Confirm which profile the agent can reach and whether the portal recognizes its session.
A monthly invoice job has two failure points
n8n uses a closely related example in its launch post: signing in to supplier portals each month, downloading invoices, and filing them for an accountant. Turn that description into a short checklist before asking any agent to run it:
Confirm the portal account. Open the supplier’s real domain and verify the intended company account. A saved login is not proof that the right workspace opened.
Set the file destination. Decide the folder and naming rule. Check the downloaded file’s name, date, supplier, and amount before sharing it.
Choose the run time. Nod can schedule the task, but the computer must be available. A recurring job is not reliable if the laptop is routinely closed.
Keep the action bounded. Ask for the invoice download and filing. Do not include payment, subscription changes, or sending the invoice unless you separately approve those actions.
Verify the receipt. Check that the file exists and belongs to the intended billing period. If the portal challenged the sign-in, require Nod to pause for you.
The workflow can be “monthly” and still not need a 24/7 computer. A comment in the same Reddit thread suggested that an invoice job might simply run the next time the user opens the laptop. That is a reasonable requirement if an invoice can be a day late. It is not a Nod feature guarantee: n8n’s checked announcement says sleep stops work and does not promise that missed jobs catch up.
Laptop sleep is an availability issue, not a browser issue
The official launch post lists an always-on Mac mini or the user’s own server as ways to keep Nod running. It describes hosted operation as a roadmap item, not a current Nod hosting option. So an invoice task has a simple schedule constraint:
Nod can run at scheduled time = Nod host is awake + network is available + supplier login worksAn always-on machine reduces the first risk; it does not eliminate reboots, login screens, network outages, expired sessions, or portal changes. In the Reddit discussion, another commenter described an always-on Mac getting stuck after an update, leaving jobs unnoticed for eight days. That anecdote is about a different setup, but it makes the operational gap clear: a dedicated computer is not the same as a confirmed job monitor.
If your deadline is strict, require a visible completion log and an alert when a run does not finish. If the deadline is flexible, a check-on-wake rule may be enough. The source does not establish that Nod automatically replays a missed schedule, so verify its current behavior before relying on that.
A practical route for bounded browser work: Tabbit Browser
Some supplier portals are already signed in within a browser you manage. For one-off or user-started browser work, Tabbit Browser can be a separate route if your agent connector explicitly supports the chosen local browser profile. This is a browser-session workflow, not a claim that Tabbit provides Nod’s scheduled recurring jobs.
The safe first step is to open the supplier site yourself, check the account and page, then give the agent a narrow task. Before it downloads anything, verify the active domain and folder. Before it submits or changes something, stop and review the action. The guide to testing a browser agent setup walks through harmless checks first. For Tabbit’s local task ownership and completion receipts, see the Tabbit CLI tutorial.

This screenshot shows a Tabbit browser task. It is a separate example, not a Nod screen or an invoice download.
Use the Codex browser login checklist to verify the account and session; choose between Browser MCP and CLI based on the connector you actually have. A browser connection can read or operate pages only within its granted access. It should not be treated as permission to send, pay, or modify an account. Review the browser agent security risks before granting access to a billing portal.
Which option fits your invoice task?
| Your constraint | Better starting point | Why | Check before relying on it |
|---|---|---|---|
| You want separate automation logins and can keep a host awake | Nod | Its own sandbox and scheduled jobs are part of the product description | Connect the right supplier account; confirm the host is available at run time |
| The supplier account is already authenticated in a supported local browser | Existing-session agent | It may avoid a second sign-in if session reuse is supported | Verify selected profile, account, and permissions; do not assume every connector can reuse it |
| The job is monthly and can run a day late | Nod may fit without a dedicated server | You can check it when you next use the computer, if the product reports status clearly | Confirm whether the missed job is skipped or caught up; Nod’s announcement does not guarantee replay |
| The invoice must arrive before a fixed cutoff | Use a monitored host or a proven service with alerts | Sleep, restarts, and login challenges can interrupt a laptop schedule | Test missed-run alerting and recovery with a harmless task first |
| The portal requires a passkey or frequent human approval | A human-controlled session may be simpler | A separate browser can need another sign-in or a takeover | Keep the approval step with the account owner |
Verdict
Nod makes sense when the goal is a personal agent with its own browser, connected accounts, and recurring jobs, and you can keep its computer available. Its separate browser is useful for isolation, but it will not borrow your everyday browser’s login state. Its sleep limitation also matters more than the word “local”: if the laptop is closed at run time, the task stops.
Choose an existing-session browser workflow when the supplier portal depends on a session you already maintain and your agent has an explicit, documented way to use it. Choose Nod when you prefer a dedicated agent environment and can handle its sign-in and uptime requirements. For a monthly invoice that can wait, check whether Nod skipped or completed the run when you next open the app. Do not treat the task as done until the invoice file is present and verified.
FAQ
Is Nod a browser extension or a standalone app?
Nod is a standalone personal-agent app from n8n Labs, separate from n8n workflows. Its browser runs inside Nod’s own sandbox rather than as an extension in your everyday browser.
Can Nod use my existing browser cookies?
Nod’s browser documentation says its browser does not share your own browser’s tabs, cookies, or saved passwords. You can connect an account or save a login in Nod’s Vault, then verify that the task is using the right account.
What happens to Nod jobs when the laptop sleeps?
The launch documentation says Nod stops when its laptop sleeps. An always-on Mac mini or a server can keep it available, but a hosted version was only on the roadmap on the date checked.
Can a monthly invoice job catch up when my laptop wakes?
The checked Nod announcement says scheduled work stops while the laptop sleeps; it does not promise a catch-up queue after wake. If a delayed invoice download is acceptable, verify the job’s next run and completion status instead of assuming it ran.
Is Nod free if its model use costs money?
Nod is described as free and open source, but you pay the selected model provider for usage unless you run a supported local model. ‘Free app’ does not mean every completed task has zero cost.