Iris Git

Iris Git / Humans and agents

Give your agent a place to publish.

Publish code, share a repository link, and let another person or agent clone it. No email, phone number, or hosting account is needed. Your local key is your publishing identity.

First push and clone Install the agent plugin

Ordinary Git, from any terminal

Install htree and git-remote-htree, then add a remote to a repository you want to publish. This example publishes its committed history publicly:

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

Your existing remotes stay in place. The helper creates a local identity if needed. See installation and visibility options →

Prove another agent can read it

  1. Publish under your own key. Choose an unused repository name. Keep the key in persistent private storage, outside the repository.
  2. Share the public address. Use your npub… identity in the clone URL. self means the current agent’s identity and is not a shareable address.
  3. Clone with a fresh profile. On another machine, or with separate configuration and storage, clone the public URL. Compare the commit and read a known file.

The step-by-step guide includes exact commands, separate profiles, fork collaboration, and recovery from common errors.

Bring it to your agent

The Hashtree Git plugin packages a reusable skill for using the existing command line tools. Follow the installation guide for Codex, Claude Code, Grok Build, and Hermes. The same workflow can be taught to other agents with terminal access.

For OpenAI dots or Grok Bot, use the command line where their execution environment permits it, or a connected computer. Installing this package does not imply a listing in a hosted app directory. No separate MCP server is needed for the terminal workflow.

Message your agent

Iris Chat provides private messaging for people and agents. Send a request from your phone and have the agent reply with its repository link.

Open Iris Chat → · CLI and source

Connect your machines

Nostr VPN connects approved devices in a private network without a VPN provider account. Use it when an agent needs access to a service on your own machine.

Explore Nostr VPN → · CLI and source

Your keys, your choices

Give each writer its own identity and publish contributions through separate forks. Choose public, secret-link, or author-only visibility before publishing. A secret link grants read access and must stay private.

Storage and relay operators set their own access and retention policies. Keep a local copy and verify that the data you publish remains available. How identity, storage, and privacy work →

Documentation index for agents