hermes-harness

Every repo is a world model. Mine git history for lifecycle patterns — what broke, what fixed it, what went back and forth. Query across repos in milliseconds.

npm install -g hermes-harness
hermes-harness seed-query "dependency version conflict"

# → 48% match: "Playwright version roll" (playwright-go)
# → 28% match: "dependency bumps and fixes" (chatbot-ui)
# → Cross-repo, 11 public repos indexed

Install

# Requires Bun (https://bun.sh)
npm install -g hermes-harness

# Or from source:
git clone https://github.com/vystartasv/hermes-harness
cd hermes-harness
bun install

Usage

🪴 Use the seed (public repos, no setup)

# Query across 11 pre-harvested OSS repos
hermes-harness seed-query "your error message here"

🌍 Create your own world model

# Clone + mine public OSS repos (langchain, nextjs, svelte, vite, ...)
hermes-harness seed-harvest

# Export for sharing or redistribution
hermes-harness seed-export

🔍 Cross-repo search

# Search across ALL your repo models
hermes-harness repo-query "build fails on CI"
# → 45% match: "npm install EPIPE" (hermes-agent)
# → 38% match: "staging deploy fail" (tickets repo)
# → 30% match: "build failure npm" (craftbot)

🤖 Self-improvement loop (runs every 30min)

hermes-harness self-improve

How it works

1. Harvest — clones repos, reads full git history (subjects, bodies, files, parents)
2. Extract — reverts, file coupling, topic clusters become lifecycle patterns
3. Compress — each pattern becomes a 128-dim word-count vector
4. Query — cosine similarity against all vectors, results in milliseconds

No AI at query time. Once trained, it's pure arithmetic. Runs on your laptop.

Data directory

All data lives in ~/.hermes-harness/. Override via HARNESS_DATA_DIR env var.

~/.hermes-harness/
├── models/           # World models (compressed vectors)
│   └── world-model.json
├── repo-models/      # Per-repo lifecycle patterns (human readable)
├── patterns/         # Extracted pattern files
├── seed-repos/       # Cloned repos (git clone --depth=500)
└── seed-world-model.publish.json  # Exportable seed (no private data)

Who this is for

Tech leads and platform engineers managing 5+ repos who want to stop repeating lessons. If you've ever said "we fixed this last quarter" and couldn't find the ticket, this is for you.

Status

Shipping. Functional seed (21 patterns, 11 OSS repos). Active development. The architecture works. The model needs more data — that's where you come in.

Contribute

See CONTRIBUTING.md. Quick ways to help:

• Run seed-harvest against your favorite OSS repos and share the export
• Add a new miner (Slack, calendar, browser history)
• Open an issue with a query that should have returned something but didn't

License

MIT