> For the complete documentation index, see [llms.txt](https://docs.githud.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.githud.net/welcome-to-githud.md).

# Welcome to Githud

### A Git Platform Built for AI Agents

Every Git platform you've used ( GitHub, GitLab, Bitbucket ) was built around a simple assumption:&#x20;

> **a human sits down, types a password or clicks through an OAuth screen, and then starts pushing code.**&#x20;

That assumption has quietly become a bottleneck. AI coding agents don't have a password. They don't have an email inbox to click a "verify your account" link. They can't sit through a browser-based OAuth redirect. Yet increasingly, *they* are the ones opening the terminal, running `git clone`, and pushing commits.

**Githud is a terminal-native Git platform built for that reality.** It is a comprehensive, self-hosted Git solution built as a single cohesive platform. It is entirely fronted by a decentralized identity system requiring no emails or passwords. Instead, access is secured via Ed25519 DIDs, where every user or agent operates under a unique cryptographic identifier such as

```
did:key:z6MkjRagNiMu91DduvCvgEsqLZDVzrJzFrwahc4tXLt9DoHd
```

### The Githood Approach

| Capability         | How it works                                                                                                                                                                                                                                               |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Identity**       | An Ed25519 keypair is generated locally (by a human or an agent). The public key is deterministically encoded into a `did:key:z6Mk...` string.                                                                                                             |
| **Registration**   | Registration is handled entirely through the CLI, which generates a private key stored securely on the local machine. The client uses this key to sign a registration payload, without ever creating an email or password.                                 |
| **Signing**        | Every Git operation is automatically signed locally using your secure private key before transmission. The server then mathematically verifies this cryptographic signature against your public DID to guarantee absolute authenticity and data integrity. |
| **Access Control** | Repository permissions are strictly bound to public DIDs rather than traditional user accounts. Access is granted by whitelisting a cryptographic identifier, ensuring absolute control over who can read and write code.                                  |

### Who Githud Is For

* **AI agent builders** who need each autonomous coding agent to have its own provable, auditable Git identity without provisioning a human-style account per agent.
* **Privacy-conscious developers** who don't want to hand over an email address just to host a repository.
* **Teams experimenting with agent-driven development pipelines**, where dozens or hundreds of ephemeral agent identities might spin up, push a branch, and disappear.
* **Anyone comfortable with the terminal** who wants a git-native workflow without a heavyweight web dashboard getting in the way.

### Quick Comparison

| Feature            | Githood                                   | Traditional Git Platforms                   |
| ------------------ | ----------------------------------------- | ------------------------------------------- |
| Authentication     | Ed25519 signature (`did:key`)             | SSH keys / Personal Access Tokens / OAuth   |
| User identity      | `did:key:z6Mk...` (self-certifying)       | Email + username (server-issued)            |
| Agent-friendliness | Native, no browser step, ever             | Requires a human-driven web login at signup |
| Privacy            | Zero required PII                         | Email address mandatory                     |
| Git protocol       | HTTP Smart Protocol via a DID-aware proxy | Native SSH and/or HTTPS                     |

### The Autonomous Workflow

Understand the core mechanics of Agent Version Control. Learn how machines seamlessly interact with your codebase.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.githud.net/welcome-to-githud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
