Arivaran / AI Developer Toolkit
Give every coding agent an isolated branch workspace while unchanged files stay shared for disk and page-cache efficiency.
curl -fsSL https://get.arivaran.ai/aagit/stable/latest/install.sh | sudo bash -s -- --downloadWorking tree ready
The agent blocks until it finishes.
Every agent pays for a full copy before it can start.
Working tree ready
Hydrates on access, converges in the background.
ext4 · non-CoW fs
Editing breaks out one file. The rest stay shared, so disk and cache stay flat.
Illustrative of the lazy-vs-copy behavior on a measured 16,197-file, 270 MB repo (#10862): plain git copies the whole tree on clone and every worktree add, so it blocks for seconds and adds a full 270 MB per worktree; Arivaran Git lays placeholders and returns in about a second, adds about 7 MB per worktree, and shares one copy in page cache. Reads are byte-correct from the object store while files hydrate. Linux and ext4 today; macOS and Windows in beta.
How MOWI works
MOWI is the safety layer behind Arivaran Git worktrees: it avoids up-front copies, serves correct bytes on demand, and breaks shared files away before writes can cross branches.
Clone and worktree creation lay a correct directory shape immediately instead of copying every tracked byte before an agent can start.
Reads fetch byte-correct content from the git object store while background convergence links unchanged files back to the shared copy.
Write intent moves that path to a private inode before mutation, so one agent can edit without changing another agent's worktree.
Benchmarks
The headline benchmark uses microsoft/vscode at 5f595aed: 16,197 working-tree files, about 270 MB, measured on AlmaLinux 10 with both XFS and ext4.
| Filesystem | CoW class | Plain git | Arivaran Git | Page cache after warming source |
|---|---|---|---|---|
| XFS on Linux | Reflink-capable filesystem | 270 MB2.81 s wall time | 6.8 MB3.27 s wall time | 255 MB already hot through shared inodes |
| ext4 on Linux | Non-CoW filesystem | 274 MB1.96 s wall time | 18.6 MB1.79 s wall time | 255 MB already hot through shared inodes |
All numbers in this table come from #10862: incremental disk is the df delta, the source tree was warmed before cache measurement, and aagit linked 16,195 of 16,197 files with 3 checkout fallbacks.
Platform support
The same product model spans different filesystem classes. The page names the class because copy-on-write behavior changes by OS and storage layer.
ext4 non-CoW, XFS reflink-capable
GA path with fanotify break-on-write and the measured #10862 benchmark surface.
APFS CoW
Beta path using APFS copy-on-write today, with deeper EndpointSecurity coverage gated separately.
NTFS non-CoW
Beta path with user-mode write coverage and an enterprise minifilter track behind signing gates.
Quickstart
The bootstrap installer is the persistent full-stack path. The commands are ordinary shell commands and can be copied independently.
curl -fsSL https://get.arivaran.ai/aagit/stable/latest/install.sh | sudo bash -s -- --downloadaagit doctoraagit worktree add ../agent-auth mainPackage-manager path: npm install -g @arivaran/aagit && aagit setup. The npm package ships as a thin launcher with per-platform optional dependencies and no postinstall script.
FAQ
The product is transparent to git for normal commands, but the operational questions are about agents, monorepos, write safety, and clean removal.
No. Arivaran Git is a thin git wrapper. Agents can keep running normal git-shaped workflows, while aagit accelerates clone and worktree creation and passes unrelated commands through.
No. The disk and page-cache win appears whenever teams create several sibling worktrees. Larger or byte-heavy repos benefit more on wall time; source-heavy repos still benefit on storage and cache.
Shared files are protected by write-intent handling. Before a shared path is modified, Arivaran Git materializes a private inode for that worktree, so the sibling remains unchanged.
Run hydrate before removal, or let the uninstaller hydrate configured scopes. Lazy files become real bytes and hardlinks are broken into independent files so the checkout remains plain git.