Skip to content

Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.

chore(release): v0.4.4

review8cf8debda1a5
diff --git a/docs/release-notes/v0.4.4.md b/docs/release-notes/v0.4.4.md
new file mode 100644
index 000000000..1ed0a4df2
--- /dev/null
+++ b/docs/release-notes/v0.4.4.md
@@ -0,0 +1,32 @@
+**Windows is a real target now — as an unsigned beta, and that word is doing work.** The
+session-host phase landed, so the whole core experience works there: agent sessions and their
+hooks, managed Claude and Codex accounts, native SSH (port and agent forwarding, `ProxyCommand`,
+Pageant, `ssh.exe`), live links and co-attach, the phone relay, dev tools, run configurations, the
+tray with background mode, and the session reaper and memory panel. What it does **not** have is a
+code-signing certificate, so Windows SmartScreen will warn on the installer, and the build cannot
+update itself: it checks for new versions and shows a card that links to the download, and you run
+the new installer over the old one. Your projects and settings are kept, and on 0.4.1+ your running
+sessions survive the update. Signing is the next phase.
+
+**Updates stop nagging, and Restart finally says something.** This is the part macOS users will
+notice. Clicking **Restart to update** used to look like nothing had happened while macOS staged
+the update underneath; now the button shows Preparing… and Restarting… and the canvas is saved
+before the app quits. Automatic checks download quietly — no progress card and no "You're up to
+date" flash unless you asked — a staged update is no longer re-downloaded every six hours, and a
+failed background check no longer puts up an error card. When a release carries notes, the card
+shows the first few lines. Errors that do reach you are plain sentences instead of `net::ERR_*`.
+
+**A hidden window gives its memory back.** Minimize nodeterm or send it to the tray and, after two
+minutes, its terminals release their GPU contexts and parked emulators — then come back warm when
+you return. A window merely *covered* by another app stays warm: that distinction cost a bug on
+macOS and is now explicit. On Windows, terminal scrollback is also capped at 10,000 lines in the
+session host, which was the single biggest memory win there.
+
+**Keep-awake now respects your battery and your lap.** While a local agent works, nodeterm holds
+off idle sleep — but below 5% battery it lets go, and re-holds when you plug in. On a Mac, a
+`critical` thermal state releases it too, latched until things cool down so it cannot flap. An
+unreadable battery level changes nothing, so a broken reader can never switch the feature off
+silently.
+
+Smaller: the mobile companion now receives a push `eventId`, and two tests that depended on the
+real clock and on CI timing were pinned.
diff --git a/package-lock.json b/package-lock.json
index 59263456d..6e242b651 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "node-terminal",
- "version": "0.4.3",
+ "version": "0.4.4",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "node-terminal",
- "version": "0.4.3",
+ "version": "0.4.4",
"hasInstallScript": true,
"license": "BUSL-1.1",
"dependencies": {
diff --git a/package.json b/package.json
index 37328f616..1cf84be9b 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "node-terminal",
- "version": "0.4.3",
+ "version": "0.4.4",
"engines": {
"node": "^22.22.2 || ^24.15.0 || >=26.0.0"
},