unsnooze 1.19.3 → 1.19.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +55 -0
- package/README.md +70 -855
- package/package.json +1 -1
- package/src/agents/agy.js +37 -8
- package/src/hook.js +2 -1
- package/src/monitor.js +1 -0
- package/src/multiplexers/tmux.js +65 -27
- package/src/update-check.js +47 -12
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,60 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.19.5 — 2026-10-05
|
|
4
|
+
|
|
5
|
+
Sessions resume again under psmux, Antigravity no longer wakes early, and
|
|
6
|
+
`unsnooze update` updates the copy you are running.
|
|
7
|
+
|
|
8
|
+
### psmux (tmux on native Windows)
|
|
9
|
+
|
|
10
|
+
- Every Claude revival in psmux failed five times with `ready timeout`. psmux
|
|
11
|
+
ran the launch command through a shell, so the space in
|
|
12
|
+
`C:\Program Files\nodejs\node.exe` closed the window before Claude started.
|
|
13
|
+
Each revival now opens its own psmux session with its arguments passed
|
|
14
|
+
through as-is, which also keeps a Codex resume message in one piece (#43).
|
|
15
|
+
- A resume message can no longer be typed into an unrelated window. psmux
|
|
16
|
+
sends keys for a pane that has closed to some other pane, and every psmux
|
|
17
|
+
session numbers its first pane `%1`. unsnooze now addresses panes as
|
|
18
|
+
`session:%N` and checks the pane still exists before reading or typing (#43).
|
|
19
|
+
|
|
20
|
+
### Antigravity (`agy`)
|
|
21
|
+
|
|
22
|
+
- A session could be woken hours before its quota came back. The `Resets in
|
|
23
|
+
3h` countdown was dated from the last prompt sent in that folder, which can
|
|
24
|
+
be much older than the banner. It is now dated from when unsnooze reads the
|
|
25
|
+
banner, so a wake can be slightly late but not early (#40).
|
|
26
|
+
|
|
27
|
+
### `unsnooze update`
|
|
28
|
+
|
|
29
|
+
- With two npm installs on one machine (for example unsnooze under `~/.local`
|
|
30
|
+
and nvm's npm first on PATH), the update went into the other npm's folder
|
|
31
|
+
and the running copy never changed. The update now targets the folder the
|
|
32
|
+
running copy was installed into (#41).
|
|
33
|
+
- It no longer prints "already up to date" when a newer version is known and
|
|
34
|
+
this copy did not change. It says what happened and exits with an error (#41).
|
|
35
|
+
|
|
36
|
+
## 1.19.4 — 2026-09-30
|
|
37
|
+
|
|
38
|
+
Antigravity's new quota banner, and a shorter README.
|
|
39
|
+
|
|
40
|
+
### Antigravity (`agy`)
|
|
41
|
+
|
|
42
|
+
- The current `Individual quota reached … Resets in 2h52m46s` banner is now
|
|
43
|
+
detected, including short countdowns (`45m10s`, `30s`) and multi-day ones
|
|
44
|
+
(`6d18h`, the weekly cap). A banner a narrow pane wrapped onto two rows is
|
|
45
|
+
read whole (#38).
|
|
46
|
+
- The countdown is dated from the prompt that hit the limit, not from when
|
|
47
|
+
unsnooze noticed the banner, so a late scrape no longer pushes the wake late.
|
|
48
|
+
- When a folder has more than one recent Antigravity conversation, unsnooze no
|
|
49
|
+
longer guesses which one stopped. It wakes the live pane, and uses
|
|
50
|
+
`--continue` if that pane is gone.
|
|
51
|
+
|
|
52
|
+
### Docs
|
|
53
|
+
|
|
54
|
+
- The README is now a short overview. Per-agent details, herdr and Windows
|
|
55
|
+
notes, and the FAQ moved to the website, including a new
|
|
56
|
+
[Supported agents](https://unsnooze.dev/docs/agents/) page (#39).
|
|
57
|
+
|
|
3
58
|
## 1.19.3 — 2026-09-30
|
|
4
59
|
|
|
5
60
|
Codex fixes from a single herdr report: stops that were missed, woken late,
|