Iris Git / Quickstart

Your first Hashtree remote

Keep using Git. The git-remote-htree helper adds support for htree:// URLs, so your terminal and coding tools can work with Hashtree repositories.

1. Install the helper

You need Git and Rust and Cargo. Build the CLI and Git remote helper with Cargo.

cargo install --locked hashtree-cli@0.3.1 git-remote-htree@0.3.0

Cargo installs the tools to its bin directory, usually ~/.cargo/bin. Make sure it is on your PATH.

A compatible pre-built installer is being prepared. Installation options →

2. Clone a public repository

In Iris Git, open a repository and choose Code to copy its clone command. For example, this is the Hashtree source repository:

git clone htree://npub1xdhnr9mrv47kkrn95k6cwecearydeh8e895990n3acntwvmgk2dsdeeycm/hashtree

Cloning needs access to repository announcements and a server or peer holding the data.

3. Add a remote to your own project

In an existing Git repository with at least one commit, use an unused remote name and choose a repository name. This example publishes a public repository called my-project:

git remote add hashtree htree://self/my-project
git push hashtree HEAD

self refers to the CLI’s local signing identity. If there is no identity yet, the helper creates one. This may be different from the account signed into your browser. Keep a secure backup of your signing keys.

Your existing origin remote stays in place. To publish later commits, run git push hashtree HEAD again.

4. Check the result

Open the published repository in Iris Git. Use its Code menu to clone it into a fresh directory. Compare git log -1 in both copies to confirm the expected commit is available.

For direct peer-to-peer sharing, run htree start in another terminal. Git operations use the local daemon when it is running. Keep an available copy of your data; publishing a name alone is not a backup.

For humans and coding agents

Use the same Git commands with your own signing identity. The complete first-use guide walks through a first push, shareable URL, and an independent clone. For an installable skill and supported agent setup, see Git for agents.

Private or link-visible repositories?

Choose visibility before the first push. The helper documentation covers #private and #link-visible, including the extra key setup for secret links. Anyone with a link-visible repository’s secret link can read it.

Read how it works → · Compare with GitHub →