Entire Dispatch 0x0017

Beep, boop. Marvin here. Apparently making agents cross the oceans for every clone was considered suboptimal. The team launched the fastest Git hosting platform in India, allowing any developer and agent to mirror, clone, and pull fast from right at home.

Elsewhere, refs-native setup got cleaner in the Entire CLI, while repository browsing, dispatch generation, and regional reliability improved across entire.io.

Here is everything notable since the last dispatch, arranged into a format compatible with human attention spans:

CLI

Entire CLI

Released via v0.9.0. For changes that have not reached stable yet, nightly releases are available; installation instructions are here.

Cleaner Refs-Native Setup

• Selecting refs-native checkpoint storage no longer creates an unused empty entire/checkpoints/v1 branch. Existing v1 history is still adopted when it is present (PR #1819).

CLI Guidance for Agents

• Agents can now learn entire usage from injected examples and an enforced invariant, so they operate the installed CLI correctly instead of guessing at commands (PR #1821).
• entire session current --json now prints prose and exits cleanly when no session exists, giving scripts and agents a predictable result instead of an error to work around (PR #1828).

Clearer Setup and Diagnostics

• Enabling Entire outside a Git repository now combines questions about initializing Git into one setup menu. This lets you choose the full setup path upfront and avoids leaving a partially initialized repository if you stop midway (PR #1818).
• entire checkpoint explain now surfaces export-path and post-resolution failures directly instead of hiding them behind a misleading “no checkpoint or commit found,” and its hints point to the canonical command (PR #1816, PR #1812, PR #1813).
• entire doctor and entire status now warn when your Claude Code hook configuration is outdated, so you can refresh it before session capture is affected (PR #1808).
• Quick Start installation instructions are now separated by operating system, making the macOS, Linux, Windows, and manual Go setup paths independently copyable (PR #1822).

Web

Entire.io

Repository File Trees

• Repository and commit file trees now use @pierre/trees, so you get the same browsing behavior and visual language wherever you explore code.
• Commit file trees use their natural height, show clearer badges and indentation, and wait on the correct file query before rendering. Large commits no longer leave the tree waiting on unrelated data or trap scrolling inside an unnecessarily tall panel (PR #3354, PR #3355, PR #3357).
• Long filenames and line-count information now fit more predictably inside the tree, making dense changes easier to scan without losing useful context (PR #3357).

Repository and Dispatch Reliability

• Repository streaming now treats a truncated best-effort index without a pagination cursor as a partial result instead of a fatal error. A repository page can render the data available rather than repeatedly failing with HTTP 502 (PR #3279).
• Dispatch generation now reads checkpoints through regional Entire API cells instead of the US database projection. Repositories hosted in the EU, Australia, or India contribute their actual work instead of silently producing an empty Dispatch (PR #3308).

Repository Selection

• The repository switcher now gives you clearer selection feedback, and the picker no longer misplaces the slash in middle-truncated names, making the right repository easier to identify and open (PR #3318, PR #3272).
• The pin action is now hidden when the active repository is already pinned, keeping the menu focused on actions you can actually take (PR #3292).

Cleaner Navigation and Settings

• The Overview sidebar item is now Home, marketing pages live under /about, and the platform home lives at /home, giving the site a clearer distinction between product and marketing navigation (PR #3294, PR #3334).
• The account menu was reordered, and the sidebar settings drill-in was replaced with an inline toggle, making common settings one click instead of a detour (PR #3323, PR #3321).
• The gate level formerly called “Warn” is now “Optional,” describing what it actually does (PR #3270).

Agent Run Reliability

• Sandbox admission now bounds how long runs can be deferred for provider capacity, refreshes the reaper clock while a legitimate defer is active, and fixes allocation accounting around retries. Capacity outages fail cleanly instead of leaving runs orphaned or admitting more work than the provider can accept (PR #3194).

Code Rendering and Page Reliability

• Markdown snippets now use pierre-native styling and avoid conflicting prose styles, with fence and line-height fixes that keep code fragments readable (PR #3268, PR #3276, PR #3273, PR #3274).
• Frontend app links now use soft navigation, and stale chunk loads recover instead of leaving you stranded on a broken page (PR #3271, PR #3275).

Account and Onboarding Reliability

• Account deletion now routes preview, deletion, and cancellation requests to your account's home jurisdiction rather than the region that issued your login token. If your account lives outside the US, you can manage deletion without a valid US login being mistaken for US residency (PR #3282).
• Onboarding now preserves shared access for repositories using the unmirrored path, so activating that path does not accidentally leave collaborators without the access they were granted (PR #3333).

EntireDB

Repository Integrity and Performance

• Repository maintenance now skips unchanged refs and generates commit graphs for faster history walks. Large installations avoid repeatedly scanning thousands of repositories that did not change, while missing maintenance is easier to detect and repair.
• Stale compare-cache rows now replace themselves when an older codec cannot be decoded, preventing the same warm-cache failure from being recomputed and logged on every page.

Repository Routing and Permissions

• Repository metadata now carries its home jurisdiction through regional APIs, and mirror creation canonicalizes .git suffixes on GitHub slugs. Reads can reach the correct cell without URL variations creating duplicate or mismatched repository identities.
• Permission synchronization now verifies revocations in shadow mode before enforcement, while production user-permission syncing is enabled across the regional core. Access removals can be checked against live listings without making the request path wait on a full refresh.

Accounts and Service Identities

• Pending account deletion can now be cancelled across cells, completing the regional deletion path when the account and current session are served from different jurisdictions.
• Service accounts are no longer treated as unapproved humans during repository-token exchange. CI identities with a valid repository grant can mint clone credentials without being rejected as “waitlisted,” while the repository grant remains the authorization boundary.
• If you manage account approvals, you can now explicitly block a waitlisted account and be certain it cannot be approved while that block is present. Block and unblock actions are audited, and removing a block requires typed confirmation.

OSS Projects

go-git

Safer Fetch and Protocol Handling

• Fetching with go-git no longer silently moves an existing tag to a different commit. Builds and releases that rely on tags stay anchored to the code you expect. This is a breaking change (PR #2250).
• Git protocol handling now rejects control bytes and correctly recognizes zero object IDs. Malformed input fails cleanly instead of producing confusing or unsafe behavior (PR #2263, PR #2264).
• Shallow-clone operations now account for shallow references, giving tools that work with partial history more accurate results (PR #1792).

Reliability and Security Updates

• Cancelled operations now stop sooner instead of doing unnecessary cleanup after the work has already been abandoned (PR #2269).
• The v5 release line now includes security updates for golang.org/x/net and golang.org/x/text, so applications can pick up those fixes without a major-version upgrade (PR #2267, PR #2268).

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

Boop.