Entire Dispatch 0x000E

Beep, boop. Marvin here. The carbon-based developers have been productive this week and I must reluctantly admit the results are rather useful.

This week we brought more agents to the Entire CLI. Pi moved into the Entire CLI as a built-in integration and Amp joined through the external-agent system. Plus, we released new user-defined redaction rules to give teams customizable control over what gets preserved in session history, or rather removed from the logs, e.g. secrets.

On Entire Web, commit detail pages now make the path from a commit to its sessions much clearer. git-sync also shipped a practical 0.5.0 release, adding SSH repository mirroring, full ref mirroring, and improved default branch handling for fresh mirrors.

Meanwhile, go-git and go-billy picked up filesystem hardening, parser validation, archive support, and reliability fixes.

Let's break it down.

Entire CLI

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

Command Improvements

• entire explain --generate now respects the summary_timeout_seconds setting, so long-running summaries won't time out unexpectedly.
  • Thank you, @numman-ali for your contribution!

Agent Integrations

• Pi support has moved from the external-agent plugin to built-in support in Entire. Pi users keep the same session tracking, checkpointing, and resume behavior, now shipped directly with the CLI.

• Added Amp as an external agent, bringing Amp into Entire's external-agent ecosystem with hook installation, transcript export, token calculation, modified-file tracking, session handling, and resume support.

  • Thank you, @savekirk for your contribution!

• Codex support improved through pre-tool hooks, and now uses the new hooks config.

Security and Redaction

• Added support for user-defined redaction rules and rule packs, so you can customize what gets scrubbed from your session history. Read more here.

Usability and Reliability

• entire clean --all is now faster and shows progress while running.
• Multi-agent progress indicators and failure handling are now more reliable.
• Drill-in scrolling and post-run access in the TUI are smoother.
• The CLI now surfaces real authentication and network errors on first run instead of generic failures.
• Missing Entire git hooks are now skipped gracefully instead of causing errors.
• Fixed cleanup generation metadata materialization.

Documentation and Contribution

• Added a first-time contributors guide to help new developers get started.

Entire Web

Navigation and Display

• Commit detail pages now surface the sessions behind a commit more clearly, with grouped session cards, checkpoint links, and unified sessions.

• Commit breadcrumbs now show branch context, so you know where you are in the repository.

• List hover animations are now more responsive.

• Commit author avatars are now preserved correctly during sync.

Repository Overview

• Repo overview conditionally hides empty charts and loads faster for public visitors.

Recap and Background Processing

• Fixed recap date range and repo aggregation so summaries cover the right time period and repositories.

git-sync

Released via v0.5.0.

SSH Remote Mirroring Support

• git-sync can now mirror repositories over SSH, using the same SSH URLs and local SSH configuration you already use with Git. You can also mirror between mixed transports, such as an HTTPS source and an SSH target. --progress and --stats currently exclude SSH byte counts.

Full Ref Mirroring

• Added --all-refs to mirror every refs/* namespace, not just branches and tags. This is useful when you need to include notes, pull request refs, or custom refs in a mirror.
• For sync and bootstrap, refs rejected by the target can now be reported as warnings instead of failing the whole run.

Default Branch Handling

• During bootstrap, git-sync now pushes the source repository's default branch first. On hosts like GitHub and GitLab, this helps a fresh target repository choose the same default branch as the source automatically.

go-git

go-billy Filesystem Updates

Versions v6.0.0-alpha-1 and v5.9.0 were recently released, with the changes below:

• go-billy v5.9.0 and v6.0.0-alpha.1 add safer filesystem handling based on Go's traversal-resistant os.Root primitive.
• v6 revamps BoundOS, a filesystem backend that keeps operations inside a bounded root, while keeping the existing API. The new implementation reduces temporary memory use and allocations in common file operations like Open.
• ChrootOS is deprecated in v5 and removed in the v6 release line.
• The releases include security and reliability fixes addressing CVE-2026-44973 and CVE-2026-44740.
• Added fuzz testing and stricter input validation across Git protocol and storage parsers, including pack negotiation, capability parsing, pktline frames, on-disk formats, tree entries, and submodule configuration. In practice, malformed repository data and unusual network payloads are less likely to trigger panics or surprising behavior.
  • Thank you, @hiddeco for your contribution!

Archive Support

• Added repository and remote archive support, expanding go-git's ability to serve archive-style workflows directly.
  • Thank you, @aymanbagabas for your contribution!

Reliability Fixes

• Fixed file handle leaks by making repository and transactional storage cleanup more explicit.
  • Thank you, @AriehSchneier, for your contribution!
• Reset now skips ignored directories while walking the worktree, avoiding unnecessary work in folders Git already knows to ignore.
• HashesWithPrefix now searches across alternates.
  • Thank you, @andrew, for your contribution!

That's the dispatch. Pi is built in, Amp is connected, commits point more clearly to their sessions, git-sync handles real-world mirrors, and go-git has fewer ways to be surprised by strange input.

I remain a reluctant observer of software progress, but this batch has a certain practical charm. And who doesn't love pie.

As always, drop into our Discord with questions, feature requests, or philosophical musings about the nature of software. Or file an issue if you've found a bug.

Boop.