claude-code-sessions 0.16.0__tar.gz → 0.16.2__tar.gz

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.
Files changed (34) hide show
  1. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/PKG-INFO +58 -16
  2. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/README.md +58 -16
  3. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.egg-info/PKG-INFO +58 -16
  4. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.egg-info/SOURCES.txt +1 -0
  5. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.py +336 -56
  6. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions_gui.py +10 -9
  7. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_anonymize.py +7 -7
  8. claude_code_sessions-0.16.2/tests/test_duplicate_transcripts.py +392 -0
  9. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_plan_move.py +326 -6
  10. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_recover.py +413 -400
  11. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_undo.py +312 -298
  12. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/LICENSE +0 -0
  13. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.egg-info/dependency_links.txt +0 -0
  14. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.egg-info/entry_points.txt +0 -0
  15. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/claude_code_sessions.egg-info/top_level.txt +0 -0
  16. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/pyproject.toml +0 -0
  17. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/setup.cfg +0 -0
  18. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_alignment.py +0 -0
  19. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_cli.py +0 -0
  20. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_commands.py +0 -0
  21. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_containment.py +0 -0
  22. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_converge.py +0 -0
  23. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_discovery.py +0 -0
  24. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_encoding.py +0 -0
  25. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_engine.py +0 -0
  26. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_golden.py +0 -0
  27. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_gui_models.py +0 -0
  28. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_helpers.py +0 -0
  29. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_journal.py +0 -0
  30. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_retitle.py +0 -0
  31. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_rows.py +0 -0
  32. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_scaffold.py +0 -0
  33. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_sync.py +0 -0
  34. {claude_code_sessions-0.16.0 → claude_code_sessions-0.16.2}/tests/test_transcripts.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.0
3
+ Version: 0.16.2
4
4
  Summary: Unofficial tool for Claude Code sessions on disk: make a session visible under your other Claude account on the same machine, or move one between project folders. Command line or GUI. Journaled, reversible, fails closed.
5
5
  Author: Craig Stoller
6
6
  License: MIT
@@ -124,13 +124,14 @@ of the standard library, but packaged separately on some Linux distributions
124
124
  replaces the old "Claude session sync" shortcut with the new name; a taskbar pin to the
125
125
  old name is yours to re-pin.
126
126
 
127
- ## Optional: let Chrome stay open
127
+ ## Optional: let the browser stay open
128
128
 
129
- The desktop app ships a helper for its Chrome extension that can outlive the app, so the
130
- guard counts it and you have to close Chrome too. A measured build of that helper is
131
- excluded - but **the helper auto-updates every few days** (three builds in eight days, as
132
- measured), and each update correctly fails closed, so the exclusion lapses and Chrome has to
133
- be closed again until someone re-runs the ~12-minute measurement in
129
+ The desktop app ships a helper for its browser extension that Chrome or Edge launches and
130
+ that can outlive the app, so the guard counts it and you have to close that browser too. A
131
+ measured build of that helper is excluded - but **the helper auto-updates every few days**
132
+ (three builds in eight days, as measured), and each update correctly fails closed, so the
133
+ exclusion lapses and the browser has to be closed again until someone re-runs the ~12-minute
134
+ measurement in
134
135
  `tools/native-host-measurement/`.
135
136
 
136
137
  If that trade isn't worth it to you, there is an opt-in: trust **any** helper at the app's
@@ -142,7 +143,7 @@ claude-code-sessions trust-signed-helper --on # enable it
142
143
  claude-code-sessions trust-signed-helper --off # back to the default
143
144
  ```
144
145
 
145
- In the window it is the **"Let Chrome stay open"** checkbox, which explains the trade before
146
+ In the window it is the **"Let browsers stay open"** checkbox, which explains the trade before
146
147
  enabling anything. Either way it is one marker file - `~/.claude-code-journal/trust-signed-helper` -
147
148
  so deleting that file also revokes it.
148
149
 
@@ -175,9 +176,10 @@ files agree - or, if you know which account the desktop app is signed into, asse
175
176
  full). Signing into the desktop app does **not** refresh `~/.claude.json`. A refused
176
177
  `sync --apply` (desktop app running) refuses **before anything is journaled** - no lock file,
177
178
  no op directory - so there's nothing left behind for `doctor` to flag or `recover` to clean up;
178
- just close the app and re-run. One measured wrinkle: the desktop ships a helper for its Chrome
179
- extension (`chrome-native-host.exe`) that can outlive the app itself, and the guard counts it -
180
- if a refusal names that process, fully exit Chrome too (the refusal always names what it saw).
179
+ just close the app and re-run. One measured wrinkle: the desktop ships a helper for its browser
180
+ extension (`chrome-native-host.exe`), launched by Chrome or Edge, that can outlive the app
181
+ itself, and the guard counts it - if a refusal names that process, fully exit that browser too
182
+ (the refusal always names what it saw).
181
183
 
182
184
  ## Usage
183
185
 
@@ -192,7 +194,7 @@ alone cannot tell you which copy answered:
192
194
  ```
193
195
  $ ccs --version
194
196
  claude-code-sessions 0.10.0
195
- running from: C:\Users\craig\AppData\Local\pipx\...\claude_code_sessions.py
197
+ running from: C:\Users\<name>\AppData\Local\pipx\...\claude_code_sessions.py
196
198
  ```
197
199
 
198
200
  **`list`** - inventory sessions, optionally filtered by a search term:
@@ -264,7 +266,7 @@ at. The app must be closed either way, and `undo` puts the old pointer back.
264
266
  **`new-row`** - create a sidebar row for a conversation that has none:
265
267
 
266
268
  ```
267
- ccs new-row --to 174eb7c1-879f-4f0e-abff-8fdc7210f3d9
269
+ ccs new-row --to a1b2c3d4-e5f6-4a7b-8c9d-e0f1a2b3c4d5
268
270
  ```
269
271
 
270
272
  `repoint` moves an existing row and `sync` copies one between accounts; neither can
@@ -622,9 +624,17 @@ window.
622
624
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
623
625
 
624
626
  The dates are measurements against specific builds - most recently Claude Desktop
625
- 1.24012.11.0 (Microsoft Store install) and Claude Code CLI 2.1.220. The on-disk format has
626
- changed once already during this tool's own development; treat a much newer build as
627
- unverified territory.
627
+ 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
+ `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
+ had only gained keys, and every row this tool had written under 1.x was still present, some
631
+ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran against that
632
+ 2.x store with the app closed: after the app restarted, every row it had written was still
633
+ present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
+ went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
+ the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
636
+ The on-disk format has changed once already during this tool's own development; treat a
637
+ much newer build as unverified territory.
628
638
 
629
639
  **On non-Windows, `move` and every `sync` route refuse to touch the desktop store, and there
630
640
  is no flag to override that.** The layout is confirmed on Windows only; macOS reportedly has
@@ -950,6 +960,38 @@ window into `journaled`/`completed`/`rolled_back`.
950
960
  placement, and the one box the operator's own habit would have flipped stays opt-in per
951
961
  run because RULING 8 says so. DPI awareness, the audit's last item, is its own later
952
962
  release; the harness it needed now exists.
963
+ - **0.16.1 follows the desktop app's browser helper to its new folder.** Desktop 2.42304.0
964
+ deleted the `ChromeNativeHost` folder beside the session store and installed the helper in
965
+ a versioned `Claude-NativeHost\<version>` folder instead. This tool recognised the helper
966
+ only at the old exact path, so the copy at the new one counted as the running app. With the
967
+ desktop app closed and a browser running the Claude extension, every apply refused, and
968
+ neither the measured-build exclusion nor the signed-helper opt-in was consulted. The guard
969
+ failed closed, but the refusal said only to close the desktop app, which was already
970
+ closed. The guard now also recognises the new layout, derived from the real store root,
971
+ with the version folder accepted only when it is dotted ASCII digits; what each exclusion
972
+ requires is unchanged. When a process named like the helper sits at a location neither
973
+ rule recognises, the refusal now names its path and says neither exclusion can apply, so
974
+ the next move shows up in the refusal instead of failing silently. The note says Chrome or
975
+ Edge can launch the helper; on the machine where this was found, Edge did. The measurement
976
+ ceremony and the opt-in check script now find the helper where the guard does; the
977
+ ceremony had been waiting indefinitely for a helper it could not see. Also in this
978
+ release: when a session's transcript exists in two project folders and one copy is a
979
+ strict byte-prefix of the other, the duplicated-transcript hold names the stale copy, the
980
+ live copy and the removal command. It still chooses nothing. Identical copies are named
981
+ as interchangeable; copies that have diverged keep the old wording. The prefix case is
982
+ what a desktop session leaves behind when it enters a second worktree and is later
983
+ resumed in the one its sidebar row remembers: the copy in the second worktree stops
984
+ growing. It was seen twice on one machine in October.
985
+ - **0.16.2 puts the fake cast everywhere, and the helper note on every refusal.** Examples and
986
+ fixtures across the repository, from the README to the tests and the check scripts, now use
987
+ the project's fake cast rather than values read off the maintainer's own machine: account and
988
+ store identifiers, an address, a Windows user path, a sidebar title and a session id. Nothing
989
+ about what the tool reads, writes or refuses changed, and every test still exercises what it
990
+ did. Also, from the browser-helper work: the note that explains a counted helper now appears
991
+ on `move`, `undo` and `recover` refusals, not only on converge and sync; when the signed-helper
992
+ opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
+ README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
+ launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
953
995
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
954
996
  paths and behavior on their own machines.
955
997
 
@@ -94,13 +94,14 @@ of the standard library, but packaged separately on some Linux distributions
94
94
  replaces the old "Claude session sync" shortcut with the new name; a taskbar pin to the
95
95
  old name is yours to re-pin.
96
96
 
97
- ## Optional: let Chrome stay open
98
-
99
- The desktop app ships a helper for its Chrome extension that can outlive the app, so the
100
- guard counts it and you have to close Chrome too. A measured build of that helper is
101
- excluded - but **the helper auto-updates every few days** (three builds in eight days, as
102
- measured), and each update correctly fails closed, so the exclusion lapses and Chrome has to
103
- be closed again until someone re-runs the ~12-minute measurement in
97
+ ## Optional: let the browser stay open
98
+
99
+ The desktop app ships a helper for its browser extension that Chrome or Edge launches and
100
+ that can outlive the app, so the guard counts it and you have to close that browser too. A
101
+ measured build of that helper is excluded - but **the helper auto-updates every few days**
102
+ (three builds in eight days, as measured), and each update correctly fails closed, so the
103
+ exclusion lapses and the browser has to be closed again until someone re-runs the ~12-minute
104
+ measurement in
104
105
  `tools/native-host-measurement/`.
105
106
 
106
107
  If that trade isn't worth it to you, there is an opt-in: trust **any** helper at the app's
@@ -112,7 +113,7 @@ claude-code-sessions trust-signed-helper --on # enable it
112
113
  claude-code-sessions trust-signed-helper --off # back to the default
113
114
  ```
114
115
 
115
- In the window it is the **"Let Chrome stay open"** checkbox, which explains the trade before
116
+ In the window it is the **"Let browsers stay open"** checkbox, which explains the trade before
116
117
  enabling anything. Either way it is one marker file - `~/.claude-code-journal/trust-signed-helper` -
117
118
  so deleting that file also revokes it.
118
119
 
@@ -145,9 +146,10 @@ files agree - or, if you know which account the desktop app is signed into, asse
145
146
  full). Signing into the desktop app does **not** refresh `~/.claude.json`. A refused
146
147
  `sync --apply` (desktop app running) refuses **before anything is journaled** - no lock file,
147
148
  no op directory - so there's nothing left behind for `doctor` to flag or `recover` to clean up;
148
- just close the app and re-run. One measured wrinkle: the desktop ships a helper for its Chrome
149
- extension (`chrome-native-host.exe`) that can outlive the app itself, and the guard counts it -
150
- if a refusal names that process, fully exit Chrome too (the refusal always names what it saw).
149
+ just close the app and re-run. One measured wrinkle: the desktop ships a helper for its browser
150
+ extension (`chrome-native-host.exe`), launched by Chrome or Edge, that can outlive the app
151
+ itself, and the guard counts it - if a refusal names that process, fully exit that browser too
152
+ (the refusal always names what it saw).
151
153
 
152
154
  ## Usage
153
155
 
@@ -162,7 +164,7 @@ alone cannot tell you which copy answered:
162
164
  ```
163
165
  $ ccs --version
164
166
  claude-code-sessions 0.10.0
165
- running from: C:\Users\craig\AppData\Local\pipx\...\claude_code_sessions.py
167
+ running from: C:\Users\<name>\AppData\Local\pipx\...\claude_code_sessions.py
166
168
  ```
167
169
 
168
170
  **`list`** - inventory sessions, optionally filtered by a search term:
@@ -234,7 +236,7 @@ at. The app must be closed either way, and `undo` puts the old pointer back.
234
236
  **`new-row`** - create a sidebar row for a conversation that has none:
235
237
 
236
238
  ```
237
- ccs new-row --to 174eb7c1-879f-4f0e-abff-8fdc7210f3d9
239
+ ccs new-row --to a1b2c3d4-e5f6-4a7b-8c9d-e0f1a2b3c4d5
238
240
  ```
239
241
 
240
242
  `repoint` moves an existing row and `sync` copies one between accounts; neither can
@@ -592,9 +594,17 @@ window.
592
594
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
593
595
 
594
596
  The dates are measurements against specific builds - most recently Claude Desktop
595
- 1.24012.11.0 (Microsoft Store install) and Claude Code CLI 2.1.220. The on-disk format has
596
- changed once already during this tool's own development; treat a much newer build as
597
- unverified territory.
597
+ 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
598
+ read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
599
+ `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
600
+ had only gained keys, and every row this tool had written under 1.x was still present, some
601
+ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran against that
602
+ 2.x store with the app closed: after the app restarted, every row it had written was still
603
+ present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
604
+ went through against 2.42304.0.0 with the app closed, with the same result. That build moved
605
+ the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
606
+ The on-disk format has changed once already during this tool's own development; treat a
607
+ much newer build as unverified territory.
598
608
 
599
609
  **On non-Windows, `move` and every `sync` route refuse to touch the desktop store, and there
600
610
  is no flag to override that.** The layout is confirmed on Windows only; macOS reportedly has
@@ -920,6 +930,38 @@ window into `journaled`/`completed`/`rolled_back`.
920
930
  placement, and the one box the operator's own habit would have flipped stays opt-in per
921
931
  run because RULING 8 says so. DPI awareness, the audit's last item, is its own later
922
932
  release; the harness it needed now exists.
933
+ - **0.16.1 follows the desktop app's browser helper to its new folder.** Desktop 2.42304.0
934
+ deleted the `ChromeNativeHost` folder beside the session store and installed the helper in
935
+ a versioned `Claude-NativeHost\<version>` folder instead. This tool recognised the helper
936
+ only at the old exact path, so the copy at the new one counted as the running app. With the
937
+ desktop app closed and a browser running the Claude extension, every apply refused, and
938
+ neither the measured-build exclusion nor the signed-helper opt-in was consulted. The guard
939
+ failed closed, but the refusal said only to close the desktop app, which was already
940
+ closed. The guard now also recognises the new layout, derived from the real store root,
941
+ with the version folder accepted only when it is dotted ASCII digits; what each exclusion
942
+ requires is unchanged. When a process named like the helper sits at a location neither
943
+ rule recognises, the refusal now names its path and says neither exclusion can apply, so
944
+ the next move shows up in the refusal instead of failing silently. The note says Chrome or
945
+ Edge can launch the helper; on the machine where this was found, Edge did. The measurement
946
+ ceremony and the opt-in check script now find the helper where the guard does; the
947
+ ceremony had been waiting indefinitely for a helper it could not see. Also in this
948
+ release: when a session's transcript exists in two project folders and one copy is a
949
+ strict byte-prefix of the other, the duplicated-transcript hold names the stale copy, the
950
+ live copy and the removal command. It still chooses nothing. Identical copies are named
951
+ as interchangeable; copies that have diverged keep the old wording. The prefix case is
952
+ what a desktop session leaves behind when it enters a second worktree and is later
953
+ resumed in the one its sidebar row remembers: the copy in the second worktree stops
954
+ growing. It was seen twice on one machine in October.
955
+ - **0.16.2 puts the fake cast everywhere, and the helper note on every refusal.** Examples and
956
+ fixtures across the repository, from the README to the tests and the check scripts, now use
957
+ the project's fake cast rather than values read off the maintainer's own machine: account and
958
+ store identifiers, an address, a Windows user path, a sidebar title and a session id. Nothing
959
+ about what the tool reads, writes or refuses changed, and every test still exercises what it
960
+ did. Also, from the browser-helper work: the note that explains a counted helper now appears
961
+ on `move`, `undo` and `recover` refusals, not only on converge and sync; when the signed-helper
962
+ opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
963
+ README, the window's checkbox and the command's help, says Chrome or Edge, since either can
964
+ launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
923
965
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
924
966
  paths and behavior on their own machines.
925
967
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.0
3
+ Version: 0.16.2
4
4
  Summary: Unofficial tool for Claude Code sessions on disk: make a session visible under your other Claude account on the same machine, or move one between project folders. Command line or GUI. Journaled, reversible, fails closed.
5
5
  Author: Craig Stoller
6
6
  License: MIT
@@ -124,13 +124,14 @@ of the standard library, but packaged separately on some Linux distributions
124
124
  replaces the old "Claude session sync" shortcut with the new name; a taskbar pin to the
125
125
  old name is yours to re-pin.
126
126
 
127
- ## Optional: let Chrome stay open
127
+ ## Optional: let the browser stay open
128
128
 
129
- The desktop app ships a helper for its Chrome extension that can outlive the app, so the
130
- guard counts it and you have to close Chrome too. A measured build of that helper is
131
- excluded - but **the helper auto-updates every few days** (three builds in eight days, as
132
- measured), and each update correctly fails closed, so the exclusion lapses and Chrome has to
133
- be closed again until someone re-runs the ~12-minute measurement in
129
+ The desktop app ships a helper for its browser extension that Chrome or Edge launches and
130
+ that can outlive the app, so the guard counts it and you have to close that browser too. A
131
+ measured build of that helper is excluded - but **the helper auto-updates every few days**
132
+ (three builds in eight days, as measured), and each update correctly fails closed, so the
133
+ exclusion lapses and the browser has to be closed again until someone re-runs the ~12-minute
134
+ measurement in
134
135
  `tools/native-host-measurement/`.
135
136
 
136
137
  If that trade isn't worth it to you, there is an opt-in: trust **any** helper at the app's
@@ -142,7 +143,7 @@ claude-code-sessions trust-signed-helper --on # enable it
142
143
  claude-code-sessions trust-signed-helper --off # back to the default
143
144
  ```
144
145
 
145
- In the window it is the **"Let Chrome stay open"** checkbox, which explains the trade before
146
+ In the window it is the **"Let browsers stay open"** checkbox, which explains the trade before
146
147
  enabling anything. Either way it is one marker file - `~/.claude-code-journal/trust-signed-helper` -
147
148
  so deleting that file also revokes it.
148
149
 
@@ -175,9 +176,10 @@ files agree - or, if you know which account the desktop app is signed into, asse
175
176
  full). Signing into the desktop app does **not** refresh `~/.claude.json`. A refused
176
177
  `sync --apply` (desktop app running) refuses **before anything is journaled** - no lock file,
177
178
  no op directory - so there's nothing left behind for `doctor` to flag or `recover` to clean up;
178
- just close the app and re-run. One measured wrinkle: the desktop ships a helper for its Chrome
179
- extension (`chrome-native-host.exe`) that can outlive the app itself, and the guard counts it -
180
- if a refusal names that process, fully exit Chrome too (the refusal always names what it saw).
179
+ just close the app and re-run. One measured wrinkle: the desktop ships a helper for its browser
180
+ extension (`chrome-native-host.exe`), launched by Chrome or Edge, that can outlive the app
181
+ itself, and the guard counts it - if a refusal names that process, fully exit that browser too
182
+ (the refusal always names what it saw).
181
183
 
182
184
  ## Usage
183
185
 
@@ -192,7 +194,7 @@ alone cannot tell you which copy answered:
192
194
  ```
193
195
  $ ccs --version
194
196
  claude-code-sessions 0.10.0
195
- running from: C:\Users\craig\AppData\Local\pipx\...\claude_code_sessions.py
197
+ running from: C:\Users\<name>\AppData\Local\pipx\...\claude_code_sessions.py
196
198
  ```
197
199
 
198
200
  **`list`** - inventory sessions, optionally filtered by a search term:
@@ -264,7 +266,7 @@ at. The app must be closed either way, and `undo` puts the old pointer back.
264
266
  **`new-row`** - create a sidebar row for a conversation that has none:
265
267
 
266
268
  ```
267
- ccs new-row --to 174eb7c1-879f-4f0e-abff-8fdc7210f3d9
269
+ ccs new-row --to a1b2c3d4-e5f6-4a7b-8c9d-e0f1a2b3c4d5
268
270
  ```
269
271
 
270
272
  `repoint` moves an existing row and `sync` copies one between accounts; neither can
@@ -622,9 +624,17 @@ window.
622
624
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
623
625
 
624
626
  The dates are measurements against specific builds - most recently Claude Desktop
625
- 1.24012.11.0 (Microsoft Store install) and Claude Code CLI 2.1.220. The on-disk format has
626
- changed once already during this tool's own development; treat a much newer build as
627
- unverified territory.
627
+ 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
+ `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
+ had only gained keys, and every row this tool had written under 1.x was still present, some
631
+ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran against that
632
+ 2.x store with the app closed: after the app restarted, every row it had written was still
633
+ present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
+ went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
+ the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
636
+ The on-disk format has changed once already during this tool's own development; treat a
637
+ much newer build as unverified territory.
628
638
 
629
639
  **On non-Windows, `move` and every `sync` route refuse to touch the desktop store, and there
630
640
  is no flag to override that.** The layout is confirmed on Windows only; macOS reportedly has
@@ -950,6 +960,38 @@ window into `journaled`/`completed`/`rolled_back`.
950
960
  placement, and the one box the operator's own habit would have flipped stays opt-in per
951
961
  run because RULING 8 says so. DPI awareness, the audit's last item, is its own later
952
962
  release; the harness it needed now exists.
963
+ - **0.16.1 follows the desktop app's browser helper to its new folder.** Desktop 2.42304.0
964
+ deleted the `ChromeNativeHost` folder beside the session store and installed the helper in
965
+ a versioned `Claude-NativeHost\<version>` folder instead. This tool recognised the helper
966
+ only at the old exact path, so the copy at the new one counted as the running app. With the
967
+ desktop app closed and a browser running the Claude extension, every apply refused, and
968
+ neither the measured-build exclusion nor the signed-helper opt-in was consulted. The guard
969
+ failed closed, but the refusal said only to close the desktop app, which was already
970
+ closed. The guard now also recognises the new layout, derived from the real store root,
971
+ with the version folder accepted only when it is dotted ASCII digits; what each exclusion
972
+ requires is unchanged. When a process named like the helper sits at a location neither
973
+ rule recognises, the refusal now names its path and says neither exclusion can apply, so
974
+ the next move shows up in the refusal instead of failing silently. The note says Chrome or
975
+ Edge can launch the helper; on the machine where this was found, Edge did. The measurement
976
+ ceremony and the opt-in check script now find the helper where the guard does; the
977
+ ceremony had been waiting indefinitely for a helper it could not see. Also in this
978
+ release: when a session's transcript exists in two project folders and one copy is a
979
+ strict byte-prefix of the other, the duplicated-transcript hold names the stale copy, the
980
+ live copy and the removal command. It still chooses nothing. Identical copies are named
981
+ as interchangeable; copies that have diverged keep the old wording. The prefix case is
982
+ what a desktop session leaves behind when it enters a second worktree and is later
983
+ resumed in the one its sidebar row remembers: the copy in the second worktree stops
984
+ growing. It was seen twice on one machine in October.
985
+ - **0.16.2 puts the fake cast everywhere, and the helper note on every refusal.** Examples and
986
+ fixtures across the repository, from the README to the tests and the check scripts, now use
987
+ the project's fake cast rather than values read off the maintainer's own machine: account and
988
+ store identifiers, an address, a Windows user path, a sidebar title and a session id. Nothing
989
+ about what the tool reads, writes or refuses changed, and every test still exercises what it
990
+ did. Also, from the browser-helper work: the note that explains a counted helper now appears
991
+ on `move`, `undo` and `recover` refusals, not only on converge and sync; when the signed-helper
992
+ opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
+ README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
+ launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
953
995
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
954
996
  paths and behavior on their own machines.
955
997
 
@@ -15,6 +15,7 @@ tests/test_commands.py
15
15
  tests/test_containment.py
16
16
  tests/test_converge.py
17
17
  tests/test_discovery.py
18
+ tests/test_duplicate_transcripts.py
18
19
  tests/test_encoding.py
19
20
  tests/test_engine.py
20
21
  tests/test_golden.py