Contributing

How to contribute to Hanzo across open-source code, documentation, and HIPs — and join the community on Discord.

Thank you for helping build Hanzo. Every repository in the hanzoai and hanzo-docs organizations welcomes bug reports, pull requests, documentation fixes, and architectural proposals.

Community & Discussions

Join the Hanzo community on Discord. All contributor onboarding, engineering discussion, HIP drafts, and documentation feedback happen on Discord rather than GitHub Discussions so maintainers and contributors stay in one place:

#docs — broken links, missing pages, or confusing steps on docs.hanzo.ai
#hips — architectural and protocol proposals for hips.hanzo.ai
#general — engineering discussion, questions, and contributor onboarding

Ways to Contribute

Code & Bug Fixes (`hanzoai/*`)

Report a bug. Open an issue in the relevant repository on github.com/hanzoai with reproduction steps, what you expected, and what happened.
Fix a bug or build a feature. Pick an open issue on hanzo.ai/bounty or across github.com/hanzoai. For anything larger than a small fix, open an issue or ask on Discord first so a maintainer can confirm the direction before you spend your time.
Submit a pull request:
1. Fork the repository and branch from main. Keep the change small and focused.
2. Run the repository's tests and linters before pushing — its README.md or LLM.md states the exact commands.
3. State what changed and why, and link the issue.

Documentation (`docs.hanzo.ai`)

Clear documentation is part of the product. If you spot a broken link, a missing page, or a confusing step:

Drop it in #docs on Discord, or
Open a pull request against hanzo-docs/docs.

Before authoring or editing docs pages, read Style for house rules (https://api.hanzo.ai/v1, sk- and pk- keys, one canonical way per task) and Docs Architecture for how docs.hanzo.ai is sourced and built.

Standards & Proposals (`hips.hanzo.ai`)

Hanzo Improvement Proposals (HIPs) specify Hanzo's architecture, protocols, and standards. Published proposals live at hips.hanzo.ai from hanzoai/hips.

Check hips.hanzo.ai first — if a HIP already covers the subsystem, update that HIP rather than duplicating it.
Copy docs/templates/hip-template.md in hanzoai/hips to HIPs/hip-<NNNN>-<slug>.md.

Run the index generator and linter locally:

python3 scripts/index.py
python3 scripts/lint-hips.py

Open a pull request on hanzoai/hips and share it on Discord.

Rewards

Merged contributions earn points on Hanzo Rewards: what counts and what each earns is listed at hanzo.ai/bounty, and standings are at hanzo.ai/leaderboard. Maintainers decide what is awarded. Low-effort or automated submissions earn nothing and may be closed.

Security

Never report a vulnerability in a public issue or on Discord. Email [email protected].

Docs Guides

Style

How code and prose are written here — one base URL, one key, one way to do a thing — and the traps that keep catching agents working in this repo.

Docs Architecture (ADR)

The one and only way Hanzo documentation is sourced, built, and joined into docs.hanzo.ai. Hub-and-spoke over a single unified build.

User Guide

The CLI tool that automates setups and installs components.

Preview

A light tool to view Markdown files.

Was this page useful?

Broken link or missing step? Drop it in #docs on Discord or open a PR.

PreviousReferral & Affiliate Program NextStyle

Last updated Nov 7, 2026