RunbookHQ

Opening workbench

Blog

Scripts, runbooks, standards, and reports in one list

2026-09-10 · What the workbench holds, and what it leaves out.

RunbookHQ is one organization-wide list. Modules you enable today are runbooks, scripts, standards, and reports. Items carry freeform tags. Search matches title, summary, and tags. There is no client catalog and no working-client switcher.

A runbook is the procedure: ordered Markdown steps, print for a change window, import .md from GitHub. Following one is browser-local. Ticks and filled {variables} stay in localStorage on that computer. There is no run record on the server.

A script is PowerShell first, then Python or Bash — one file or a small tree, with parsed parameters. Desktop confirms before a local run. The hosted app never executes it. Activity records interpreter, host, and exit code, not stdout.

A standard is a desired-state spec (MUST / SHOULD / MAY), not a procedure. An optional naming generator can lock {seq}. Procedure runbooks attach with item_links.relation = procedure.

Reports are authored flows: libraries (shared files), generators (inputs, steps, outputs), and saved artifacts. JavaScript builds in a browser worker. Python runs on the desktop after a native confirm. Hosted MCP never runs generator code and never accepts source-file bytes.

Marketplace is a signed-in catalog of frozen packs, not a fifth module. Share links are /share/{token} and stay off the search index.