Proposed scope | Draft prepared Nov 17, 2026
Proposed by Jon Komet

Build the Hermes community

A proposed Community Manager scope connecting developer community, hands-on building, and creative experiences.

Jon would like to contribute across community, developer tools and plugins, and creative work including merch and accessories. The final title, scope, priorities, capacity, and compensation remain open for discussion.

Proposed title directions

Possible title directions to discuss. Each one lists the kinds of work it could naturally include. This is a starting point, not a list of duties. The final title is still open.

Title direction

Community Manager

  • Socials, Discord, and support help
  • Events, online and in person
  • Broader community activity
  • Plugins, tools, and creative work, as agreed with Sam

Title direction

Technical Community Manager

  • Discord and support, with developer help
  • Plugins, integrations, and guides
  • Builder-focused events and demos
  • Creative work as agreed

Title direction

Developer Community Manager

  • Developer Discord and support
  • Developer events and sessions
  • Guides, examples, and feedback for the product team
  • Plugins and creative work as agreed

Title direction

Community and Developer Relations Manager

  • Socials and events
  • Developer advocacy
  • The feedback loop between the community and the product team
  • Plugins and creative work as agreed

This is a proposed role direction for discussion. Sam is the reported manager. Decision-making and priorities are still to be clarified.

Three areas, to agree with Sam

Community and events

Socials, Discord, support help, and events, online and in person.

  • Socials and Discord activity
  • Support help for community members
  • Events, online and in person, with priorities agreed with Sam

Developer experience

Plugins, integrations, and guides, and turning developer feedback into product signal.

  • Plugins and integrations, scoped together
  • Guides, examples, and demos
  • Developer feedback passed to the product team

Creative direction

Merch, accessories, and event materials.

  • Merch and accessory design
  • Event graphics and materials
  • Budget, approvals, production, and fulfillment confirmed before any work starts

Published work

Aether catalog cover

Aether

Living themes for Hermes Desktop. A Hermes Desktop plugin, MIT licensed. Public GitHub repo.

Trophy Room catalog cover

Trophy Room

Achievements for Hermes Desktop. 120 illustrated trophies across 18 categories, earned from real Hermes work, with collectible cards and unlock pop-ups. Runtime-tested on Windows. MIT.

Derived in part from hermes-achievements by PCinkusz (MIT), which provides the 60 original achievement definitions.

Cadence catalog cover

Cadence

A local usage page for Hermes Desktop: year heatmap, streaks, and model mix. Reads local data only, with no network calls. Merged into the Hermes catalog. MIT.

Community and events

Hermes Agent Meetup, Bangkok

Held Friday, September 25, 2026 at Cleverse, Bangkok. Hosted by Jon Komet. Free and RSVP-based, with live demos of Hermes Desktop and the Hermes Browser Extension. Per the Luma listing, Nous Research was the official sponsor, with a merch giveaway and compute-credit raffle listed.

Event graphics

Flyers, invite cards, and ad graphics for the Bangkok meetup.

Merch and creative concepts

Merch and accessory concepts

Proposed, not shipped. Merch and accessory concepts for the Hermes community. Any design, budget, approval, production, and fulfillment step gets agreed in writing before work starts.

How we could work together

  1. 01Start with a trial period. Its length and terms are agreed in writing before work begins.
  2. 02Choose the specific projects from the three areas together.
  3. 03Confirm the reporting line, decision-making, and priorities with Sam. Agree success criteria before the start.
  4. 04Agree hours, budget, approvals, and payment terms in writing before work starts.

Outside the default scope

Not included unless agreed in writing: around-the-clock support, ongoing maintenance after a prototype ships, vendor production or fulfillment, inventory, travel without an approved budget, and ownership changes for existing work.