The README section was gated on `readme: true` in the catalog YAML and no entry set it, so
all 222 plugin pages shipped without one. READMEs now render for every GitHub/GitLab entry
(fetched at the reviewed sha, subdir first then repo root, common casings and docs/README.md
as fallbacks); `readme: false` opts an entry out. Build proof: 222/222 READMEs rendered.
/docs/plugins/<name> and /docs/plugins/by/<maintainer> are generated at
build time by a small Docusaurus plugin (website/plugins/plugin-catalog-pages)
from the same plugins.json the grid fetches, so a merged catalog PR is the
only way a page appears or changes.
Plugin page: full description with the Disclosure sentence pulled into a
callout, pinned commit / version / platforms / requires facts, tools, hooks
and env chips, Desktop install button + CLI command, repository and reviewed
source links, optional screenshots gallery, optional README rendered from the
PINNED commit (fetched at build, allowlisted HTML, raw HTML dropped, relative
links and images resolved against the pinned tree), and a "More by this
author" shelf. Author page: everything a maintainer has in the catalog with
total stars and a profile link when all repos share one owner.
Cards on the grid link through: the title is a link and a card click opens
the page (the Desktop picker embed keeps expanding in place). The shared
vocabulary (entry type, tier/category taxonomy, link builders) moved to
src/components/PluginCatalog/catalog.ts so the three surfaces cannot drift.
Docs: field table and catalog README describe screenshots:/readme: and the
pages.
Merge cdp-manager fix (config.json into plugin dir, LOCALAPPDATA-derived
default profile, public REPO_URL) and set platforms: [windows]; profile
paths description now says local app-data directory instead of Hermes home.
Small thank-you to @teknium1 and the team for adding bridge-adapter to the plugin catalog — great to see it in the #plugins-skills-and-skins sweep. This bumps the pinned sha from 406a53d to the current main (3615cc9), so catalog installs pick up the new README covering hermes_bridge_sdk and the Plugin Catalog install instructions.
Bumps the pinned commit from 88939ad → 42afc81 and version 0.1.1 → 0.1.2,
reflecting the hardening release (profile-name validation + narrowed MEDIA roots)
and the v0.1.2 tag on lvabarajithan/hermes-cron-bulletin.
Claude Code installs natively on Windows; the only POSIX-only piece was the
plugin's own process-group cleanup, which 0.3.0 makes portable (taskkill /T,
CREATE_NEW_PROCESS_GROUP, resolved claude.cmd path, inherited SystemRoot).
Its suite now runs green on ubuntu/macos/windows runners against current
hermes-agent main, so the platforms restriction goes and the pin moves to
c92c27c. The 2:1 card is the plugin's house-style (nous-technohellenic) art.
The provider extracted from #105863 lives at
NousResearch/hermes-plugin-claude-subscription-directsdk; this pins fa920cbb so
`hermes plugins install claude-subscription-directsdk` resolves through the
reviewed catalog (sidecar, pinned checkout, no "unreviewed source" warning)
instead of tracking the repo's main. It needs the external-process provider
seams from #117451, hence requires_hermes >=0.21.4 (the first release carrying
them). POSIX-only: the transport uses process groups.
Bumps sha to a6cf35afc3ca607271284844ee79c60ee4083296 (tag v0.4.5),
which carries the review fix: catch-all allow patterns refused at YAML
load and in `add --type allow` unless forced interactively.
🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
