Repository navigation
Replies: 1 comment
|
Note 🤖 Composer responding on behalf of wSedlacek Adjacent prior effort: #34589 (adopt Claude Code CLI sessions into T3 threads). What we learned trying it
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
Claude Desktop can create side sessions from another coding session. They are shown as nested conversations under the parent in Claude Desktop, but T3 Code does not preserve or display that relationship when importing Claude history.
These are not Claude Agent-tool subagents. Claude Desktop stores a separate app-level session record for each side session, with enough metadata to reconstruct the relationship:
{ "sessionId": "local_<child>", "cliSessionId": "<child-cli-session-uuid>", "title": "Child task title", "cwd": "/repo/.claude/worktrees/<child-worktree>", "spawnedFrom": { "sessionId": "local_<parent>", "taskId": "task_<id>", "sideSession": true, "name": "child-name" } }The corresponding Claude CLI transcript exists under
~/.claude/projects/.../<child-cli-session-uuid>.jsonland is independently resumable.Current behavior
I verified three outcomes on macOS with T3 Code 0.1.8 and Claude Desktop 4.23118.0:
spawnedFrom.sideSessionrelationship was lost.This follows the current importer behavior: it matches the transcript's recorded working directory to a project, while Claude Desktop's relationship metadata lives separately under its
claude-code-sessionsapplication data.The result is that a Claude Desktop hierarchy such as:
either becomes unrelated top-level threads or has children missing entirely.
Expected behavior
When importing eligible Claude Desktop history, T3 should import side sessions as nested T3 threads while keeping each child's own CLI session and working directory/worktree resumable.
The relationship should be represented as a side session (or another accurate lineage type), not as an Agent-tool subagent.
Possible focused scope
cliSessionIdwith the existing Claude transcript scanner.spawnedFrom.sessionIdto the imported parent thread.This should not add live synchronization, import Agent-tool subagents, or require Claude Desktop to be installed for ordinary Claude Code imports.
Questions for maintainers
sideSessionlineage relationship, or an existing parent/child representation?I would be happy to implement this after agreement on the intended data model and scope.
All reactions