Nod can provide a single assistant experience across laptops, desktops, and hosted machines, but only when each client connects to the same Nod server. In that setup, the server is the home for the assistant and its shared state. Separate local installations, or clients attached to different servers, do not automatically combine their memory.
The distinction matters for anyone expecting an AI assistant to retain context while they move between devices. Nod's official desktop installation documentation instructs users who already have a Nod server to select Connect to a server during setup. Once connected, clients reach the same assistant and connected accounts rather than creating separate assistant environments on every computer.
A common Nod server creates one shared assistant
Nod's server connection is not a file-sync feature between desktop apps. It is a central-assistant model: the server stores the assistant, channels, and model credentials, and every client connected to that server accesses that same server-backed environment.
This gives a user continuity that separate installations cannot provide. A conversation or workflow context handled through the shared assistant can be continued from another connected client. The server can also keep the assistant running after a user quits the desktop app, allowing work to continue through another Nod client.
The important boundary is the server address. Two devices share the assistant only when both are connected to the same Nod server. A laptop using its own local setup and a desktop connected to a self-hosted server are not using one shared memory space simply because both run Nod.
| Setup | Assistant and memory outcome | What users should expect |
|---|---|---|
| Separate local Nod installations | Separate assistant environments | Memory does not automatically synchronize between installations. |
| Multiple clients connected to one Nod server | One server-backed assistant | Connected clients access the same assistant, channels, and connected accounts. |
| Existing desktop app connected to a server | Shared server assistant, separate existing local data | Local conversations and saved accounts are not copied to the server. |
What does not move from a desktop app
Nod's Mac mini hosting guidance makes the limitation explicit: desktop app data and the self-hosting stack have separate data. Connecting a desktop client to a server does not transfer its existing local conversation history or saved accounts into the server environment.
That means a switch to a shared server should be treated as a connection to a different, centralized assistant context, not as a migration of every local record. The server is authoritative for the shared assistant after clients connect, while pre-existing local desktop data remains on the device where it was created.
Why shared context matters for multi-device work
For a business owner or team member, a common server can make Nod more useful as an ongoing operational assistant. Someone might begin work on a laptop, later use a desktop client, and continue with the same assistant context rather than re-explaining the task. The value is continuity, not merely access from another screen.
A shared server can be especially relevant where the assistant is connected to recurring work. The verified documentation indicates that connected clients reach the same assistant and channels, while the supplied research also identifies shared schedules as part of the server-backed workflow context. In practice, this can support a more consistent working environment across devices.
Before relying on that continuity, teams should establish a simple operating rule:
- Connect every intended client to the same Nod server.
- Treat the server-backed assistant as the shared working context.
- Do not expect data from an older local desktop assistant to appear on the server automatically.
- Keep private or disconnected local assistants separate unless cross-device access is intentionally required.
This approach also helps avoid a common source of confusion. If an assistant appears to have forgotten a conversation after a device change, the issue may not be memory quality. The user may be connected to a different Nod environment, such as a standalone local installation rather than the shared server.
For businesses, the practical benefit is a clearer division between personal experimentation and persistent operational workflows. A local setup can remain isolated for private work, while a shared server can provide continuity for the devices that need to access one assistant. The documentation supports cross-device access, but it does not indicate that Nod merges data from independent desktop installations.
If your team wants persistent AI context to support repeatable work rather than isolated chats, Scalevise can help design the connection between assistants, workflows, and business tools. Our n8n automation setup services focus on practical workflow implementation, including connected systems and dependable operational processes. Request an n8n automation setup consultation.
Frequently Asked Questions
Do two separate Nod installations share memory automatically?
No. Separate local installations, or clients connected to different Nod servers, maintain separate assistant environments. To access one shared assistant, both clients must connect to the same Nod server.
What does a Nod server store for connected clients?
According to Nod's desktop documentation, the server stores the assistant, channels, and model credentials. Clients connected to that server access the same assistant and connected accounts.
Does connecting a desktop app to a Nod server upload existing local conversations?
No. Nod states that connecting the desktop app to a self-hosted server does not copy the app's local conversation history or saved accounts to the server.
Can Nod work continue after the desktop app is closed?
Yes. Nod's Mac mini hosting documentation says the server keeps the assistant running after the app is quit, so a Nod client can connect and continue working.
Conclusion
Nod's cross-device continuity depends on architecture rather than automatic synchronization. A common Nod server gives connected clients access to one server-backed assistant and its shared context, while local desktop data remains separate. Users who need consistent assistant memory across devices should connect each client to the same server and understand that existing local data is not migrated automatically.
