viraj
1
Nod’s release came at a great time for me when I was exploring alternatives outside OpenWebUI that were lighter. Sharing some initial views from v 0.7.3 using Qwen3.8:27b Q4 with 64k context.
I had started to settle on Cline Desktop (with a remote SSH server for agent use) when Nod came out. I liked Nod so much that I’m spending as much time with it as I am in Cline, especially where I am looking for chat/document based outputs rather than code. It feels incredibly polished for a v0.x release - hats off!
What makes it impressive:
- It makes my local setup feel very powerful. I’d say this gives me the same output quality as frontier models for everyday chats, just a bit slower. Tool calls are also accurate and well formed.
- The docker/server support and connections/settings UI is a nice touch. In contrast,Cline requires a TUI to add MCP servers.
- The visibility and taxonomy of memory notes - ‘learned’ / ‘mentioned once’ etc.
- The docs are very good for this early a stage.
- Nod’s frequency of checking in with me before running actions is about where I’d expect and want an agent to be and a whole lot better behaved in this regard than Cline and Claude harnesses.
What I miss:
- Better support for remote/local access. The .env variable for NOD URL requires that it’s https but this means it doesn’t work in a private network with Netbird (where address are http://client.netbird.cloud). Similarly, localhost:4310 doesn’t cut it when I’m accessing Nod’s UI from another machine locally.
- Composio felt pushed. It’s not clear enough that by linking services through the default app options, you’re sending all tool call data to a third party. Direct MCP support should be a first class citizen.
- More control - e.g. bringing up the browser or file tree whenever I want. Right now the agent decides when I can see the browser and to see the file tree I have to click on a previously uploaded or generated file in the logs. Looks like 0.7.4 might improve on this.
- More logs / thinking info . Most interfaces let you see the agent’s reasoning process and tool calls more clearly.
- Multi-player mode: I want more of team using this but need a way to share selected chat outputs/artifacts between us.
All in all, super excited and impressed to see this release from n8n. Huge congrats to all those involved - I know this is just the beginning!
4 Likes
I strongly agree on more control, thinking, and logs. I would love to see more transparency on what it’s thinking.
Yeah I started using Nod in the last 24 hours. I gave it a bunch of local models to use. One of the things that could definitely be improved upon is if you could actually set different models to different modes, like fast model thinking or deep thinking for example, hypothetically. Those could be different models they could select from.
I set it up on a local server running LM Studio. I got decent results but memory-wise it’s failing really badly. Creating documentation and files is really bad. It hasn’t been successful at all.
I made a video as well but not able to upload, this is my attempt to integrate NOD with my local ai stack, including deepseek on strata as well as integating a custom voice module on NOD so i can do interactive voice chat with NOD, thanks to n8n team, i have lot to learn here, thought will share my work so far
Its great. I would love if we can have, optionality to have decision ai models, to be used natively for many scenarios like automatic model switching, status updates, and much more
In nod there is already self persisting knowledge base, having decision ai integration would optimize many things like for example, when doing any browser based tasks, there are many llm calls to understand the state, decision ai can make that functionality much efficient.