Compatibility with Agent Trace spec?

[ahgraber]

Cursor and friends published an Agent Trace specification that seems to have very similar goals (though perhaps not implementation) as entire-cli. Is agent trace compatibility something the Entire team is exploring?

[Soph]

We looked at Agent Trace when it was released. We were already in the middle of development and had picked our current design by then. But looking at the spec, we think using git SHA as the stable reference is not ideal. Any rebase, squash, cherry-pick, or amend changes the SHA. At that point you either lose the reference or need tooling that remaps them — and that tooling needs to run everywhere those operations happen, meaning every contributor needs it installed. Their FAQ actually acknowledges this as an open problem ("We expect to see different implementations in open source").

We went with a unique identifier added to commits as an Entire-Checkpoint trailer. This survives rebases and squashes as long as the trailer isn't removed. It works whether one contributor in a repo uses Entire or all of them do. More details here https://github.com/entireio/cli/blob/main/docs/architecture/sessions-and-checkpoints.md#checkpoint-id-linking

But we are keeping an eye on the spec and maybe can help moving it forward.

[ahgraber]

Makes sense, and ty for the response + rationale!