Plugins
Every plugin, in three groups. All of them write ordinary code into your project, and all of them come back out with one command.
Built into the CLI, maintained with the framework, tested on every release.
grit plugin listBoards, columns and cards, dragged with a pointer, a finger or the keyboard.
grit plugin add kanbanOrganizations, per-org roles, and query scoping a forgotten WHERE cannot leak past.
grit plugin add multitenantAn MCP server for your app: an agent held to the same permissions and audit trail a person is.
grit plugin add mcpSign in as another user to reproduce their bug, with an audit trail of every swap.
grit plugin add impersonateCtrl+K to anywhere in the admin, built from the resource registry.
grit plugin add command-paletteA table’s filters, sort and search saved as a named view, per user.
grit plugin add saved-viewsSign in a browser by scanning a code from a phone that is already signed in.
grit plugin add device-pairingNotifications to the Expo app through Expo, so no certificates reach the API.
grit plugin add pushClips converted by ffmpeg to an MP4 and a poster every client can play.
grit plugin add videoCheckout and billing, with webhooks that survive a redelivery.
grit plugin add stripeOutbound webhooks to the Standard Webhooks spec, signed and retried.
grit plugin add webhooksLarger pieces that ship as Go modules from grit-plugins. Installed with go get rather than grit plugin add, because they are libraries your code imports rather than code generated into it.
websocketsRealtime hub with rooms, presence and typing indicators
notificationsIn-app and push notifications with a delivery log
searchFull-text search across resources
stripeSubscriptions and recurring billing
oauthSign in with Google, GitHub and friends
i18nTranslated API messages and locale negotiation
videoVideo upload, transcode and playback
exportScheduled exports to CSV and XLSX
conferenceAudio and video rooms
go get github.com/MUKE-coder/grit-plugins/grit-websockets
Written by other people and listed here on request.
Listing is not endorsement
The review is deliberately shallow: that the repository exists, that it installs and removes cleanly on a fresh project, and that it is not obviously hostile. Nobody audits the code for you. A plugin writes files into your project and patches existing ones, so read what it did with git diff, the same as any dependency.
Installing one takes the repository directly. Grit names the source and confirms before cloning, and nothing from the repository is executed: it reads the manifest and writes the files that manifest names.
grit plugin add github.com/someone/grit-calendar
grit plugin submit prints the checklist and the submission link. Three commands on a freshly scaffolded project, and the third is the one people skip:
grit plugin add <your repo>installs without errorsgo build ./...compiles afterwardsgrit plugin remove <name>leaves the project compiling againRemoval replays the lockfile backwards, so it only works if every change the plugin made is one the lockfile recorded. A plugin that edits a file outside the injection mechanism installs fine and leaves wreckage when it is taken out.