Publish a plugin

Publish a plugin when it works for you and you want others to install it from Settings → Plugins. HiveHub lists it; your GitHub repository keeps the files. How a listing works: What HiveHub is.

Publish the Hivemind plugin in the folder I name on HiveHub.

1. Read its manifest (`widget.json`, `hivemind-view.json` or `hivemind-tool.json`). Check it has an id in my GitHub account (`@login/name` for a widget or view, `login/name` for a tool), a `version`, a one-line `description` and a `category`. Check `README.md` says what it does and what it asks for. For a view, publish its built `dist` folder.
2. If it is an agent (`agent.yaml`), stop: agents are listed by pull request to the GitHub repository dip497/hivemind-plugins, in `agents/<id>/`. Ask me before opening one with `gh`.
3. The folder must be in a git repository whose `origin` is on GitHub, and I must be able to push to it. Ask me which repository if there is none. Commit, then push. HiveHub publishes the pushed commit, never the disk.
4. Get the `hivehub` command if `command -v hivehub` finds nothing: `curl -fsSL https://hivehub.griiken.workers.dev/hivehub.mjs -o ~/.local/bin/hivehub && chmod +x ~/.local/bin/hivehub`. It needs Node 20 or newer.
5. Run `hivehub whoami`. If I am not signed in, run `hivehub login`, show me the link and the code it prints, and wait while I open the link and type the code myself.
6. Run `hivehub publish <folder>` without `--yes`. Show me the preview: id, version, files and what it asks for. Add `--yes` only after I agree.
7. Check: it prints `Published <id>` and the plugin's page on HiveHub.

At the end, give me the plugin's page on HiveHub, and tell me others install it from Settings → Plugins, on the HiveHub tab.

REFERENCE https://hivemind.griiken.com/guide/publish-to-hivehub.md

Before you startCopy Anchor Link

• Your plugin works: hive plugins list shows it on, with no problem.
• Its id is in your own GitHub account: @you/name for a widget or view, you/name for a tool. Nobody can publish into someone else's account, and an id stays with the account that first published it.
• Its folder is in a public GitHub repository you can push to, and within HiveHub's limits.
• You sign in with GitHub to publish: Signing in to HiveHub.

Get it readyCopy Anchor Link

Then publish it in one of three ways: the web form, the hivehub command, or GitHub Actions.

From the web formCopy Anchor Link

From a terminalCopy Anchor Link

curl -fsSL https://hivehub.griiken.workers.dev/hivehub.mjs -o ~/.local/bin/hivehub && chmod +x ~/.local/bin/hivehub

hivehub login

hivehub publish ./counter      # a widget or tool folder
hivehub publish dist           # a view: its built folder

From GitHub ActionsCopy Anchor Link

Store a GitHub token as the repository secret HIVEHUB_TOKEN. Its account publishes the plugin. Which token to make: A token for CI. Then add a workflow:

name: Publish to HiveHub
on:
  push:
    tags: ["v*"]
jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: |
          curl -fsSL https://hivehub.griiken.workers.dev/hivehub.mjs -o hivehub
          node hivehub publish ./counter --yes
        env:
          HIVEHUB_TOKEN: ${{ secrets.HIVEHUB_TOKEN }}

The job publishes the commit it runs on. --yes answers the question, because a job has no one to ask. Any other CI works the same way with HIVEHUB_TOKEN set.

Signing in as the job's own repository, with no token stored, works today only for dip497/hivemind-plugins on main: see GitHub Actions.

Publish an agentCopy Anchor Link

Agents are listed by pull request to dip497/hivemind-plugins: one folder per agent, agents/<id>/, with its agent.yaml and a README.md. An agent's id is one name, such as gemini, so each name means one program. Once the pull request is merged, that repository's workflow publishes it. Hivemind then adds it on any computer where its program is on the PATH. How to write one: Add your own agent.

Publish a packageCopy Anchor Link

A package publishes as one listing with every member: commit it with each view's dist/, push, and run hivehub publish <package folder>. See Packages.

The listing holds the package's hivemind-package.json, its README and licence, and the files in its members' folders. A file beside them, such as a build script or the sources a view's dist/ is built from, is left out, so nobody downloads it.

The oldest Hivemind it needsCopy Anchor Link

HiveHub works this out for you. A manifest field that is newer than some apps (a view's widgets or tokens, a package's themes) makes the listing need the Hivemind release that first reads it, and a package needs the newest of its members. Those three need 2026.10.6; a package's wallpapers (live wallpapers) need 2026.10.8. An older app says "needs Hivemind 2026.10.8 or newer" before it downloads anything. An agent or a tool says it itself with minAppVersion in its manifest.

What people see when they install itCopy Anchor Link

The card shows your plugin's name and your one line. Before anything is added, people see what it adds and what it asks for. That list comes from your manifest, not from the form. Its page in Settings → Plugins shows your README under Read me, and your account and version. A tool arrives switched off, and so does every update to one. The whole install: Install from HiveHub.

Publish an updateCopy Anchor Link

Raise version, commit, push, and publish again. If you leave the one line empty, the card keeps the line it has. Everyone who has the plugin sees Update on the HiveHub tab.

If it didn'tCopy Anchor Link

ReferenceCopy Anchor Link

• The hivehub command: every command, flag, message and exit code.
• Signing in to HiveHub: every way to sign in, and how to revoke it.
• HiveHub API: the publish route, its errors and its limits.

Last validated for Hivemind 2026.10.3.