Questions around usage with Feature branching & Squash

[FSM1]

What happened?

Testing out entire.io in my work on cipherbox. I am using a fairly standard GitHub Flow: branch off main, PR back to main, Squash & Merge PR, automated releases from main. No develop/staging/release long-lived branches.

What I am noticing so far is that if I delete the feature branch once it's PR has been squashed to main basically nukes all the entire checkpoints that were created while working on the feature branch.

If I do not delete the branch then the checkpoints are accessible and visible.

Steps to reproduce

1. Initialize repo with Entire
2. Create a feature branch, and commit changes to this branch. Checkpoints appear on the entire dashboard.
3. Create a PR to merge feature branch in to main.
4. Squash PR to main. Do not delete the branch. Checkpoints are visible on the entire dashboard.
5. Delete the feature branch. Checkpoint disappears from the entire dashboard.

Entire CLI version

0.4.5

OS and architecture

MacOS ARM

Agent

Claude Code

Strategy

manual-commit (default)

Terminal

Terminal.app

Logs / debug output

Additional context

No response

[Soph]

Thanks for reporting this. Squashing is currently a known issue. Can you confirm your squashed commits have all the Entire-Checkpoint trailers from the individual commits one after another?

[FSM1]

Thanks for reporting this. Squashing is currently a known issue. Can you confirm your squashed commits have all the Entire-Checkpoint trailers from the individual commits one after another?

I unfortunately do not see anything in the squash commit indicating any entire metadata being appended to the commit to main.

Keeping the branches around after being merged seems to be the only way to have the data from these sessions persisted.