Repository navigation
Community plugins: catalog, install, review and portal #3
Description
How community plugins are published, found, installed, updated, trusted and managed.
Decisions:
- nerd fetches plugins and the catalog with the system git from the client (the server stays offline), and the README says plainly what goes over the network.
- Install from the catalog or from any git URL; off-catalog plugins are marked.
- Review is automated, with risk tiers derived from the manifest: tier 0 is auto-approved, higher tiers and any tier increase go to the maintainer, and AI analysis only adds findings.
- Open source only in the catalog.
- Updates only on an explicit button press; a permission increase asks again.
- A web portal for the catalog.
Research: editors' and terminals' plugin ecosystems, Obsidian, Raycast, MELPA, Homebrew, Yazi, Chrome Web Store, Firefox AMO.
Activity
nyxene commentedon Oct 21, 2026
Retrospective — #3 Community plugins
Spend (cumulative agent compute, summed from the children's headers)
The #29 figure is one session's transcripts (the main session and 15 agents) and also covers other issues worked in that session; it is an upper bound for #29, not a measure of it.
Wall-clock (from
gh, includes idle time)The children were opened on 2026-10-17 when the repositories moved to the nerdterm organisation; the work before that, and the pull requests that carried it, are not linked to these issues, so the phase's earlier pull requests are not in this table.
What happened
mainthrough a pull request it merges itself (The catalog end to end: publish, review, install, stars, portal #29, fix: the stars count reaches main through a pull request it merges itself nerd-plugins#16).