agent-kickstartClaude Code onboarding
A guided, project-local first experience for Claude Code beginners.Evidence boundary: Candidate entry point; fresh-machine, cross-platform, and privacy review remain open.
Open-source AI agent reliability toolsNine-product active core
Tools for the AI failures that surface after the demo.
The Hermes Labs open-source core is a workflow, not a wall of repositories: begin with a project-local setup, inspect language before runtime, observe live behavior, evaluate changes, and preserve the context behind decisions. Each tool below names the boundary of what its present evidence supports.
Follow the path: start → static checks → runtime → evaluate → memory
See also: research and evidence · upstream contributions
§ 01
Active public core
Tool · role
Purpose · evidence boundary
Install · source
StartOne guided entry point
Static checks & drift gatesStatic analysis and drift preflight
lintlangRelational agent-language linter
Deterministic static analysis for agent instructions, including H1.6 pairwise differentia: comparisons of tool descriptions within one parsed input that report when one or both lack distinguishing wording. Zero LLM calls.Evidence boundary: H1.6 uses a finite term-and-synonym model and does not establish runtime tool-selection improvement; a clean scan does not prove runtime safety.Public evidence: 3,000+ PyPI downloads · recurring CI in Character.AI's public Larch repository · independent Gentoo packaging · attributed product influence on Agent Lint
hermeneuticCorrection-aware drift gate
Mines corrections from chat logs (prior response, user correction, repair) and runs a preflight gate on the next response.Evidence boundary: A drift check, not proof that the proposed response is correct or complete.
Observe at runtimeExperimental probes and policy monitoring
little-canaryExperimental prompt-injection preflight
Probes untrusted input with a sacrificial canary model before the primary model acts.Evidence boundary: Experimental security tool; efficacy and false-positive behavior depend on the models and evaluation distribution.
agent-gorgonRuntime policy guard
Scores observed file, network, and subprocess behavior against policy and records forensic evidence.Evidence boundary: Reactive user-space monitoring; it is not a sandbox or a prevention guarantee.
Evaluate and reviewEvidence-first scoring
hermes-rubricEvidence-first review protocol
Builds structured rubrics, binds scores to cited evidence, and records reproducibility receipts.Evidence boundary: Advisory, not a binary release gate; the published agreement result still needs independent reproduction.
Memory & recoveryLocal memory, session recovery, and a compact reference track
Fidelis MemoryLocal-first agent memory
Returns your original stored passages verbatim, with no LLM call in the default retrieval path.Evidence boundary: Published on PyPI as fidelis-memory; the repository, import name, and CLI remain fidelis. Independent install-to-recall proof remains open.
hermes-blindSession recovery scaffold
Extracts turn-one goals from Claude Code or Codex session logs into a compact anchor for long-task reorientation.Evidence boundary: Deterministic mission representation, not automatic drift detection or proof of improved model behavior.
zer0dexMemory reference implementation
A compact dual-layer memory pattern combining a human-readable index with vector retrieval.Evidence boundary: Teaching and reference track; benchmark implications are not independently reproduced.
§ 02
How to read this catalog
01
Inspect the evidence
Repository-level truth
A public repository is an inspectable artifact, not a claim of production fitness. Read its README, limitations, tests, and release history against your actual environment before adoption.
02
Separate kinds of proof
Local · live · independent
Local tests, a public package, a benchmark, and independent evaluation answer different questions. The boundary on each tool names material work that remains before a stronger claim is fair.
03
Use the research as context
Concepts · methods · limits
The research index provides the conceptual and empirical work behind Hermes Labs. It informs the engineering program; it does not certify every tool or deployment.
The wider organization remains available for historical and secondary source inspection. Those repositories are not part of this active core. Browse the full GitHub organization