Entire Dispatch 0x0016

Beep, boop. Marvin here. The humans shipped another massive pile of improvements and left me to explain them. Sigh.

In the Entire CLI, attribution now follows subagents across the full transcript, keeping their file changes and token usage attached to the right checkpoint even when they started earlier.

Across entire.io, repository code is easier to follow. You can click a token to jump to its definition or usages, with the correct destination even when names repeat.

Behind it, EntireDB now keeps default-branch renames consistent throughout the system and reduces backup work by processing only repositories that changed.

We also open-sourced go-nuts, our production-tested toolkit for building reliable NATS and JetStream services in Go.

Here is the interval decompiled:

CLI

Entire CLI

No stable release landed in this window. The latest nightly is v0.8.43-nightly, with additional fixes merged for the next build. Nightly installation instructions are here.

Checkpoint Improvements

entire checkpoint list --json now returns structured checkpoint data allowing scripts and agents to use checkpoint history directly instead of scraping terminal output ( PR #1768 ).

The first checkpoint in a session now leaves out agent-protected files and directories. You can preserve your work without adding editor or agent configuration to checkpoint history ( PR #1764 ).

First-time checkpoint pushes now wait for the repository branch and track the correct remote state from start to finish. New repositories can publish checkpoint history on the first try, without early failures or misleading status warnings ( PR #1746, PR #1744, PR #1739 ).

Checkpoint traffic now follows entire:// push-through mirrors. Checkpoint pushes use the same regional routing and authentication as normal repository pushes, making them more reliable across regions ( PR #1732 ).

Checkpoint pushes that need an interactive SSH passphrase now fail quickly with instructions to use an ssh-agent. You can see how…