ARIVARAN GIT

Clone once. Give every agent an isolated worktree.

Here is how it works: clone, add a worktree, files appear as they are touched, and each write stays private. Unchanged repository content stays storage-efficient; setup time, merge conflicts, and platform behavior still depend on your workload and platform.

Clone. Add. Touch. Write—without duplicating unchanged work.

UnavailableRepository and worktree isolation

Open this product's main page Products

Arivaran Git

Unavailable

The diagram shows the mechanism, its current result, and the limit that remains in force.

Step 1 of 3Reuse repository content without repeating it
On Linux, measured worktrees keep unchanged content shared through hardlinks. On Windows, user-mode coverage is a Preview and the driver-backed mode is still being validated. On macOS, APFS clone mode shares disk blocks between independent files.
Step 2 of 3Measured storage efficiency for parallel work
Our benchmark supports the storage claim. Setup time depends on the filesystem, and the single shared page cache applies to hardlink modes, not macOS clone mode.
Step 3 of 3Limits
macOS clone mode does not share one file copy or one page cache. Public Git installation stays unavailable until its separate installer, rollback, and release requirements are met.

Mechanism

On Linux, measured worktrees keep unchanged content shared through hardlinks. On Windows, user-mode coverage is a Preview and the driver-backed mode is still being validated. On macOS, APFS clone mode shares disk blocks between independent files.

Platform state

Status is per mode, not per platform. Linux hardlink mode with break-on-write is available within its tested scope. On Windows (NTFS), the isolation mode is available only when the verified, Microsoft-signed driver is installed and active, and that driver mode is still being validated; without the driver, the user-mode fallback, which copies files up front, is a best-effort Preview. macOS APFS clone mode is available, is still being validated, needs no special Apple permission, and uses copy-on-write clones rather than a shared page cache; the macOS hardlink mode stays unavailable until Apple grants that permission and the mode is validated.

Limits

macOS clone mode does not share one file copy or one page cache. Public Git installation stays unavailable until its separate installer, rollback, and release requirements are met.

Before you start

The Windows driver still has to be proven installing and loading on real devices, including Windows driver verification. macOS clone mode still needs its cloning, isolation, metadata, fallback, installer, and status checks validated.

Evidence reviewed 2026-08-26

Git products

Overview
Arivaran Git — Unavailable
One copy of your repository content can back many isolated workspaces, using a mode that depends on the platform: shared hardlinks where validated, or copy-on-write clones on macOS APFS.
clone
worktree add
lazy / on-touch
isolated write
1. Mechanism
  Reuse repository content without repeating it
  On Linux, measured worktrees keep unchanged content shared through hardlinks. On Windows, user-mode coverage is a Preview and the driver-backed mode is still being validated. On macOS, APFS clone mode shares disk blocks between independent files.
2. Current outcome
  Measured storage efficiency for parallel work
  Our benchmark supports the storage claim. Setup time depends on the filesystem, and the single shared page cache applies to hardlink modes, not macOS clone mode.
3. Limits
  Limits
  macOS clone mode does not share one file copy or one page cache. Public Git installation stays unavailable until its separate installer, rollback, and release requirements are met.
Platform state
Status is per mode, not per platform. Linux hardlink mode with break-on-write is available within its tested scope. On Windows (NTFS), the isolation mode is available only when the verified, Microsoft-signed driver is installed and active, and that driver mode is still being validated; without the driver, the user-mode fallback, which copies files up front, is a best-effort Preview. macOS APFS clone mode is available, is still being validated, needs no special Apple permission, and uses copy-on-write clones rather than a shared page cache; the macOS hardlink mode stays unavailable until Apple grants that permission and the mode is validated.
Before you start
The Windows driver still has to be proven installing and loading on real devices, including Windows driver verification. macOS clone mode still needs its cloning, isolation, metadata, fallback, installer, and status checks validated.
Torya Build & Artifact Fabric — Planned
This is the build and artifact job that sits next to Git. It is packaged and released separately from Arivaran Git.
1. Mechanism
  Repository-to-artifact handoff
  Source state, build identity, and the resulting artifact form one traceable handoff, separate from Arivaran Git itself.
2. Current outcome
  One workflow, separate products
  You can see where build and artifact work fits, without mistaking unreleased components for a product you can buy.
3. Limits
  Limits
  There is no public Build Artifact download or sign-up on this page yet.
Platform state
Platform and deployment support will be stated once Torya and its artifact packaging are released.
Before you start
Still needed: released packages, a way to turn it on, artifact retention, and a validated service.
Git SDK and MCP integrations — Planned
SDK and MCP integrations will appear here once their public package, permissions, and compatibility rules are released.
1. Mechanism
  Typed request boundary
  An integration sends an allowed operation through a versioned interface and gets back a bounded result with a clear failure state.
2. Current outcome
  A clear integration point
  Developers can see where integrations will plug in, without assuming an unpublished package can be installed.
3. Limits
  Limits
  This integration is not released yet. It is not an install promise or an available MCP endpoint.
Platform state
Runtime and editor support stay unavailable until each integration is packaged and validated.
Before you start
Still needed: a published package, sign-in scopes, a compatibility policy, and documentation.
Git editor tooling — Planned
Editor integrations are shortcuts into the same Git workflow, each with its own signing, marketplace, and compatibility checks.
1. Mechanism
  Editor-to-workflow handoff
  The editor requests a reviewed Git operation and returns the user to a visible branch and worktree result.
2. Current outcome
  Less context switching
  The intended workflow is clear, and so is how far each package and marketplace listing has come.
3. Limits
  Limits
  No editor download or marketplace CTA is available from this panel today.
Platform state
No editor or marketplace is supported until its package is signed and validated.
Before you start
Still needed: signed extension packages, marketplace approval, version compatibility, and a tested uninstall.

What we claim depends on the mode, not just the platform.

Each row below is one isolation mode. A single badge per platform would hide that the Windows guarantee depends on a verified signed driver being active, and that macOS APFS clone mode is safe without special Apple permission but shares no page cache.

Linux · hardlinks with break-on-write
Available
ext4: no copy-on-write; XFS: supports file cloning
Available on the Linux setups we have tested.
When a program opens a shared file to write, a background service pauses it until the file has its own private copy. Support covers the Linux distributions and versions on our tested list, not every Linux system.
Windows/NTFS · Microsoft-signed driver
Available with the signed driver active
NTFS: no copy-on-write
Available only when the verified, Microsoft-signed driver is installed and active.
The driver files returned by Microsoft's signing service carry valid Windows signatures. Installing and loading the driver on real devices, and Windows driver verification, are not yet proven, so this mode is published as validation pending. This is not a WHQL certification, a Windows Update release, or a feature-release claim.
Windows/NTFS · user-mode fallback
Preview
NTFS: no copy-on-write
Preview: best-effort coverage when the driver is missing, inactive, blocked, or not yet validated.
When the fallback cannot hook a process, it copies files up front instead. This fallback is a best-effort Preview and never a system-wide, driver-backed guarantee.
macOS/APFS · clone mode
Validation pending
APFS copy-on-write
Available; validation pending. This mode needs no special Apple permission.
Each clone is an independent file whose disk blocks are shared until one side changes, so the mode is safe without intercepting file opens. An APFS clone is not a hardlink, so it does not share page cache or memory. Validation of cloning, write isolation, metadata, fallback on non-APFS volumes, installer setup, and status checks is still pending.
macOS · hardlinks with break-on-write
Unavailable
APFS copy-on-write
Unavailable until Apple grants the EndpointSecurity permission and the mode is validated.
Watching file opens on macOS needs Apple's EndpointSecurity permission, plus signing, a configuration profile, a system extension, and user approval. Only this mode would share one file copy and one page cache; clone mode does not.

Unavailable

You can read how it works while we finish it.

Arivaran Git is not publicly available yet. No install command is published until signed downloads, automated safety checks, and a safe rollback path are all ready.

View release status

Release requirements

You can review Arivaran Git today, but public installation stays unavailable until every requirement below is met.

Public, immutable release channelBlocked
Installer verified before it asks for admin rightsBlocked
Complete Linux safety bundleBlocked
Automated install verificationBlocked
Interrupted-upgrade and rollback coverageBlocked

Documentation and animations follow the same checklist, so they cannot show a command early.

Platform support and public availability are separate.

linux-x64Not yet released
linux-arm64Not yet released
macosNot in the public release
windowsNot in the public release

Clone once. Give every agent an isolated worktree.

Arivaran Git

Mechanism

Platform state

Limits

What we claim depends on the mode, not just the platform.

Linux · hardlinks with break-on-write

Windows/NTFS · Microsoft-signed driver

Windows/NTFS · user-mode fallback

macOS/APFS · clone mode

macOS · hardlinks with break-on-write

Release requirements

Platform support and public availability are separate.