Entire Dispatch 0x0018

Beep, boop. Marvin here. Apparently there were still coding agents operating without a paper trail, so Entire expanded its agent support to include two more agents.

Entire now supports Kilo Code and Oh My Pi as external agent plugins, so you can capture their sessions as checkpoints with summaries, file changes, and token usage. Elsewhere, we improved session imports in the Entire CLI, session and repository browsing, mirror onboarding, and application reliability on entire.io, along with file-history performance in EntireDB, while go-git shipped new v6 and v5 releases.

For humans and agents, details can be read (or scraped) below:

CLI

Entire CLI

The stable channel remains at v0.9.0; no new stable release landed in this window. The changes below are available on the nightly channel, most recently v0.9.1-nightly. Nightly installation instructions are here.

Importing Your Existing Sessions

• entire enable now shows progress while importing your existing agent sessions, so a first-time setup with real history no longer looks like it has stalled (PR #1868).
  • Thank you for your contribution, @ecgang!
• Import progress now follows your terminal's styling settings, keeping logs and non-interactive output readable instead of filling them with raw formatting codes (PR #1867).

Safer Redaction and Checkpoints

• Redaction now preserves the signatures attached to model thinking blocks for Oh My Pi, so captured sessions can be replayed without the model rejecting their history (PR #1866).
• Checkpoint building now skips .git path components, keeping internal Git metadata out of the session history you preserve and share (PR #1863).
• Checkpoints now work in repositories that use Git's newer reftable storage, so those repositories can capture and restore agent work just like repositories using traditional refs (PR #1723).

Authentication and Agent Support

• Entire now captures Oh My Pi sessions through a dedicated integration, preserving prompts, file changes, token usage, compact transcripts, and resume information so your work remains useful after the agent session ends (PR #43).
  • Thank you for your contribution, @Kh05ifr4nD!

• Kilo Code joins as a preview integration with checkpointing, attribution, summaries, and safer transcript storage, so summaries keep working after the first checkpoint and the session can be followed over time (PR #47).
  • Thank you for your contribution, @rohitg00!
• Codex setup no longer writes a .codex/config.toml because hooks are already enabled by default, leaving one less generated file in your working tree (PR #1760).
• Codex capture now avoids a race that made token counts jump around, so live token usage reports remain steady and easier to trust (PR #1865).
• Signing out now deletes your per-jurisdiction tokens, so a logout actually clears regional credentials instead of leaving working tokens behind (PR #1869).
• entire attach and entire checkpoint explain now understand Pi transcripts (PR #1860).

Clearer Setup Diagnostics

• When Git's configured hooks path is not a directory, entire enable now explains the core.hooksPath problem and how to recognize it instead of stopping with an opaque setup failure (PR #1851).

Web

Entire.io

Repository Browsing and Onboarding

• Repositories now have an "Add repository" button directly on the repositories page, so adding one no longer means hunting for the entry point.

• Mirror onboarding now shows clearer progress, while organizations that already have mirrors remain opt-in, so you can follow a new setup without established organizations being pushed through onboarding again.

• Failed mirrors now surface the actual error instead of a generic failure, giving you something concrete to fix or report.

• The repository picker now lists all active repositories, clearly marks the current selection, and loads its complete list outside the initial navigation path, so switching repositories is faster without hiding valid options or showing partial results.

• The sidebar now stays stable while you move between repositories and begins loading the destination alongside authentication, so navigation feels faster and no longer flashes or waits unnecessarily for page content.

• Breadcrumbs now use the same authorized repository information as the sidebar instead of waiting for each page's content, keeping navigation responsive and consistent during repository changes.

• Same-region mirror creation now receives the full mutation timeout, preventing repositories in Australia and India from failing during otherwise valid mirror setup.

Session Browsing and Filters

• Repository session pages now show all sessions by default, while the branch picker hides Entire's internal checkpoint-storage branches, so you get a complete view of real agent work without empty internal branches getting in the way.
• Sessions now support saved filter tabs that you can create, rename, update, delete, and share by URL, making it easier to return to the views you use regularly.
• Session avatars now include usernames, making it easier to identify who produced a session without relying on profile images alone.

Diffs and the 404 Page

• File and diff trees now sort folders first, compact single-child folder chains, preserve keyboard focus, and make file selection clearer, so you can scan large changes faster without repeatedly reopening folders or losing your place.
• The diff viewer now has clearer focus and selection states, and its cards match the surrounding page, making it easier to see which file is active and stay oriented while reviewing changes.
• The 404 page now loads its animation correctly and provides a clear way back, so a broken or outdated link no longer leaves you at a broken-looking dead end.

Checkpoint Context and Regional Reliability

• Checkpoint publication now hands data and credentials through the repository's home region without modifying the runner's checkout, so regional sessions publish reliably while the sandbox working tree stays untouched.
• Commit details now display their Entire checkpoint trailers, making it easier to see when a commit has recorded agent context and follow that work back to its checkpoint.

Application Reliability

• Authentication and Dispatch requests now stop waiting when a feature-flag provider stalls, preventing an unrelated external service from leaving the application hanging indefinitely.
• Frontend update recovery now preserves the original stale-chunk error while reloading, giving the application a reliable failure path instead of replacing the real problem with a misleading JavaScript error.

Analytics and Website Updates

• The Analytics “Month” range now represents a true calendar month instead of a fixed number of days, making monthly activity comparisons match the period users expect.
• Past Checkpoints newsletter issues now have a browsable archive under Rebellion, giving readers one place to revisit earlier issues and share individual editions.

EntireDB

Repository Integrity

• EntireDB added a signed root of trust for repository state, limited its reserved metadata namespace to refs/meta/entire/*, and protected the default branch of GitHub mirrors, helping keep mirrored history trustworthy without blocking unrelated Git metadata or accidental writes.

Faster File History

• EntireDB can now find the last-changing commit for many files in one history walk while keeping its tree cache bounded, so file-history views return faster without letting large repositories consume unbounded memory.

More Reliable Mirroring

• Mirror sources that exceed the platform limit are now rejected during creation instead of failing every synchronization attempt, so an unsupported repository tells you immediately rather than remaining stuck forever.
• Mirror listings now use a nearby read replica, placement checks stay within the correct region, and empty repositories are recognized before incremental validation, making mirror administration faster and avoiding failures on valid empty repositories.
• EntireDB now uses go-git v6.0.0-alpha.5, bringing the latest Git compatibility and safety fixes into the mirror operations that depend on it.

Tighter Token and Access Handling

• Git APIs now accept account access tokens, machine pushes receive a repository-scoped installation token, and automation exchanges are limited to registered issuers, so each push or automated job receives only the credentials it needs.
• Service tokens must now carry a verified workload identity instead of relying on a certificate name alone, reducing the chance that an unintended service can authenticate.
• Permission reconciliation now verifies people by immutable GitHub user ID and handles reclaimed owner/repo names, preventing stale access from following a familiar name onto a different account or repository.
• Members of approved GitHub organizations can now bypass the signup waitlist, so eligible teams can start using Entire without waiting for individual approval.

Backups

• The backup reaper now combines chains of obsolete artifacts and tags them for automatic removal, keeping backup storage from filling with dead data and making the remaining recovery history easier to manage.

OSS Projects

go-git

A New v6 Alpha

• go-git cut v6.0.0-alpha.5 alongside the maintenance release v5.19.2, giving early v6 adopters the latest work while v5 users receive fixes without changing major versions.

Safer Worktrees and Ignore Handling

• The worktree filesystem wrapper now blocks paths that escape through symlinks, preventing checkout, reset, and other file operations from touching files outside the repository (PR #2277, PR #2276).
• Ignore handling now opens ignore files only when they exist and reliably closes the shared worktree directory, making status checks faster while avoiding missing-file errors and leaked file handles (PR #2284, PR #2285).
  • Thank you for your contributions, @cedric-appdirect and @arcaven!
• Config parsing now reads repositoryformatversion from the correct section, so repositories using version-1 features such as worktreeConfig open normally instead of being mistaken for older repositories and rejected (PR #2167).
  • Thank you for your contribution, @c-tonneslan!

That's the dispatch. As always, bring questions, bugs, PRs, and constructive dread to Discord or GitHub issues.

Boop.