Skip to content

FAQ

The source is available under BUSL-1.1 (the Business Source License), and each release converts to MIT four years after it ships. In practice you can read, build, and modify the code today, with the fully permissive MIT license arriving on a rolling schedule.

Very little, and it’s opt-out. There are no accounts, no login, and no third-party analytics SDKs. The only outbound signal is an anonymous telemetry ping containing your app version and OS, sent on launch and once a day — used solely to see which versions are in use. Turn it off in Settings → Privacy, or set DO_NOT_TRACK in your environment to disable it entirely. Full details are in the privacy policy.

Yes. nodeterm runs entirely on your machine — terminals, agents, projects, and the canvas all work with no network. Only features that are inherently online need a connection: checking for updates, and remote access through the relay (see Relay quota & Pro and Team access).

The desktop app ships for macOS (Apple Silicon and Intel) and Linux (x64, as a self-updating AppImage or a .deb — see Installation). For a headless box there’s also the Server Edition — the same canvas served from your server to a browser (see Server Edition) — and an iOS companion for attaching to your sessions from your phone (see Mobile companion). Windows isn’t supported yet.

No — nodeterm doesn’t sell model access or mark up tokens. Agent nodes run the real CLIs (Claude Code, Codex, Gemini, opencode) using your own subscriptions or API keys. You bring the CLIs you already have installed and logged in; nodeterm just runs and orchestrates them. See the Agents overview.

In three places, each with a clear job:

  • Live terminals run inside tmux sessions named nt-<node-id>, which outlive the app so your work survives quits — see Terminal persistence.
  • Project layout (your nodes, notes, groups) lives in a per-project .nodeterm/project.json inside the project folder, so it’s git-shareable and travels with the repo — see Projects.
  • App-level data (settings, the workspace index, scrollback snapshots) lives in nodeterm’s application-data directory.