Packages

Start the package

hive plugins new package kit

It writes kit/ with a hivemind-package.json that holds nothing yet, a README.md, and a PROMPT.md to hand your coding agent. Its owner is the GitHub login gh is signed in as, or the one you pass with --owner.

Add members

Start each member inside the package. It is named in hivemind-package.json for you, with the package's owner:

hive plugins new tool prs --in kit        # kit/tools/prs
hive plugins new widget dog --in kit      # kit/widgets/dog
hive plugins new view board --in kit      # kit/views/board, named by its dist/
hive plugins new wallpaper pond --in kit  # kit/wallpapers/pond
hive plugins add ../counter --to kit      # copied to kit/widgets/counter

add takes one you already wrote. It refuses a plugin whose id is not yours (@you/<name>), and changes nothing. Each new member has its own PROMPT.md with the guide of its kind: tools, widgets, views or live wallpapers. For a view or a live wallpaper, run npm install once where its package.json is.

Check it

hive plugins check kit

It checks hivemind-package.json, then every member with that member's own check: its types, its manifest, and its code drawn once. A view is built first. Each problem has its file and line: a member's in its own folder, and a misspelt member path or a member with someone else's id at the line of hivemind-package.json that names it.

Check: it ends with ok: package @you/kit. --json gives the same report to an agent.

Install it

hive plugins install ./kit

It prints the package and each member it holds, with what each asks for. Install again after each change. --dry-run shows what would change, member by member, and installs nothing.

Switch it on

A package that holds a tool or an agent preset arrives off. Switch it on once you trust what it runs:

hive plugins enable @you/kit
hive ctl plugin open tool:@you/prs     # or widget:… or view:…
hive ctl tile look <tile>              # what a tool drew, and what its code logged

In the app, it is one row in Settings → Plugins, with one switch.

To open a view as soon as the package is in, name it in hivemind-package.json: "startup": { "view": "@you/board" }. Once the package is on, the app asks Open Board?, and Open shows it. Settings → Plugins asks under each install it makes. After hive plugins install, the app asks in the corner of the window, at once if it is open, or the next time it starts. It asks there once per view: an update or a rollback to a view it offered before does not ask again.

The app never switches the view without you, since an agent may be the one installing. To switch at once from a terminal, run the command the install prints: hive ctl plugin open view:@you/board. --json gives it as startView.open.

A package's view brings the package's widgets. The first time a workspace shows the view, however it was opened, each of the package's widgets that is on goes down the edge the view keeps for widgets ("widgets": "left" in its hivemind-view.json, or the right). They show over that view alone, so the canvas and your other views stay clear. To have one over every view, point at it, or Tab to it, and press its pin, Show on every view. An agent runs hive ctl plugin open <its id>; hive ctl plugin list names each widget and the view it shows over. Hide widgets, in the bottom-right corner, hides them over the view you are in, and each view keeps its own choice.

A widget you close with its × stays closed, unless you press Undo on the notice that says it was removed, before you switch workspace: the view never brings it to that workspace again, in any window. One that a later version of the package adds comes when the view shows: at once if it is open. A workspace where you had already put some of the package's widgets is left as you arranged it. So the install's next does not list them: hive ctl plugin open widget:… adds another copy, over every view.

To offer one of its live wallpapers as the background, name it the same way: "startup": { "wallpaper": "@you/kit/pond" }. It must be one of the package's own. The app offers it once, and never switches without you; --json gives the command as startWallpaper. See Make a live wallpaper.

Update it

Change a member, raise version in hivemind-package.json, check, and install again. When a change needs your trust again, the package goes off, and the install lists what changed.

Roll back

hive plugins rollback @you/kit

It puts back the version in use before the last update, switched on or off as it was.

Publish it

Commit the package folder, with each view's dist/, and push it to GitHub. Then:

hivehub publish kit

It shows the package, each member, where its code runs and what it asks for, and publishes when you answer y. Anyone can then install it with hive plugins install @you/kit. Getting the hivehub command and signing in are in Publish to HiveHub.