claude-code-sessions 0.16.2__tar.gz → 0.16.3__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 (35) hide show
  1. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/LICENSE +21 -21
  2. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/PKG-INFO +34 -2
  3. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/README.md +33 -1
  4. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.egg-info/PKG-INFO +34 -2
  5. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.egg-info/SOURCES.txt +1 -0
  6. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.py +250 -36
  7. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/pyproject.toml +50 -50
  8. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_alignment.py +144 -144
  9. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_cli.py +172 -172
  10. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_containment.py +71 -71
  11. claude_code_sessions-0.16.3/tests/test_data_root.py +515 -0
  12. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_discovery.py +48 -48
  13. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_encoding.py +41 -41
  14. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_engine.py +274 -274
  15. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_golden.py +18 -18
  16. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_helpers.py +39 -39
  17. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_journal.py +87 -87
  18. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_plan_move.py +152 -29
  19. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_rows.py +73 -73
  20. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_scaffold.py +18 -18
  21. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_transcripts.py +24 -24
  22. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.egg-info/dependency_links.txt +0 -0
  23. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.egg-info/entry_points.txt +0 -0
  24. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions.egg-info/top_level.txt +0 -0
  25. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/claude_code_sessions_gui.py +0 -0
  26. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/setup.cfg +0 -0
  27. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_anonymize.py +0 -0
  28. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_commands.py +0 -0
  29. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_converge.py +0 -0
  30. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_duplicate_transcripts.py +0 -0
  31. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_gui_models.py +0 -0
  32. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_recover.py +0 -0
  33. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_retitle.py +0 -0
  34. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_sync.py +0 -0
  35. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.3}/tests/test_undo.py +0 -0
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 Craig Stoller
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Craig Stoller
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.2
3
+ Version: 0.16.3
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
@@ -620,11 +620,13 @@ window.
620
620
  | Platform | Status | Mutations |
621
621
  |---|---|---|
622
622
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
623
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
623
624
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
624
625
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
625
626
 
626
627
  The dates are measurements against specific builds - most recently Claude Desktop
627
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
629
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
628
630
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
631
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
632
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -633,6 +635,17 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
633
635
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
636
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
637
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
638
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
639
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
640
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
641
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
642
+ and a `converge` dry run) were checked against the moved store the same day. One known gap
643
+ remains: rows this tool created before the move are journaled at their old paths, so `doctor`
644
+ reports them as "no longer on disk" although they moved with the store. Those lines are false,
645
+ and so is their advice to run `new-row` again. For the same reason `undo` cannot reverse an
646
+ operation from before the move, and changes nothing trying: it refuses a `converge`, refuses a
647
+ `new-row` with "that row is already gone", which is false too, and fails with an unhandled
648
+ error on a `move`.
636
649
  The on-disk format has changed once already during this tool's own development; treat a
637
650
  much newer build as unverified territory.
638
651
 
@@ -992,6 +1005,25 @@ window into `journaled`/`completed`/`rolled_back`.
992
1005
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
1006
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
1007
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
1008
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
1009
+ app's whole user-data folder out of the Microsoft Store package, from
1010
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
1011
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
1012
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
1013
+ store and `converge` planned nothing. This release reads the moved folder first. When a
1014
+ package's data has moved, its old folder is never read, and a store still sitting there is
1015
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
1016
+ move. The guard had found it two folders up from the store, which after the move is a
1017
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
1018
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
1019
+ with the data, and the guard recognises it at its new path. When no store is found and the
1020
+ app's marker names a folder this version does not know, `doctor` says so instead of
1021
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
1022
+ reports an error rather than falling back to the old store. One gap remains: operations
1023
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
1024
+ created then as no longer on disk although they moved with the store, and `undo` cannot
1025
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
1026
+ `converge --apply` by `alignment`.
995
1027
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
996
1028
  paths and behavior on their own machines.
997
1029
 
@@ -590,11 +590,13 @@ window.
590
590
  | Platform | Status | Mutations |
591
591
  |---|---|---|
592
592
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
593
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
593
594
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
594
595
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
595
596
 
596
597
  The dates are measurements against specific builds - most recently Claude Desktop
597
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
598
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
599
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
598
600
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
599
601
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
600
602
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -603,6 +605,17 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
603
605
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
604
606
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
605
607
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
608
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
609
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
610
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
611
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
612
+ and a `converge` dry run) were checked against the moved store the same day. One known gap
613
+ remains: rows this tool created before the move are journaled at their old paths, so `doctor`
614
+ reports them as "no longer on disk" although they moved with the store. Those lines are false,
615
+ and so is their advice to run `new-row` again. For the same reason `undo` cannot reverse an
616
+ operation from before the move, and changes nothing trying: it refuses a `converge`, refuses a
617
+ `new-row` with "that row is already gone", which is false too, and fails with an unhandled
618
+ error on a `move`.
606
619
  The on-disk format has changed once already during this tool's own development; treat a
607
620
  much newer build as unverified territory.
608
621
 
@@ -962,6 +975,25 @@ window into `journaled`/`completed`/`rolled_back`.
962
975
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
963
976
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
964
977
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
978
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
979
+ app's whole user-data folder out of the Microsoft Store package, from
980
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
981
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
982
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
983
+ store and `converge` planned nothing. This release reads the moved folder first. When a
984
+ package's data has moved, its old folder is never read, and a store still sitting there is
985
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
986
+ move. The guard had found it two folders up from the store, which after the move is a
987
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
988
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
989
+ with the data, and the guard recognises it at its new path. When no store is found and the
990
+ app's marker names a folder this version does not know, `doctor` says so instead of
991
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
992
+ reports an error rather than falling back to the old store. One gap remains: operations
993
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
994
+ created then as no longer on disk although they moved with the store, and `undo` cannot
995
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
996
+ `converge --apply` by `alignment`.
965
997
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
966
998
  paths and behavior on their own machines.
967
999
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.2
3
+ Version: 0.16.3
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
@@ -620,11 +620,13 @@ window.
620
620
  | Platform | Status | Mutations |
621
621
  |---|---|---|
622
622
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
623
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
623
624
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
624
625
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
625
626
 
626
627
  The dates are measurements against specific builds - most recently Claude Desktop
627
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
629
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
628
630
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
631
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
632
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -633,6 +635,17 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
633
635
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
636
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
637
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
638
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
639
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
640
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
641
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
642
+ and a `converge` dry run) were checked against the moved store the same day. One known gap
643
+ remains: rows this tool created before the move are journaled at their old paths, so `doctor`
644
+ reports them as "no longer on disk" although they moved with the store. Those lines are false,
645
+ and so is their advice to run `new-row` again. For the same reason `undo` cannot reverse an
646
+ operation from before the move, and changes nothing trying: it refuses a `converge`, refuses a
647
+ `new-row` with "that row is already gone", which is false too, and fails with an unhandled
648
+ error on a `move`.
636
649
  The on-disk format has changed once already during this tool's own development; treat a
637
650
  much newer build as unverified territory.
638
651
 
@@ -992,6 +1005,25 @@ window into `journaled`/`completed`/`rolled_back`.
992
1005
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
1006
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
1007
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
1008
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
1009
+ app's whole user-data folder out of the Microsoft Store package, from
1010
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
1011
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
1012
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
1013
+ store and `converge` planned nothing. This release reads the moved folder first. When a
1014
+ package's data has moved, its old folder is never read, and a store still sitting there is
1015
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
1016
+ move. The guard had found it two folders up from the store, which after the move is a
1017
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
1018
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
1019
+ with the data, and the guard recognises it at its new path. When no store is found and the
1020
+ app's marker names a folder this version does not know, `doctor` says so instead of
1021
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
1022
+ reports an error rather than falling back to the old store. One gap remains: operations
1023
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
1024
+ created then as no longer on disk although they moved with the store, and `undo` cannot
1025
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
1026
+ `converge --apply` by `alignment`.
995
1027
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
996
1028
  paths and behavior on their own machines.
997
1029
 
@@ -14,6 +14,7 @@ tests/test_cli.py
14
14
  tests/test_commands.py
15
15
  tests/test_containment.py
16
16
  tests/test_converge.py
17
+ tests/test_data_root.py
17
18
  tests/test_discovery.py
18
19
  tests/test_duplicate_transcripts.py
19
20
  tests/test_encoding.py