slimtree
slimtree makes git worktrees that take little disk. On macOS it clones the
files of an existing worktree of the repository with APFS clones, which share
their blocks with the originals until either side changes a file. Git sees an
ordinary worktree, so git status, commits and branches work as they do after
git worktree add.
Measured
A new worktree of pydantic-ai (6,069 tracked paths, 333 MiB), median of 5 rounds:
| slimtree | git worktree add |
|
|---|---|---|
| Disk, at the base worktree's commit | 0.84 MiB | 346 MiB |
| Disk, at a pull request's commit | 2.08 MiB | 346 MiB |
| Create | 3.31 s | 1.39 s |
First git status |
38 ms | 420 ms |
Second git status |
35 ms | 31 ms |
slimtree saves disk, not time. It takes longer than git to make a worktree,
because it hashes every file once to check each clone against Git
(git update-index --refresh). Its first git status is then as fast as the
second, but create plus first git status still takes 3.36 s against git's
1.81 s.
How it was measured:
slimtree --version:slimtree 0.1.0a1 (v0.1.0-alpha.1, f2eed729d076, go1.27.4, darwin/arm64), the binary thatuvx slimtree@0.1.0a1installs. Since 0.1.0a1,slimtree newandslimtree rmchange only in how they release their locks; the cloning and hashing the table times are unchanged.- Both tools made a new branch:
slimtree new <branch> --from <commit> --path <path>andgit worktree add -b <branch> <path> <commit>, from the same base worktree. - Disk is the data only the new worktree and its admin directory hold: the sum
of APFS's private size (
ATTR_CMNEXT_PRIVATESIZE) over their files, read right after the create.ducounts a clone's shared blocks, so it reports 345 MiB for either tool. The pull request's commit differs from the base worktree's in 56 paths. - Times are the wall-clock time of each command, at the base worktree's commit.
At the pull request's commit they were: create 3.16 s and 1.51 s, first
git status33 ms and 477 ms, secondgit status33 ms and 28 ms, for slimtree and git. - The tools alternated in order each round. Every run started and ran while the 5-minute load average was under 20; it stayed between 6.7 and 8.9.
- MacBook Air (Apple M4, 24 GB), macOS 27.2, internal SSD, Git 2.54.0 (Apple Git-157), 2026-11-17.
What works in this release
| Command | macOS on Apple silicon | Linux on x86_64 or arm64 |
|---|---|---|
slimtree new <branch> |
Makes a worktree from APFS clones | Coming |
slimtree rm <worktree> |
Removes a worktree slimtree made | Coming |
slimtree list |
Lists the worktrees slimtree made | Lists the worktrees slimtree made |
slimtree doctor |
Checks what slimtree needs | Checks the FUSE setup, and reports that Linux support is coming |
Release builds are tested on macOS 26, Ubuntu 24.04 and Alpine Linux. Linux
support is coming: there, slimtree new will make worktrees served from an
artifact-fs FUSE mount. Until then
slimtree new exits with an error on Linux and makes nothing.
Install
uv tool install slimtree
slimtree doctor
slimtree doctor checks what slimtree needs on this machine and in the current
directory. It installs nothing, and prints the fix for each check that fails.
Use
In a repository whose main worktree is ~/src/app:
cd ~/src/app
slimtree new fix/login # makes ~/src/app-login on the branch fix/login
slimtree list
slimtree rm app-login
A new worktree goes next to the main worktree, named after it and the last
segment of the branch: <main worktree>-<last segment>. Two variants:
slimtree new fix/login --path ~/wt/loginmakes~/wt/logininstead.slimtree new spike --from origin/mainmakes~/src/app-spikeon a new branchspikeatorigin/main.
slimtree new clones the main worktree, from any worktree of the repository.
It checks out the branch when it exists, and otherwise makes it at --from,
else at HEAD.
slimtree rm takes a worktree by its directory name or its path. It refuses a
worktree with changes unless you pass --force. It keeps the worktree's HEAD
in a ref under refs/slimtree/archive/ and never deletes a branch. Run
slimtree --help for every flag.
Source and license
Source: https://github.com/dsfaccini/artifact-fs. Apache-2.0; see LICENSE.
slimtree is built on dsfaccini/artifact-fs, a fork of cloudflare/artifact-fs. It is not affiliated with or endorsed by Cloudflare.
Metadata
Release files for slimtree 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| slimtree-0.1.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl | Python 3 | none | Linux musl 1.1+ x86-64, Linux glibc 2.17+ x86-64 | Details for slimtree-0.1.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl |
| slimtree-0.1.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64, Linux musl 1.1+ ARM64 | Details for slimtree-0.1.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl |
| slimtree-0.1.0-py3-none-macosx_13_0_arm64.whl | Python 3 | none | macOS 13.0+ ARM64 | Details for slimtree-0.1.0-py3-none-macosx_13_0_arm64.whl |
Total release size: 14.6 MB
Release files / slimtree-0.1.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl
| Download URL | slimtree-0.1.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl |
|---|---|
| Size | 5.0 MB |
| Tags | Linux glibc 2.17+ x86-64 Linux musl 1.1+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
294f98f039a5990afe439ac30d5be6975dca9e23e9c683f46c9205fe22c6830f
|
|
BLAKE2b-256 checksum How to use checksums |
39b66873f492a62eed4fbb12c42e5d18b1211d9231370079b5c9d06d05556f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / slimtree-0.1.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl
| Download URL | slimtree-0.1.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.musllinux_1_1_aarch64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | Linux glibc 2.17+ ARM64 Linux musl 1.1+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
76d5ff718e78fbc6b47e826831bd9b674b15599d74ea6aa5dcd4d3536fa4accd
|
|
BLAKE2b-256 checksum How to use checksums |
249775c6ac17294d2de349bdf99c1762ca4a038d90a175b83736fd2eda2ff1b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / slimtree-0.1.0-py3-none-macosx_13_0_arm64.whl
| Download URL | slimtree-0.1.0-py3-none-macosx_13_0_arm64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | Python 3 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
88791e430afde8b2672cf1791b909f515080f76ec16a5628c129e8902a231852
|
|
BLAKE2b-256 checksum How to use checksums |
17ba72a90f6c8d9950539f8da28fae7ff3a4bbf7ac4bfb0332229e3dea72350b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for slimtree 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 3 files in this release have been uploaded with provenance metadata.
Attestation for slimtree-0.1.0-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.musllinux_1_1_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.