claude-code-sessions 0.17.0__tar.gz → 0.18.0__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 (42) hide show
  1. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/PKG-INFO +113 -4
  2. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/README.md +112 -3
  3. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.egg-info/PKG-INFO +113 -4
  4. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.egg-info/SOURCES.txt +1 -0
  5. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.py +2705 -100
  6. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions_gui.py +80 -24
  7. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_anonymize.py +140 -0
  8. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_converge.py +2183 -1
  9. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_gui_models.py +139 -0
  10. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_journal_reroot.py +34 -0
  11. claude_code_sessions-0.18.0/tests/test_lineage.py +1092 -0
  12. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_realign.py +4 -0
  13. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_sync.py +2140 -0
  14. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_undo.py +55 -0
  15. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/LICENSE +0 -0
  16. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.egg-info/dependency_links.txt +0 -0
  17. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.egg-info/entry_points.txt +0 -0
  18. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/claude_code_sessions.egg-info/top_level.txt +0 -0
  19. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/pyproject.toml +0 -0
  20. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/setup.cfg +0 -0
  21. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_alignment.py +0 -0
  22. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_cli.py +0 -0
  23. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_commands.py +0 -0
  24. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_containment.py +0 -0
  25. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_data_root.py +0 -0
  26. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_discovery.py +0 -0
  27. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_duplicate_transcripts.py +0 -0
  28. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_encoding.py +0 -0
  29. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_engine.py +0 -0
  30. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_golden.py +0 -0
  31. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_gui_destination.py +0 -0
  32. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_gui_dpi.py +0 -0
  33. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_gui_env_rebuild.py +0 -0
  34. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_helpers.py +0 -0
  35. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_journal.py +0 -0
  36. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_plan_move.py +0 -0
  37. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_recover.py +0 -0
  38. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_retitle.py +0 -0
  39. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_rows.py +0 -0
  40. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_scaffold.py +0 -0
  41. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/tests/test_split_rows.py +0 -0
  42. {claude_code_sessions-0.17.0 → claude_code_sessions-0.18.0}/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.17.0
3
+ Version: 0.18.0
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
@@ -450,6 +450,22 @@ is always a preview will misread `sync --apply --json`.
450
450
  grants** across the account boundary unchanged. The permission half is the more
451
451
  security-relevant of the two: use `--verbatim` only when you actually want the second account
452
452
  to inherit what the first one had allowed.
453
+ - **A row's link to its parent is translated, not copied.** A row `sync` adds carries the same
454
+ translated link and chain that `converge` writes (see `converge`, below), or none, and the plan
455
+ prints the same `links :` and `chains :` lines. A refresh replaces the whole row, link
456
+ included, so the destination's own link is dropped or translated, never merged. A refresh that
457
+ drops it or points it at another row says so, one line per row (`link : local_c1 loses its
458
+ link`, `link : local_c1 now links to another row`, and `chain :` for the chain), and the
459
+ fields line leaves the link out so it is reported once. One exception: a destination link that
460
+ already names the same row and `taskId` is kept as it is. A refresh whose bytes already match
461
+ the destination's row is reported unchanged, unless the source row carries a link or a chain:
462
+ then the link is translated first, and the row is written when the translated link differs, so
463
+ a copy that names a row in the source account is corrected. (Under `--newer-only` such a row
464
+ meets the age holds first, like any refresh.) In the window the sync pane shows the
465
+ same lines. An apply that ends with nothing to write says "Nothing to copy: the destination
466
+ already holds these rows" and leaves Undo as it was.
467
+ **`--verbatim` copies links as they are**, so a link may name a row that does not exist in the
468
+ destination. Such an add is counted: `links : 2 copied verbatim (not translated)`.
453
469
  - **It needs the app closed too, the same as `move`, `undo`, and `recover` - regardless of which
454
470
  file resolved the signed-in account.** `sync` only ever writes the store you are *not* signed
455
471
  into, and re-checks that at the moment it writes, not just when it planned; that re-check
@@ -606,6 +622,70 @@ stopped being redundant is presence it leaves alone. `doctor`'s vanished-row che
606
622
  converge-created rows the same way it watches `new-row`'s, with the same journal-retention
607
623
  window.
608
624
 
625
+ **Side sessions keep their parent.** A side session's row names its parent's row (`spawnedFrom`),
626
+ and a row deep in a chain of them names the chain's first row (`startChain`). Both name a row by
627
+ its id in the same account, so a copy would point at a row the other account does not have.
628
+ `converge` and `sync` therefore write them translated. The link becomes
629
+ `{"sessionId": <that account's own row for the parent>, "taskId": <copied unchanged>}`, and the
630
+ chain becomes `{"firstSessionId": <that account's own row for the root>, "depth": <copied>}`.
631
+ Everything else in the source link (`title`, `sideSession`, `name`, `sharedFolder`, `wakeParent`,
632
+ `pendingPop` and any key this tool has not seen) is left behind and recorded. The `taskId` is not
633
+ optional: on the one side session measured per link shape, a link without it hid the child from
634
+ the sidebar, and a link with it nested the child under its parent. Only the link shapes that were
635
+ measured are carried: an app-written side-session link, the older `{sessionId, taskId, title}`,
636
+ and this tool's own output, so a carried link can be carried again.
637
+
638
+ The row is still created when its link is left out, and the plan says why. A link is left out
639
+ when the holders disagree on the parent or on `taskId`; when it names the conversation itself;
640
+ when the parent's transcript is gone; when that account has no row for the parent, or the
641
+ parent's own row is held in this plan, or its row there opens another conversation; when the
642
+ link's shape is not one that was measured; or when it would close a cycle. A link is written only
643
+ to a row that will exist, including a parent created in the same run, which is written first.
644
+ The plan reports it:
645
+
646
+ ```
647
+ links : 4 to carry, 1 left out (holders disagree on the parent 1)
648
+ chains : 2 to carry
649
+ cycles : 1 already present, left as they are
650
+ ```
651
+
652
+ Each part prints only when its count is not zero, the most frequent reason first. A row whose
653
+ link was left out carries `[link: <reason>]` on its own line. The apply resolves every link
654
+ again under the lock, against the store as it then stands, and its last lines say what changed
655
+ since the plan: `links : 4 carried, 1 left out (...); since the plan: 1 changed, 1 gained`.
656
+ `changed` and `dropped` count links the plan had, `gained` one it did not. With `--verbose` the
657
+ apply also lists them, one line per written row whose link or chain was left out or changed
658
+ since the plan, with its account:
659
+
660
+ ```
661
+ local_c3 -> bob@example.com (cccc1111/dddd2222) [link: the parent's own row is held in this plan; dropped since the plan]
662
+ ```
663
+
664
+ The journal records the final link per row, and recovery never resolves again. It writes the
665
+ journaled bytes, skips a row (`parent_not_written`) whose planned parent it did not write, and
666
+ skips one (`parent_changed`) whose parent's row is gone or now opens another conversation.
667
+ `recover --forward` names each row it skipped that way, with its reason, in the `skipped :` line
668
+ `converge` prints for a skipped row.
669
+
670
+ `undo` can leave a link dangling. When a row it created has become the last pointer to its
671
+ conversation, `undo` keeps it, while it still removes the parent row the same operation created.
672
+ It says so, for `undo` of a `converge`, a `sync` or a `new-row`, and for `recover --back` and a
673
+ finished `recover --forward`:
674
+
675
+ ```
676
+ link left dangling: local_c1 (its parent's row was removed)
677
+ ```
678
+
679
+ A child whose parent's row is missing is listed on its own and opens, which was measured. A
680
+ chain root's row that is missing is reported the same way ("its chain root's row"), but how the
681
+ app shows that was not measured. `link redirected: ... (its parent's row now opens another
682
+ conversation)` names a link whose target row survives and now opens a different conversation,
683
+ and `links not checked: N could not be read` counts what the report could not read. The report
684
+ covers rows that link to a row the command removed, and for `recover --forward` the operation's
685
+ own targets. It is not a check of every link in the store. A reversal cut short and run again
686
+ counts a row the first run removed as removed, so a link to it is still named. The window's Undo
687
+ shows the same lines, for a copy and a converge alike.
688
+
609
689
  **`realign`** - point every account's row of a split conversation at the folder holding its
610
690
  live transcript copy:
611
691
 
@@ -735,14 +815,14 @@ here.
735
815
  | Windows 11 + Claude Desktop 3.6556.2 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: read-only paths and `converge --apply` verified 2026-10-23, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
736
816
  | Windows 11 + Claude Desktop 4.4212.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor`, `alignment` and `converge --apply` verified 2026-11-01, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
737
817
  | Windows 11 + Claude Desktop 5.1231.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor` and `alignment` verified read-only 2026-11-10. Needs 0.16.3 or later to find the store | read-only + mutations, `--apply` not yet run on this build |
738
- | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. Needs 0.16.3 or later to find the store | read-only + mutations |
818
+ | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. From 0.18.0: `converge --apply` with carried links verified 2026-11-19, the apply with the app closed; the app nested both children opened, and after a reopen every carried link and chain read back as written. Needs 0.16.3 or later to find the store | read-only + mutations |
739
819
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
740
820
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
741
821
 
742
822
  The dates are measurements against specific builds of the MSIX that Anthropic signs and
743
823
  distributes itself from claude.ai - most recently Claude Desktop 6.6395.0.0 with Claude Code
744
- CLI 2.1.326 for `doctor` and the last `--apply` run, a `realign`; `converge --apply` last ran
745
- on 4.4212.0.0 with CLI 2.1.309. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
824
+ CLI 2.1.326 for `doctor` and the last two `--apply` runs, a `realign` on 2026-11-17 and a
825
+ `converge` on 2026-11-19. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
746
826
  This tool does not look in that package's folder and has never been run against it.
747
827
  On 2026-10-14 the
748
828
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
@@ -1231,6 +1311,35 @@ window into `journaled`/`completed`/`rolled_back`.
1231
1311
  the process's DPI over 96. Verified at 250 % and in a faithful 100 % run, and every other
1232
1312
  GUI harness passes in an aware process. 150 %, a common laptop setting, is untested; Tk 8.6
1233
1313
  is unchanged.
1314
+ - **0.18.0 keeps a side session under its parent in every account.** A side session's row names
1315
+ its parent's row (`spawnedFrom`) and its chain's first row (`startChain`), each by an id that
1316
+ exists only in that account. `converge` used to write its rows without either, and `sync`
1317
+ copied both as they stood, so a copied link named a row the destination does not have. Both
1318
+ commands now write them translated to the destination's own rows, the link as `{sessionId,
1319
+ taskId}`. On the machine it was built on, probes found that the app hides a child whose link
1320
+ lacks `taskId` and nests it when the link has both keys, for the app's side-session links and
1321
+ for its older `{sessionId, taskId, title}` links, one candidate each. Only those measured
1322
+ shapes and this tool's own output are carried. Any other link is left out with its reason, as
1323
+ are the cases "Side sessions keep their parent" above lists: holders that disagree, a parent
1324
+ the account lacks, a link that would close a cycle. A parent created in the same run is
1325
+ written first. The apply resolves every link again under the lock, and the journal keeps the
1326
+ final link per row. Recovery never resolves again. When a pending row's parent was not
1327
+ written, or its row is gone or now opens another conversation, `converge` skips that row and
1328
+ `sync` stops offering to go forward. `undo` and
1329
+ `recover --back` remove children before their parents and report any link they leave
1330
+ dangling, or naming a row that now opens another conversation; the window's Undo shows the
1331
+ same lines. A
1332
+ `spawnedFrom` or `startChain` that is not an object, a null say, counts as no link. Before
1333
+ the release, a `converge --apply` on that machine created 20 rows and carried 20 links and 18
1334
+ chains. The app nested both children opened, one whose source link also carried
1335
+ `sharedFolder` and one with `userFork`, and after a reopen every carried link and chain read
1336
+ back as written. A child with the older link shape written by a release run, and a child
1337
+ `sync` added, have not been looked at in the app. `sync` now decodes its stores a second time
1338
+ for the links. On a store of about 3,000 rows (400 MB) its dry run took about 30% longer and
1339
+ peaked at 879 MB against 229 MB, and with `--update` at 1.13 GB against 452 MB. A fix is
1340
+ planned. `converge` recovery also keeps a row that landed before a hard kill: it records the
1341
+ row as written before re-checking anything, so `undo` still removes it, even after the app
1342
+ has rewritten it.
1234
1343
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
1235
1344
  paths and behavior on their own machines.
1236
1345
 
@@ -420,6 +420,22 @@ is always a preview will misread `sync --apply --json`.
420
420
  grants** across the account boundary unchanged. The permission half is the more
421
421
  security-relevant of the two: use `--verbatim` only when you actually want the second account
422
422
  to inherit what the first one had allowed.
423
+ - **A row's link to its parent is translated, not copied.** A row `sync` adds carries the same
424
+ translated link and chain that `converge` writes (see `converge`, below), or none, and the plan
425
+ prints the same `links :` and `chains :` lines. A refresh replaces the whole row, link
426
+ included, so the destination's own link is dropped or translated, never merged. A refresh that
427
+ drops it or points it at another row says so, one line per row (`link : local_c1 loses its
428
+ link`, `link : local_c1 now links to another row`, and `chain :` for the chain), and the
429
+ fields line leaves the link out so it is reported once. One exception: a destination link that
430
+ already names the same row and `taskId` is kept as it is. A refresh whose bytes already match
431
+ the destination's row is reported unchanged, unless the source row carries a link or a chain:
432
+ then the link is translated first, and the row is written when the translated link differs, so
433
+ a copy that names a row in the source account is corrected. (Under `--newer-only` such a row
434
+ meets the age holds first, like any refresh.) In the window the sync pane shows the
435
+ same lines. An apply that ends with nothing to write says "Nothing to copy: the destination
436
+ already holds these rows" and leaves Undo as it was.
437
+ **`--verbatim` copies links as they are**, so a link may name a row that does not exist in the
438
+ destination. Such an add is counted: `links : 2 copied verbatim (not translated)`.
423
439
  - **It needs the app closed too, the same as `move`, `undo`, and `recover` - regardless of which
424
440
  file resolved the signed-in account.** `sync` only ever writes the store you are *not* signed
425
441
  into, and re-checks that at the moment it writes, not just when it planned; that re-check
@@ -576,6 +592,70 @@ stopped being redundant is presence it leaves alone. `doctor`'s vanished-row che
576
592
  converge-created rows the same way it watches `new-row`'s, with the same journal-retention
577
593
  window.
578
594
 
595
+ **Side sessions keep their parent.** A side session's row names its parent's row (`spawnedFrom`),
596
+ and a row deep in a chain of them names the chain's first row (`startChain`). Both name a row by
597
+ its id in the same account, so a copy would point at a row the other account does not have.
598
+ `converge` and `sync` therefore write them translated. The link becomes
599
+ `{"sessionId": <that account's own row for the parent>, "taskId": <copied unchanged>}`, and the
600
+ chain becomes `{"firstSessionId": <that account's own row for the root>, "depth": <copied>}`.
601
+ Everything else in the source link (`title`, `sideSession`, `name`, `sharedFolder`, `wakeParent`,
602
+ `pendingPop` and any key this tool has not seen) is left behind and recorded. The `taskId` is not
603
+ optional: on the one side session measured per link shape, a link without it hid the child from
604
+ the sidebar, and a link with it nested the child under its parent. Only the link shapes that were
605
+ measured are carried: an app-written side-session link, the older `{sessionId, taskId, title}`,
606
+ and this tool's own output, so a carried link can be carried again.
607
+
608
+ The row is still created when its link is left out, and the plan says why. A link is left out
609
+ when the holders disagree on the parent or on `taskId`; when it names the conversation itself;
610
+ when the parent's transcript is gone; when that account has no row for the parent, or the
611
+ parent's own row is held in this plan, or its row there opens another conversation; when the
612
+ link's shape is not one that was measured; or when it would close a cycle. A link is written only
613
+ to a row that will exist, including a parent created in the same run, which is written first.
614
+ The plan reports it:
615
+
616
+ ```
617
+ links : 4 to carry, 1 left out (holders disagree on the parent 1)
618
+ chains : 2 to carry
619
+ cycles : 1 already present, left as they are
620
+ ```
621
+
622
+ Each part prints only when its count is not zero, the most frequent reason first. A row whose
623
+ link was left out carries `[link: <reason>]` on its own line. The apply resolves every link
624
+ again under the lock, against the store as it then stands, and its last lines say what changed
625
+ since the plan: `links : 4 carried, 1 left out (...); since the plan: 1 changed, 1 gained`.
626
+ `changed` and `dropped` count links the plan had, `gained` one it did not. With `--verbose` the
627
+ apply also lists them, one line per written row whose link or chain was left out or changed
628
+ since the plan, with its account:
629
+
630
+ ```
631
+ local_c3 -> bob@example.com (cccc1111/dddd2222) [link: the parent's own row is held in this plan; dropped since the plan]
632
+ ```
633
+
634
+ The journal records the final link per row, and recovery never resolves again. It writes the
635
+ journaled bytes, skips a row (`parent_not_written`) whose planned parent it did not write, and
636
+ skips one (`parent_changed`) whose parent's row is gone or now opens another conversation.
637
+ `recover --forward` names each row it skipped that way, with its reason, in the `skipped :` line
638
+ `converge` prints for a skipped row.
639
+
640
+ `undo` can leave a link dangling. When a row it created has become the last pointer to its
641
+ conversation, `undo` keeps it, while it still removes the parent row the same operation created.
642
+ It says so, for `undo` of a `converge`, a `sync` or a `new-row`, and for `recover --back` and a
643
+ finished `recover --forward`:
644
+
645
+ ```
646
+ link left dangling: local_c1 (its parent's row was removed)
647
+ ```
648
+
649
+ A child whose parent's row is missing is listed on its own and opens, which was measured. A
650
+ chain root's row that is missing is reported the same way ("its chain root's row"), but how the
651
+ app shows that was not measured. `link redirected: ... (its parent's row now opens another
652
+ conversation)` names a link whose target row survives and now opens a different conversation,
653
+ and `links not checked: N could not be read` counts what the report could not read. The report
654
+ covers rows that link to a row the command removed, and for `recover --forward` the operation's
655
+ own targets. It is not a check of every link in the store. A reversal cut short and run again
656
+ counts a row the first run removed as removed, so a link to it is still named. The window's Undo
657
+ shows the same lines, for a copy and a converge alike.
658
+
579
659
  **`realign`** - point every account's row of a split conversation at the folder holding its
580
660
  live transcript copy:
581
661
 
@@ -705,14 +785,14 @@ here.
705
785
  | Windows 11 + Claude Desktop 3.6556.2 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: read-only paths and `converge --apply` verified 2026-10-23, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
706
786
  | Windows 11 + Claude Desktop 4.4212.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor`, `alignment` and `converge --apply` verified 2026-11-01, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
707
787
  | Windows 11 + Claude Desktop 5.1231.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor` and `alignment` verified read-only 2026-11-10. Needs 0.16.3 or later to find the store | read-only + mutations, `--apply` not yet run on this build |
708
- | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. Needs 0.16.3 or later to find the store | read-only + mutations |
788
+ | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. From 0.18.0: `converge --apply` with carried links verified 2026-11-19, the apply with the app closed; the app nested both children opened, and after a reopen every carried link and chain read back as written. Needs 0.16.3 or later to find the store | read-only + mutations |
709
789
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
710
790
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
711
791
 
712
792
  The dates are measurements against specific builds of the MSIX that Anthropic signs and
713
793
  distributes itself from claude.ai - most recently Claude Desktop 6.6395.0.0 with Claude Code
714
- CLI 2.1.326 for `doctor` and the last `--apply` run, a `realign`; `converge --apply` last ran
715
- on 4.4212.0.0 with CLI 2.1.309. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
794
+ CLI 2.1.326 for `doctor` and the last two `--apply` runs, a `realign` on 2026-11-17 and a
795
+ `converge` on 2026-11-19. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
716
796
  This tool does not look in that package's folder and has never been run against it.
717
797
  On 2026-10-14 the
718
798
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
@@ -1201,6 +1281,35 @@ window into `journaled`/`completed`/`rolled_back`.
1201
1281
  the process's DPI over 96. Verified at 250 % and in a faithful 100 % run, and every other
1202
1282
  GUI harness passes in an aware process. 150 %, a common laptop setting, is untested; Tk 8.6
1203
1283
  is unchanged.
1284
+ - **0.18.0 keeps a side session under its parent in every account.** A side session's row names
1285
+ its parent's row (`spawnedFrom`) and its chain's first row (`startChain`), each by an id that
1286
+ exists only in that account. `converge` used to write its rows without either, and `sync`
1287
+ copied both as they stood, so a copied link named a row the destination does not have. Both
1288
+ commands now write them translated to the destination's own rows, the link as `{sessionId,
1289
+ taskId}`. On the machine it was built on, probes found that the app hides a child whose link
1290
+ lacks `taskId` and nests it when the link has both keys, for the app's side-session links and
1291
+ for its older `{sessionId, taskId, title}` links, one candidate each. Only those measured
1292
+ shapes and this tool's own output are carried. Any other link is left out with its reason, as
1293
+ are the cases "Side sessions keep their parent" above lists: holders that disagree, a parent
1294
+ the account lacks, a link that would close a cycle. A parent created in the same run is
1295
+ written first. The apply resolves every link again under the lock, and the journal keeps the
1296
+ final link per row. Recovery never resolves again. When a pending row's parent was not
1297
+ written, or its row is gone or now opens another conversation, `converge` skips that row and
1298
+ `sync` stops offering to go forward. `undo` and
1299
+ `recover --back` remove children before their parents and report any link they leave
1300
+ dangling, or naming a row that now opens another conversation; the window's Undo shows the
1301
+ same lines. A
1302
+ `spawnedFrom` or `startChain` that is not an object, a null say, counts as no link. Before
1303
+ the release, a `converge --apply` on that machine created 20 rows and carried 20 links and 18
1304
+ chains. The app nested both children opened, one whose source link also carried
1305
+ `sharedFolder` and one with `userFork`, and after a reopen every carried link and chain read
1306
+ back as written. A child with the older link shape written by a release run, and a child
1307
+ `sync` added, have not been looked at in the app. `sync` now decodes its stores a second time
1308
+ for the links. On a store of about 3,000 rows (400 MB) its dry run took about 30% longer and
1309
+ peaked at 879 MB against 229 MB, and with `--update` at 1.13 GB against 452 MB. A fix is
1310
+ planned. `converge` recovery also keeps a row that landed before a hard kill: it records the
1311
+ row as written before re-checking anything, so `undo` still removes it, even after the app
1312
+ has rewritten it.
1204
1313
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
1205
1314
  paths and behavior on their own machines.
1206
1315
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.17.0
3
+ Version: 0.18.0
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
@@ -450,6 +450,22 @@ is always a preview will misread `sync --apply --json`.
450
450
  grants** across the account boundary unchanged. The permission half is the more
451
451
  security-relevant of the two: use `--verbatim` only when you actually want the second account
452
452
  to inherit what the first one had allowed.
453
+ - **A row's link to its parent is translated, not copied.** A row `sync` adds carries the same
454
+ translated link and chain that `converge` writes (see `converge`, below), or none, and the plan
455
+ prints the same `links :` and `chains :` lines. A refresh replaces the whole row, link
456
+ included, so the destination's own link is dropped or translated, never merged. A refresh that
457
+ drops it or points it at another row says so, one line per row (`link : local_c1 loses its
458
+ link`, `link : local_c1 now links to another row`, and `chain :` for the chain), and the
459
+ fields line leaves the link out so it is reported once. One exception: a destination link that
460
+ already names the same row and `taskId` is kept as it is. A refresh whose bytes already match
461
+ the destination's row is reported unchanged, unless the source row carries a link or a chain:
462
+ then the link is translated first, and the row is written when the translated link differs, so
463
+ a copy that names a row in the source account is corrected. (Under `--newer-only` such a row
464
+ meets the age holds first, like any refresh.) In the window the sync pane shows the
465
+ same lines. An apply that ends with nothing to write says "Nothing to copy: the destination
466
+ already holds these rows" and leaves Undo as it was.
467
+ **`--verbatim` copies links as they are**, so a link may name a row that does not exist in the
468
+ destination. Such an add is counted: `links : 2 copied verbatim (not translated)`.
453
469
  - **It needs the app closed too, the same as `move`, `undo`, and `recover` - regardless of which
454
470
  file resolved the signed-in account.** `sync` only ever writes the store you are *not* signed
455
471
  into, and re-checks that at the moment it writes, not just when it planned; that re-check
@@ -606,6 +622,70 @@ stopped being redundant is presence it leaves alone. `doctor`'s vanished-row che
606
622
  converge-created rows the same way it watches `new-row`'s, with the same journal-retention
607
623
  window.
608
624
 
625
+ **Side sessions keep their parent.** A side session's row names its parent's row (`spawnedFrom`),
626
+ and a row deep in a chain of them names the chain's first row (`startChain`). Both name a row by
627
+ its id in the same account, so a copy would point at a row the other account does not have.
628
+ `converge` and `sync` therefore write them translated. The link becomes
629
+ `{"sessionId": <that account's own row for the parent>, "taskId": <copied unchanged>}`, and the
630
+ chain becomes `{"firstSessionId": <that account's own row for the root>, "depth": <copied>}`.
631
+ Everything else in the source link (`title`, `sideSession`, `name`, `sharedFolder`, `wakeParent`,
632
+ `pendingPop` and any key this tool has not seen) is left behind and recorded. The `taskId` is not
633
+ optional: on the one side session measured per link shape, a link without it hid the child from
634
+ the sidebar, and a link with it nested the child under its parent. Only the link shapes that were
635
+ measured are carried: an app-written side-session link, the older `{sessionId, taskId, title}`,
636
+ and this tool's own output, so a carried link can be carried again.
637
+
638
+ The row is still created when its link is left out, and the plan says why. A link is left out
639
+ when the holders disagree on the parent or on `taskId`; when it names the conversation itself;
640
+ when the parent's transcript is gone; when that account has no row for the parent, or the
641
+ parent's own row is held in this plan, or its row there opens another conversation; when the
642
+ link's shape is not one that was measured; or when it would close a cycle. A link is written only
643
+ to a row that will exist, including a parent created in the same run, which is written first.
644
+ The plan reports it:
645
+
646
+ ```
647
+ links : 4 to carry, 1 left out (holders disagree on the parent 1)
648
+ chains : 2 to carry
649
+ cycles : 1 already present, left as they are
650
+ ```
651
+
652
+ Each part prints only when its count is not zero, the most frequent reason first. A row whose
653
+ link was left out carries `[link: <reason>]` on its own line. The apply resolves every link
654
+ again under the lock, against the store as it then stands, and its last lines say what changed
655
+ since the plan: `links : 4 carried, 1 left out (...); since the plan: 1 changed, 1 gained`.
656
+ `changed` and `dropped` count links the plan had, `gained` one it did not. With `--verbose` the
657
+ apply also lists them, one line per written row whose link or chain was left out or changed
658
+ since the plan, with its account:
659
+
660
+ ```
661
+ local_c3 -> bob@example.com (cccc1111/dddd2222) [link: the parent's own row is held in this plan; dropped since the plan]
662
+ ```
663
+
664
+ The journal records the final link per row, and recovery never resolves again. It writes the
665
+ journaled bytes, skips a row (`parent_not_written`) whose planned parent it did not write, and
666
+ skips one (`parent_changed`) whose parent's row is gone or now opens another conversation.
667
+ `recover --forward` names each row it skipped that way, with its reason, in the `skipped :` line
668
+ `converge` prints for a skipped row.
669
+
670
+ `undo` can leave a link dangling. When a row it created has become the last pointer to its
671
+ conversation, `undo` keeps it, while it still removes the parent row the same operation created.
672
+ It says so, for `undo` of a `converge`, a `sync` or a `new-row`, and for `recover --back` and a
673
+ finished `recover --forward`:
674
+
675
+ ```
676
+ link left dangling: local_c1 (its parent's row was removed)
677
+ ```
678
+
679
+ A child whose parent's row is missing is listed on its own and opens, which was measured. A
680
+ chain root's row that is missing is reported the same way ("its chain root's row"), but how the
681
+ app shows that was not measured. `link redirected: ... (its parent's row now opens another
682
+ conversation)` names a link whose target row survives and now opens a different conversation,
683
+ and `links not checked: N could not be read` counts what the report could not read. The report
684
+ covers rows that link to a row the command removed, and for `recover --forward` the operation's
685
+ own targets. It is not a check of every link in the store. A reversal cut short and run again
686
+ counts a row the first run removed as removed, so a link to it is still named. The window's Undo
687
+ shows the same lines, for a copy and a converge alike.
688
+
609
689
  **`realign`** - point every account's row of a split conversation at the folder holding its
610
690
  live transcript copy:
611
691
 
@@ -735,14 +815,14 @@ here.
735
815
  | Windows 11 + Claude Desktop 3.6556.2 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: read-only paths and `converge --apply` verified 2026-10-23, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
736
816
  | Windows 11 + Claude Desktop 4.4212.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor`, `alignment` and `converge --apply` verified 2026-11-01, the apply with the app closed and the browser helper running. Needs 0.16.3 or later to find the store | read-only + mutations |
737
817
  | Windows 11 + Claude Desktop 5.1231.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | on 0.16.5: `doctor` and `alignment` verified read-only 2026-11-10. Needs 0.16.3 or later to find the store | read-only + mutations, `--apply` not yet run on this build |
738
- | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. Needs 0.16.3 or later to find the store | read-only + mutations |
818
+ | Windows 11 + Claude Desktop 6.6395.0 (user data still in `%LOCALAPPDATA%\Claude-Data`) | from 0.17.0: `doctor` and `realign --apply` verified 2026-11-17, the apply with the app closed; after the app reopened, `doctor` and a fresh `realign` plan found every rewritten row opening the live copy and no set-aside copy back in its old folder. From 0.18.0: `converge --apply` with carried links verified 2026-11-19, the apply with the app closed; the app nested both children opened, and after a reopen every carried link and chain read back as written. Needs 0.16.3 or later to find the store | read-only + mutations |
739
819
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
740
820
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
741
821
 
742
822
  The dates are measurements against specific builds of the MSIX that Anthropic signs and
743
823
  distributes itself from claude.ai - most recently Claude Desktop 6.6395.0.0 with Claude Code
744
- CLI 2.1.326 for `doctor` and the last `--apply` run, a `realign`; `converge --apply` last ran
745
- on 4.4212.0.0 with CLI 2.1.309. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
824
+ CLI 2.1.326 for `doctor` and the last two `--apply` runs, a `realign` on 2026-11-17 and a
825
+ `converge` on 2026-11-19. The Microsoft Store build is a separate package, `AnthropicPBC.Claude_<id>`.
746
826
  This tool does not look in that package's folder and has never been run against it.
747
827
  On 2026-10-14 the
748
828
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
@@ -1231,6 +1311,35 @@ window into `journaled`/`completed`/`rolled_back`.
1231
1311
  the process's DPI over 96. Verified at 250 % and in a faithful 100 % run, and every other
1232
1312
  GUI harness passes in an aware process. 150 %, a common laptop setting, is untested; Tk 8.6
1233
1313
  is unchanged.
1314
+ - **0.18.0 keeps a side session under its parent in every account.** A side session's row names
1315
+ its parent's row (`spawnedFrom`) and its chain's first row (`startChain`), each by an id that
1316
+ exists only in that account. `converge` used to write its rows without either, and `sync`
1317
+ copied both as they stood, so a copied link named a row the destination does not have. Both
1318
+ commands now write them translated to the destination's own rows, the link as `{sessionId,
1319
+ taskId}`. On the machine it was built on, probes found that the app hides a child whose link
1320
+ lacks `taskId` and nests it when the link has both keys, for the app's side-session links and
1321
+ for its older `{sessionId, taskId, title}` links, one candidate each. Only those measured
1322
+ shapes and this tool's own output are carried. Any other link is left out with its reason, as
1323
+ are the cases "Side sessions keep their parent" above lists: holders that disagree, a parent
1324
+ the account lacks, a link that would close a cycle. A parent created in the same run is
1325
+ written first. The apply resolves every link again under the lock, and the journal keeps the
1326
+ final link per row. Recovery never resolves again. When a pending row's parent was not
1327
+ written, or its row is gone or now opens another conversation, `converge` skips that row and
1328
+ `sync` stops offering to go forward. `undo` and
1329
+ `recover --back` remove children before their parents and report any link they leave
1330
+ dangling, or naming a row that now opens another conversation; the window's Undo shows the
1331
+ same lines. A
1332
+ `spawnedFrom` or `startChain` that is not an object, a null say, counts as no link. Before
1333
+ the release, a `converge --apply` on that machine created 20 rows and carried 20 links and 18
1334
+ chains. The app nested both children opened, one whose source link also carried
1335
+ `sharedFolder` and one with `userFork`, and after a reopen every carried link and chain read
1336
+ back as written. A child with the older link shape written by a release run, and a child
1337
+ `sync` added, have not been looked at in the app. `sync` now decodes its stores a second time
1338
+ for the links. On a store of about 3,000 rows (400 MB) its dry run took about 30% longer and
1339
+ peaked at 879 MB against 229 MB, and with `--update` at 1.13 GB against 452 MB. A fix is
1340
+ planned. `converge` recovery also keeps a row that landed before a hard kill: it records the
1341
+ row as written before re-checking anything, so `undo` still removes it, even after the app
1342
+ has rewritten it.
1234
1343
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
1235
1344
  paths and behavior on their own machines.
1236
1345
 
@@ -27,6 +27,7 @@ tests/test_gui_models.py
27
27
  tests/test_helpers.py
28
28
  tests/test_journal.py
29
29
  tests/test_journal_reroot.py
30
+ tests/test_lineage.py
30
31
  tests/test_plan_move.py
31
32
  tests/test_realign.py
32
33
  tests/test_recover.py