Manually Importing Claude Code sessions

[kfischer-okarin]

Problem or use case

There's two use cases where it would be very helpful to be able to manually import Claude Code sessions

1. Because of some bug in entire the a session was not properly registered as checkpoint

2. When I want to start using entire with an existing repository that already has a wealth of sessions associated with it

Desired behavior

# Importing into head commit or adding to the existing checkpoint
$ entire import-session path/to/session.jsonl [path/to/session2.jsonl ...]

Imported agent session to new checkpoint .... on HEAD

# Specifying past commit
$ entire import-session path/to/session.jsonl [path/to/session2.jsonl ...] --commit efgd111

Imported agent session to new checkpoint .... on efgd111
# Maybe some kind of warning in case a checkpoint marker was added to a past commit
Caution: Your git history has now diverged from origin you will need to force push to share it with contributors

Proposed solution

No response

Alternatives or workarounds

Maybe instead of rewriting the history maybe there's also a way to somehow leave markers on future commits which assign checkpoints to past commits to keep the git history clean? But since commit sha's are not guaranteed to be stable that is probably more fragile than just biting the bullet and force pushing 😬

[khaong]

Thanks for the detailed write-up — importing existing sessions is something we're considering. There's already a PR in flight for this (#324), so we'll have a look at that and consider the approach. Appreciate you thinking through the CLI interface.