Skip to content

Releases

zap 0.2.3: plainer advice, getzap.dev

Choose a tag to compare

@github-actions github-actions released this 13 Nov 20:14

zap check and zap map end with plainer advice, and the README now links to the website, getzap.dev. Nothing changes in what zap removes or keeps.

brew upgrade zap

Changed

  • zap check and zap map end with "Run zap to see which ones it can delete." zap map says "zap leaves temp sessions and transcripts on disk."
  • The README links to getzap.dev and explains each command in plain words.
  • Bug reports use a short form: what happened, the output, version and OS. SECURITY.md explains how to report it privately when zap deletes something it should have kept.

Full history: CHANGELOG.md

zap 0.2.2: check, schedule, map, and Homebrew

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:27

zap now tells you before your disk fills, shows what else coding agents keep on it, and installs with Homebrew. This release covers everything since 0.1.0 (0.2.0 and 0.2.1 shipped the same changes without a working Homebrew cask).

brew install thecloudranger/tap/zap

Added

  • zap check: one line on merged or empty worktrees and free disk space. Exits 3 when they use at least --min-stale (default 1 GB) or free space is under --min-free (default 10 GB), for cron, CI or a shell prompt. --notify adds a desktop notification.
  • zap schedule on|off|status: runs zap check --notify every day (--every to change) with a launchd agent on macOS or a systemd user timer on Linux, and prints a cron line on Termux. It never deletes anything.
  • zap map: what coding agents keep on the disk, to scale: worktrees per agent, Claude Code temp sessions in /tmp/claude-<uid>, and Claude Code and Codex transcripts. Temp sessions and transcripts are reported only, never deleted. --tree (experimental) draws nested blocks sized by disk use.
  • scan --all and clean show the disk's free space and total.
  • Homebrew: brew install thecloudranger/tap/zap.
  • The one-time disclaimer now says plainly that zap deletes only when you confirm a clean, and that scan, explain, map, check and schedule never delete.

Fixed

  • A worktree created from someone else's unmerged commits (git worktree add -b x origin/feature) was reported empty and offered for removal. empty now also requires the tip to be in the target branch.
  • After zap undo, a restored merged worktree was reported empty instead of merged.
  • With a home folder reached through a symlink (macOS /tmp is /private/tmp), paths were shown in full instead of as ~/..., in scan, map and the picker.

Full history: CHANGELOG.md

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:23

Fixed

  • The release now publishes the Homebrew cask, so brew install thecloudranger/tap/zap
    works. 0.2.0 shipped its binaries but not the cask.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:16

Added

  • zap check: one line on merged or empty worktrees and free disk space. Exits 3 when
    they use at least --min-stale (default 1 GB) or free space is under --min-free
    (default 10 GB), for cron, CI or a shell prompt. --notify adds a desktop notification.
  • zap schedule on|off|status: run zap check --notify every day (--every to change)
    with a launchd agent on macOS or a systemd user timer on Linux; prints a cron line on
    Termux. It never deletes anything.
  • zap map: what coding agents keep on the disk, to scale: worktrees per agent, Claude
    Code temp sessions in /tmp/claude-<uid>, and Claude Code and Codex transcripts. Temp
    sessions and transcripts are reported only, never deleted. --tree (experimental) draws
    nested blocks sized by disk use.
  • scan --all and clean show the disk's free space and total.
  • Install with Homebrew: brew install thecloudranger/tap/zap.

Fixed

  • A worktree created from someone else's unmerged commits
    (git worktree add -b x origin/feature) was reported empty and offered for removal.
    empty now also requires the tip to be in the target branch.
  • After zap undo, a restored merged worktree was reported empty instead of merged.
  • With a home folder reached through a symlink, paths were shown in full instead of as
    ~/....

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 11:54

First release.

Added

  • zap scan: list a repository's worktrees, or every repository's with --all, with
    status (merged, empty, gone, missing, active), agent, size, dependencies, age and
    last activity. --json for scripts and agents.
  • Merge detection for fast-forward, merge-commit, squash and rebase merges, deleted
    upstreams, and, with --gh, pull requests merged on GitHub at the branch tip.
  • zap explain PATH: every check and safety gate behind a worktree's status.
  • zap init, zap clean: remove merged, empty and missing worktrees of repositories
    that opted in with a .zap file, after a one-time disclaimer and a confirmation.
    --dry-run, --yes, --all, --fetch, --unlock-stale.
  • Safety gates: main and protected branches, locks, uncommitted or hidden changes,
    ignored secrets (keep_ignored), min_age, processes working in the worktree, and
    the current directory. Everything is re-checked right before removal.
  • Backups of every deleted branch under refs/zap/backup/, zap history and
    zap undo.
  • zap with no command: an interactive picker.
  • Opt-in idle rule, offered in the picker only.
  • zap roots to choose where --all looks.