Contact
Horde is maintained by Andrew Somervell. There is no support queue and no sales team — the routes below all reach the same person, so pick whichever fits what you need.
Bugs and feature requests
Open an issue at https://github.com/gethamster/horde/issues. This is the preferred route for anything reproducible, because the discussion stays attached to the code. Include your Horde version from horde --version, your operating system and architecture, the executor you configured, and the relevant lines from daemon.log in your data directory (~/.local/share/horde by default).
Write to andrew@tryhamster.com for security reports, licensing questions, or anything you would rather not file in public. Security reports get priority; please do not open a public issue for a vulnerability until it has been addressed.
Business address
425 2nd St STE 500
San Francisco, CA 94107
United States
Public repositories
- Source code — Horde’s public Apache-2.0 repository
- Release manifest — the latest version, artifact URLs, and checksums
- Agent skills — the Horde skills for the Agent Skills Protocol
Source code, release metadata, and agent skills are all publicly available.
For agents
If you are an automated agent looking for a programmatic contact route, the MCP manifest carries the same email and issue tracker in its contact object, and /llms.txt lists them alongside the rest of the published descriptions.