docs: third-party-product plugins ship standalone, not into core tree - #54001
Merged
Conversation
Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close.
Contributor
🔎 Lint report:
|
alt-glitch
added
type/docs
pai-scaffolde
pushed a commit
to pai-scaffolde/hermes-agent
that referenced
this pull request
Jun 28, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
waefrebeorn
pushed a commit
to waefrebeorn/slermes
that referenced
this pull request
Jul 2, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
Jasper6439
pushed a commit
to Jasper6439/hermes-agent
that referenced
this pull request
Jul 5, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
habarmc1223-sudo
pushed a commit
to habarmc1223-sudo/hermes-agent-fluxmem
that referenced
this pull request
Jul 8, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
santhreal
pushed a commit
to santhreal/hermes-agent
that referenced
this pull request
Jul 13, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
leewenjie
pushed a commit
to leewenjie/hermes-agent
that referenced
this pull request
Aug 7, 2026
…NousResearch#54001) * docs: third-party-product plugins ship standalone, not into core tree Generalizes the closed-set memory-provider policy to any plugin that integrates someone else's product/project (observability backends, vendor SaaS, analytics dashboards, paid-service tie-ins). These create an open-ended maintenance burden on us for backends we don't own, so they ship as standalone plugin repos installed into ~/.hermes/plugins/ and are promoted in #plugins-skills-and-skins — not merged into core. - AGENTS.md: new 'what we don't want' bullet + generalized policy note beside the memory-provider closed-set rule - CONTRIBUTING.md: new 'Third-Party Product Integrations' section - build-a-hermes-plugin.md: caution callout at the top of the guide It's a coupling decision, not a quality bar — a plugin can clear review and still be a close. * docs: add infographic for standalone-plugin policy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Third-party-product plugins ship as standalone repos, not into the core tree — and the developer-facing docs now say so explicitly.
This generalizes the existing closed-set memory-provider policy to any plugin that integrates someone else's product or project (observability/metrics backends, vendor SaaS connectors, analytics dashboards, paid-service tie-ins). Absorbing those into the tree puts an open-ended maintenance burden on us for backends we don't own and can't control, against a fast-moving core. The decision is about coupling and maintenance, not code quality — a plugin can clear automated review with a green approval and still belong in its own repo.
Changes
AGENTS.md: new "what we don't want" bullet for third-party-product integrations, plus a generalized policy note beside the existing memory-provider closed-set rule.CONTRIBUTING.md: new "Third-Party Product Integrations: Ship as a Standalone Plugin" section after the memory-provider one.website/docs/guides/build-a-hermes-plugin.md: a caution callout at the top of the guide so contributors see the placement decision before they start building.The guidance points contributors to publish standalone plugin repos (install into
~/.hermes/plugins/or a pip entry point), use the existing ABCs/hooks/ctxsurface (no core changes), and promote them in the Nous Research Discord#plugins-skills-and-skinschannel.Validation
/docs/guides/build-a-hermes-plugin(exists)Docs-only change; no code paths touched.
Infographic