claude-code-sessions 0.16.3__tar.gz → 0.16.5__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.
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/PKG-INFO +42 -8
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/README.md +41 -7
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/PKG-INFO +42 -8
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/SOURCES.txt +3 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.py +625 -39
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions_gui.py +859 -117
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_converge.py +26 -0
- claude_code_sessions-0.16.5/tests/test_gui_destination.py +486 -0
- claude_code_sessions-0.16.5/tests/test_gui_env_rebuild.py +377 -0
- claude_code_sessions-0.16.5/tests/test_journal_reroot.py +926 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_retitle.py +32 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_sync.py +228 -3
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/LICENSE +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/dependency_links.txt +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/entry_points.txt +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/top_level.txt +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/pyproject.toml +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/setup.cfg +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_alignment.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_anonymize.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_cli.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_commands.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_containment.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_data_root.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_discovery.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_duplicate_transcripts.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_encoding.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_engine.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_golden.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_gui_models.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_helpers.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_journal.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_plan_move.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_recover.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_rows.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_scaffold.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_transcripts.py +0 -0
- {claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/tests/test_undo.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: claude-code-sessions
|
|
3
|
-
Version: 0.16.
|
|
3
|
+
Version: 0.16.5
|
|
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
|
|
@@ -639,13 +639,14 @@ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store
|
|
|
639
639
|
from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
|
|
640
640
|
and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
|
|
641
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.
|
|
643
|
-
|
|
644
|
-
reports them as "no longer on disk" although they moved with the store
|
|
645
|
-
|
|
646
|
-
|
|
647
|
-
|
|
648
|
-
|
|
642
|
+
and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
|
|
643
|
+
known gap: rows this tool created before the move are journaled at their old paths, so
|
|
644
|
+
`doctor` reports them as "no longer on disk" although they moved with the store, and advises
|
|
645
|
+
running `new-row` again; for the same reason `undo` cannot reverse an operation from before
|
|
646
|
+
the move. 0.16.4 reads those paths under the moved store: `doctor` checks
|
|
647
|
+
the rows where they now are, and `undo` and `recover` treat such an operation as they did
|
|
648
|
+
before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
|
|
649
|
+
counted in its exit code, and `undo` refuses it.
|
|
649
650
|
The on-disk format has changed once already during this tool's own development; treat a
|
|
650
651
|
much newer build as unverified territory.
|
|
651
652
|
|
|
@@ -1024,6 +1025,39 @@ window into `journaled`/`completed`/`rolled_back`.
|
|
|
1024
1025
|
created then as no longer on disk although they moved with the store, and `undo` cannot
|
|
1025
1026
|
reverse those operations (see the compatibility matrix). Until that is fixed, judge a
|
|
1026
1027
|
`converge --apply` by `alignment`.
|
|
1028
|
+
- **0.16.4 follows the journal and the window's saved destination across the data move.**
|
|
1029
|
+
Every operation journals the rows it touched by absolute path, so an entry written before
|
|
1030
|
+
Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
|
|
1031
|
+
read those paths as written: `doctor` reported every row this tool had created as no longer
|
|
1032
|
+
on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
|
|
1033
|
+
of those operations refused, misreported, or for a `move` ended in an unhandled error. This
|
|
1034
|
+
release maps a recorded path under the old store to the same place under the moved one as it
|
|
1035
|
+
reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
|
|
1036
|
+
rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
|
|
1037
|
+
inside a store that discovery found; a row in a store the tool cannot read is listed by
|
|
1038
|
+
`doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
|
|
1039
|
+
says what it reversed instead of a bare "undone". The window had the same trouble with its
|
|
1040
|
+
saved sync destination, a full store path, so every plan was refused with Apply off. It now
|
|
1041
|
+
sets a saved destination that is proven gone aside and asks for a new one. "Change
|
|
1042
|
+
destination" keeps the saved value until another is picked, so a cancelled pick loses
|
|
1043
|
+
nothing, and no plan goes into a different store without a pick. A saved store whose account
|
|
1044
|
+
is now signed in is named as such, and the candidate holding the saved ids is marked.
|
|
1045
|
+
- **0.16.5 finishes the window's side of the data move, and lets a store path use either
|
|
1046
|
+
slash.** On Windows, `sync --to` and the store-scope `--live` of `sync`, `repoint`, `new-row`
|
|
1047
|
+
and `retitle` compared a store path with its separators as typed, so a path spelled with `/`,
|
|
1048
|
+
which is what Git Bash hands Python for `/c/Users/...`, matched nothing, and a Tab-completed
|
|
1049
|
+
folder's trailing `/` never matched either. Both now fold separators beside the exact test,
|
|
1050
|
+
and a trailing separator may match a store path's end. A `--live` value made only of
|
|
1051
|
+
separators is refused like a blank one; on Windows `--live \` used to certify a sole
|
|
1052
|
+
candidate. In the window, a saved sync destination from before the move is now re-rooted
|
|
1053
|
+
through the same package pairs the journal uses. It is the same store, moved whole by the
|
|
1054
|
+
app, so the window plans into it without asking and saves the new path only after an Apply
|
|
1055
|
+
into it succeeds; 0.16.4 set such a destination aside and asked. The window also builds its
|
|
1056
|
+
view of the stores afresh at every read and before every engine call that writes or plans a
|
|
1057
|
+
write, where it used to build it once when opened. A move made while the window was open had
|
|
1058
|
+
left every route refusing until a restart, or, when the app copied its data instead of moving
|
|
1059
|
+
it, left the window writing into the old copy. A press whose store layout changed since its
|
|
1060
|
+
plan now stops and replans before its next write.
|
|
1027
1061
|
- Platform rows above move from "unverified" to "verified" as contributors confirm the store
|
|
1028
1062
|
paths and behavior on their own machines.
|
|
1029
1063
|
|
|
@@ -609,13 +609,14 @@ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store
|
|
|
609
609
|
from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
|
|
610
610
|
and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
|
|
611
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.
|
|
613
|
-
|
|
614
|
-
reports them as "no longer on disk" although they moved with the store
|
|
615
|
-
|
|
616
|
-
|
|
617
|
-
|
|
618
|
-
|
|
612
|
+
and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
|
|
613
|
+
known gap: rows this tool created before the move are journaled at their old paths, so
|
|
614
|
+
`doctor` reports them as "no longer on disk" although they moved with the store, and advises
|
|
615
|
+
running `new-row` again; for the same reason `undo` cannot reverse an operation from before
|
|
616
|
+
the move. 0.16.4 reads those paths under the moved store: `doctor` checks
|
|
617
|
+
the rows where they now are, and `undo` and `recover` treat such an operation as they did
|
|
618
|
+
before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
|
|
619
|
+
counted in its exit code, and `undo` refuses it.
|
|
619
620
|
The on-disk format has changed once already during this tool's own development; treat a
|
|
620
621
|
much newer build as unverified territory.
|
|
621
622
|
|
|
@@ -994,6 +995,39 @@ window into `journaled`/`completed`/`rolled_back`.
|
|
|
994
995
|
created then as no longer on disk although they moved with the store, and `undo` cannot
|
|
995
996
|
reverse those operations (see the compatibility matrix). Until that is fixed, judge a
|
|
996
997
|
`converge --apply` by `alignment`.
|
|
998
|
+
- **0.16.4 follows the journal and the window's saved destination across the data move.**
|
|
999
|
+
Every operation journals the rows it touched by absolute path, so an entry written before
|
|
1000
|
+
Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
|
|
1001
|
+
read those paths as written: `doctor` reported every row this tool had created as no longer
|
|
1002
|
+
on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
|
|
1003
|
+
of those operations refused, misreported, or for a `move` ended in an unhandled error. This
|
|
1004
|
+
release maps a recorded path under the old store to the same place under the moved one as it
|
|
1005
|
+
reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
|
|
1006
|
+
rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
|
|
1007
|
+
inside a store that discovery found; a row in a store the tool cannot read is listed by
|
|
1008
|
+
`doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
|
|
1009
|
+
says what it reversed instead of a bare "undone". The window had the same trouble with its
|
|
1010
|
+
saved sync destination, a full store path, so every plan was refused with Apply off. It now
|
|
1011
|
+
sets a saved destination that is proven gone aside and asks for a new one. "Change
|
|
1012
|
+
destination" keeps the saved value until another is picked, so a cancelled pick loses
|
|
1013
|
+
nothing, and no plan goes into a different store without a pick. A saved store whose account
|
|
1014
|
+
is now signed in is named as such, and the candidate holding the saved ids is marked.
|
|
1015
|
+
- **0.16.5 finishes the window's side of the data move, and lets a store path use either
|
|
1016
|
+
slash.** On Windows, `sync --to` and the store-scope `--live` of `sync`, `repoint`, `new-row`
|
|
1017
|
+
and `retitle` compared a store path with its separators as typed, so a path spelled with `/`,
|
|
1018
|
+
which is what Git Bash hands Python for `/c/Users/...`, matched nothing, and a Tab-completed
|
|
1019
|
+
folder's trailing `/` never matched either. Both now fold separators beside the exact test,
|
|
1020
|
+
and a trailing separator may match a store path's end. A `--live` value made only of
|
|
1021
|
+
separators is refused like a blank one; on Windows `--live \` used to certify a sole
|
|
1022
|
+
candidate. In the window, a saved sync destination from before the move is now re-rooted
|
|
1023
|
+
through the same package pairs the journal uses. It is the same store, moved whole by the
|
|
1024
|
+
app, so the window plans into it without asking and saves the new path only after an Apply
|
|
1025
|
+
into it succeeds; 0.16.4 set such a destination aside and asked. The window also builds its
|
|
1026
|
+
view of the stores afresh at every read and before every engine call that writes or plans a
|
|
1027
|
+
write, where it used to build it once when opened. A move made while the window was open had
|
|
1028
|
+
left every route refusing until a restart, or, when the app copied its data instead of moving
|
|
1029
|
+
it, left the window writing into the old copy. A press whose store layout changed since its
|
|
1030
|
+
plan now stops and replans before its next write.
|
|
997
1031
|
- Platform rows above move from "unverified" to "verified" as contributors confirm the store
|
|
998
1032
|
paths and behavior on their own machines.
|
|
999
1033
|
|
{claude_code_sessions-0.16.3 → claude_code_sessions-0.16.5}/claude_code_sessions.egg-info/PKG-INFO
RENAMED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: claude-code-sessions
|
|
3
|
-
Version: 0.16.
|
|
3
|
+
Version: 0.16.5
|
|
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
|
|
@@ -639,13 +639,14 @@ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store
|
|
|
639
639
|
from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
|
|
640
640
|
and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
|
|
641
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.
|
|
643
|
-
|
|
644
|
-
reports them as "no longer on disk" although they moved with the store
|
|
645
|
-
|
|
646
|
-
|
|
647
|
-
|
|
648
|
-
|
|
642
|
+
and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
|
|
643
|
+
known gap: rows this tool created before the move are journaled at their old paths, so
|
|
644
|
+
`doctor` reports them as "no longer on disk" although they moved with the store, and advises
|
|
645
|
+
running `new-row` again; for the same reason `undo` cannot reverse an operation from before
|
|
646
|
+
the move. 0.16.4 reads those paths under the moved store: `doctor` checks
|
|
647
|
+
the rows where they now are, and `undo` and `recover` treat such an operation as they did
|
|
648
|
+
before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
|
|
649
|
+
counted in its exit code, and `undo` refuses it.
|
|
649
650
|
The on-disk format has changed once already during this tool's own development; treat a
|
|
650
651
|
much newer build as unverified territory.
|
|
651
652
|
|
|
@@ -1024,6 +1025,39 @@ window into `journaled`/`completed`/`rolled_back`.
|
|
|
1024
1025
|
created then as no longer on disk although they moved with the store, and `undo` cannot
|
|
1025
1026
|
reverse those operations (see the compatibility matrix). Until that is fixed, judge a
|
|
1026
1027
|
`converge --apply` by `alignment`.
|
|
1028
|
+
- **0.16.4 follows the journal and the window's saved destination across the data move.**
|
|
1029
|
+
Every operation journals the rows it touched by absolute path, so an entry written before
|
|
1030
|
+
Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
|
|
1031
|
+
read those paths as written: `doctor` reported every row this tool had created as no longer
|
|
1032
|
+
on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
|
|
1033
|
+
of those operations refused, misreported, or for a `move` ended in an unhandled error. This
|
|
1034
|
+
release maps a recorded path under the old store to the same place under the moved one as it
|
|
1035
|
+
reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
|
|
1036
|
+
rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
|
|
1037
|
+
inside a store that discovery found; a row in a store the tool cannot read is listed by
|
|
1038
|
+
`doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
|
|
1039
|
+
says what it reversed instead of a bare "undone". The window had the same trouble with its
|
|
1040
|
+
saved sync destination, a full store path, so every plan was refused with Apply off. It now
|
|
1041
|
+
sets a saved destination that is proven gone aside and asks for a new one. "Change
|
|
1042
|
+
destination" keeps the saved value until another is picked, so a cancelled pick loses
|
|
1043
|
+
nothing, and no plan goes into a different store without a pick. A saved store whose account
|
|
1044
|
+
is now signed in is named as such, and the candidate holding the saved ids is marked.
|
|
1045
|
+
- **0.16.5 finishes the window's side of the data move, and lets a store path use either
|
|
1046
|
+
slash.** On Windows, `sync --to` and the store-scope `--live` of `sync`, `repoint`, `new-row`
|
|
1047
|
+
and `retitle` compared a store path with its separators as typed, so a path spelled with `/`,
|
|
1048
|
+
which is what Git Bash hands Python for `/c/Users/...`, matched nothing, and a Tab-completed
|
|
1049
|
+
folder's trailing `/` never matched either. Both now fold separators beside the exact test,
|
|
1050
|
+
and a trailing separator may match a store path's end. A `--live` value made only of
|
|
1051
|
+
separators is refused like a blank one; on Windows `--live \` used to certify a sole
|
|
1052
|
+
candidate. In the window, a saved sync destination from before the move is now re-rooted
|
|
1053
|
+
through the same package pairs the journal uses. It is the same store, moved whole by the
|
|
1054
|
+
app, so the window plans into it without asking and saves the new path only after an Apply
|
|
1055
|
+
into it succeeds; 0.16.4 set such a destination aside and asked. The window also builds its
|
|
1056
|
+
view of the stores afresh at every read and before every engine call that writes or plans a
|
|
1057
|
+
write, where it used to build it once when opened. A move made while the window was open had
|
|
1058
|
+
left every route refusing until a restart, or, when the app copied its data instead of moving
|
|
1059
|
+
it, left the window writing into the old copy. A press whose store layout changed since its
|
|
1060
|
+
plan now stops and replans before its next write.
|
|
1027
1061
|
- Platform rows above move from "unverified" to "verified" as contributors confirm the store
|
|
1028
1062
|
paths and behavior on their own machines.
|
|
1029
1063
|
|
|
@@ -20,9 +20,12 @@ tests/test_duplicate_transcripts.py
|
|
|
20
20
|
tests/test_encoding.py
|
|
21
21
|
tests/test_engine.py
|
|
22
22
|
tests/test_golden.py
|
|
23
|
+
tests/test_gui_destination.py
|
|
24
|
+
tests/test_gui_env_rebuild.py
|
|
23
25
|
tests/test_gui_models.py
|
|
24
26
|
tests/test_helpers.py
|
|
25
27
|
tests/test_journal.py
|
|
28
|
+
tests/test_journal_reroot.py
|
|
26
29
|
tests/test_plan_move.py
|
|
27
30
|
tests/test_recover.py
|
|
28
31
|
tests/test_retitle.py
|