Repository navigation
NODE 0.9.9 lets you share a trail with someone, and talk it through in threads. Thank you for testing.
NODE updates itself on Windows, and on a Mac from 0.9.6 on. Copies of 0.9.5 or earlier on a Mac need this version downloaded by hand once.
What's new
- Threads in a trail. In Menu → Trail, start a thread: a question or a line of inquiry. Reply, and answer replies, like a Reddit thread. Mark a thread resolved with a short conclusion, add tags, or link the page you're on. When a keyword shows up on several pages, NODE offers to make it a thread.
- Notes on pages. Every page in the trail has Add note.
- Your name. Threads, replies and notes carry a display name. NODE asks for it the first time. You can change it in Settings → Sharing. There is no account.
- Share a trail. File → Share Trail… (or Share… in Menu → Trail) saves the trail as a
.trail.mdfile. Untick any page you don't want to send. Research reports go with it; open tabs only if you tick them. Send the file with any app: Messages, email, Telegram, Discord or AirDrop. Sign-in and payment pages, private parts of web addresses and tracking codes never go in the file. - Open a shared trail. File → Open Shared Trail…, drop the file on NODE, or on a Mac use Open With → NODE in Finder. You see who sent it and what's in it, then choose Open as New Trail or Merge into one of yours. A merge never removes anything: everyone's replies and notes stay, and NODE asks which thread status, tags and pinned keywords to keep.
- Works with AI. The trail file is plain Markdown. You can give it to an AI assistant to summarize, or to answer in a thread, and open it again in NODE.
- Thread count in the sidebar. The trail line shows how many threads the trail has.
Which file to download
Scroll down to Assets and download one file:
| Your computer | Download |
|---|---|
| Mac with an Apple chip (M1, M2, M3, M4 or later) | NODE-0.9.9-mac-arm64.dmg |
| Mac with an Intel processor | NODE-0.9.9-mac-x64.dmg |
| Windows | NODE-0.9.9-win-x64.exe |
| Linux | NODE-0.9.9-linux-x86_64.AppImage |
Not sure which Mac you have? Click the Apple menu in the top-left corner and choose About This Mac. If the line "Chip" says Apple M1, M2, M3 or M4, download the Apple chip file. If it says "Processor" with Intel, download the Intel file.
You can ignore the other files, including Source code (zip) and Source code (tar.gz). They are for developers.
Installing on a Mac
If you have 0.9.6, 0.9.7 or 0.9.8, NODE updates itself: when the update is ready it offers to restart. Otherwise:
- Open the downloaded
.dmgfile. - Drag NODE into the Applications folder, replacing the old one if you have it.
- Open NODE from Applications.
NODE is signed and checked by Apple, so it opens like any other app. Copies of 0.9.5 or earlier can't update themselves; download this version by hand once.
Installing on Windows
- If your browser warns about the download, choose Keep.
- Open the
.exefile. If you see "Windows protected your PC", click More info, then Run anyway. - Follow the installer.
Windows copies of NODE check for updates and install them by themselves.
Installing on Linux
Download the .AppImage file, make it executable (right-click → Properties → Allow executing, or chmod +x), and open it.
Known limits
- The first time NODE saves a password on a Mac, macOS may ask whether NODE can use its "Safe Storage" key in your keychain. Click Always Allow. If you are coming from 0.9.5 or earlier, it asks once more: click Always Allow again, or NODE can't read your saved passwords and API keys.
- Signing in to Google accounts opens in a separate Chrome-based window.
- Screenshots and saved pages are not in a shared trail file yet. They will come with share links.
- On Windows, NODE is not listed under "Open with" for Markdown files. Use File → Open Shared Trail…, drag the file onto NODE, or choose Open with → Choose another app and pick NODE.
- On a Mac, passkeys (Touch ID / iCloud Keychain sign-in) are turned off; sites offer password sign-in instead.
Reporting a problem
In NODE's menu bar, choose Help → Report a Problem…. NODE copies its diagnostics and opens a short bug form on GitHub. Paste them where the form asks, with what you were doing when it went wrong.