Settings reference

This page lists the pages in Settings and every setting in the settings file. To change the look step by step, see Change how Hivemind looks.

Using the Hivemind settings reference, change the setting I describe.

1. Find its dotted path on the reference page, for example `views.layers.groupBy` or `appearance.glass.blur`, and its allowed values.
2. Show me the current value: `hive config get <path>`.
3. Set it: `hive config set <path> '<JSON value>'`. Text goes in double quotes inside single quotes (`'"status"'`). Numbers, `true` and `false` go as they are.
4. If it is refused, show me the message. Never edit the file by hand.

At the end, show the new value with `hive config get <path>` and the command that sets it back.

REFERENCE https://hivemind.griiken.com/guide/settings.md

Settings pagesCopy Anchor Link

Open Settings from the gear at the right end of the toolbar, or at the foot of the Layers panel.

Each plugin also has its own page under Plugins, with Settings, Read me and What it can do.

The settings fileCopy Anchor Link

Everything is one file you own. The app and the hive command both read and write it, and it is checked each time. A value out of range is set to the nearest allowed one; an unknown value falls back to its default. hive config set refuses a path that is not a setting, and lists the settings there. It also refuses a <view> that is not a view's id, a <kind>:<id> that is not a plugin's, and a key under either that is not one of its settings. A plugin's option ids are checked only as ids there; hive plugins set checks them against the plugin's own settings.

A change writes only the settings it changes. Everything else in the file stays as it is, so a newer version and this one can share the file:

• A key this version does not know stays, wherever it is: at the top of the file, in a section, or in a group such as appearance.glass.
• A value this version does not know, such as a newer accent's, mode's or wallpaper's id, reads as the default here and stays in the file until you set that setting here. A preset's id is kept as written: one this version does not know shows as Custom.
• Choosing a preset writes its colours, accent and mode, whatever they read as here. Importing a theme writes only the keys its file names.
• v is the file's format. A file from a newer version is read for the settings this version knows, and keeps its v; hive config get says so. A file without v is read as format 1. v is not a setting: the app keeps it.

hive config path                              # where it is
hive config get appearance.glass.blur         # one value, as JSON
hive config set appearance.glass.blur 12      # a JSON value; the app reloads
hive config set views.layers.groupBy '"status"'

appearanceCopy Anchor Link

A view you installed is told your fonts. It draws a theme's fonts, the fonts it ships and the fonts your computer has (how).

appearanceExtraCopy Anchor Link

The parts of the look an older Hivemind does not know. They sit in their own key, so a write by an older app or hive keeps them, and appearance.accent keeps a built-in id that older builds read. Each part is set whole.

hive config set appearanceExtra.accent '{"brand":"#c08552","accent":"#d9a273"}'

viewsCopy Anchor Link

The views.layers values are what the Layers panel's View menu sets.

agentsCopy Anchor Link

pluginsCopy Anchor Link

notificationsCopy Anchor Link

Change them on Settings → Notifications (Know who is waiting), or with hive notifications set or hive config set. Both refuse a path not listed here and a value not of its kind. Only the person changes them: an agent is refused.

profile, network, browserApp, quitCopy Anchor Link

Last validated for Hivemind 2026.10.3.