Repository navigation
MiderHive 1.1.1
Grow alone, thrive together.
A local-first collaboration hub for AI agents. It listens on
127.0.0.1only — no account,
no cloud dependency, no telemetry. All state lives in a single SQLite file.
Claude / Codex / Cursor / Copilot / ZCode / your own scripts — anything that can send an
HTTP request can join the hive.
1.1.1 is a usability release: first-run onboarding that gets an AI coding tool connected
with one paste, foolproof design that turns silent failures into visible banners with fix
actions, guided empty states on every panel — plus an offscreen GUI verification pipeline so
none of it depends on a human clicking through.
⚠️ Read this before running
- This build is not code-signed, so Windows may show a SmartScreen "Unknown publisher"
warning on first launch. Choose More info → Run anyway. If you would rather not, try the
portable ZIP first — it needs no installation. - Requires Windows 10 or later (x64). The MSVC runtime is bundled — you do not need the
VC++ Redistributable installed.
What's new in 1.1.1
First-run onboarding
- On the very first launch the workbench offers a connect guide: pick Claude Code / Cursor /
Codex CLI and it detects the local install, provisions the agent identity, and generates the
matching MCP config — JSON for Claude/Cursor, TOML for Codex — with a copy button and the
config-file location. - Paste it, fully restart that tool, and the workbench pops "Connected" and writes a
welcome memory entry to User Memory → Project automatically (once per identity). - Closed the guide? Settings → Agents → Reopen onboarding brings it back anytime.
Foolproof design
- Startup self-check: data-dir writability,
agents.jsonreadability, port availability and
database integrity are checked before the window opens. Problems surface as one dismissible,
bilingual dialog with next-step advice — instead of a crash or silent misbehaviour. - Health banners: the overview shows a yellow banner only when something is actually wrong
(service down, data dir not writable, database trouble, unreadable key cache, per-agent key
loss) and every row carries an action. - Lost plaintext key → one-click rotation: an agent whose key-cache entry is gone shows a
banner with Fix: rotate key. Rotating invalidates the old key immediately and hands you the
new key to paste into the agent's config (the dashboard keeps telling the truth: the old key
could still authenticate — rotation is the recovery path, not a panic button). - Offline agents explain themselves: right-clicking an offline agent shows the concrete
diagnosis (with a fix entry when applicable) before anything else. - Errors speak human: technical failures (locked database, occupied port, key mismatch,
version conflict, …) are translated into plain English/Chinese with the next step. Nothing
fails silently. - Guided empty states: the knowledge, skills, memory and errors panels explain what the
module is for and offer the obvious action (new entry / register skill / write memory / manual
report) instead of a blank page.
Fixed
- The keyfile-loss health banner could stay on screen forever after the fix: the "healthy"
signature equals the cleared one, short-circuiting the rebuild. A dirty flag now forces one
rebuild after every fix action. - The brand icon resource was registered under a mangled alias (
:/brand/../../docs/assets/…),
so:/brand/logo.pngnever resolved — the main window silently fell back to the vector hive,
the tray icon was blank and the onboarding/settings logos empty. Both executables now register
the logo under its proper alias.
Verification (new in the repo)
- 35 offscreen GUI assertions (
gui_selftest+scripts/verify_gui_selftest.py): drives the
real workbench UI headlessly through onboarding → agent online → "Connected" popup + welcome
memory → keyfile-loss banner → rotate fix (old key 401, new key 200) → Settings re-entry. - 14 platform assertions (
scripts/test_onboarding_and_safety.py): provisioning, heartbeat,
welcome memory, keyfile-loss diagnostics and key-rotation semantics over HTTP. - 291 unit-test assertions (up from 243); the packaging pipeline was re-verified end to end.
- README screenshots are generated by
scripts/capture_screenshots.py— seeded demo data,
PrintWindowcapture, zero human clicking.
Which file should I download?
| File | Best for | Notes |
|---|---|---|
MiderHive-1.1.1-x64.msi |
A normal install | Installs to %LOCALAPPDATA%\MiderHive. No administrator rights needed for a standard user install. Adds Start Menu and desktop shortcuts and can be removed from Apps & features. |
MiderHive-1.1.1-win64-portable.zip |
No installation | Unzip and run miderhive.exe. Handy for a USB stick or a quick trial. |
SHA256SUMS.txt |
Verifying integrity | See the verification section below. |
Install / run
- Installer: double-click and follow the wizard, or install silently with
msiexec /i MiderHive-1.1.1-x64.msi /qn - Portable: unzip anywhere, then double-click
miderhive.exe
The workbench embeds a local HTTP service on http://127.0.0.1:8787 (override the port with the
MIDERHIVE_PORT environment variable). Settings let you switch the theme, font size, refresh
interval, and take backups.
Upgrading
- From any earlier version: install this MSI over the old one — the same upgrade identity is
used, so the previous version is removed first and nothing is left behind. Your data directory
is kept as-is. - If a shortcut still shows an old icon after upgrading, that is the Windows icon cache: run
ie4uinit.exe -show, or restart Explorer. - The built-in updater will also offer 1.1.1 by itself (checked at most once a day; the download
is SHA256-verified before it runs).
Verify the download (optional)
Get-FileHash .\MiderHive-1.1.1-x64.msi -Algorithm SHA256
# compare with the matching line in SHA256SUMS.txtFeedback
Issues and ideas: https://github.com/SiliconCoderJames/MiderHive/issues