Workbench Plugins
A plugin is one sandboxed HTML file that turns a plain channel file into an interactive board — a markdown todo becomes a checklist, a YAML map becomes a clickable code atlas. Files stay pure content that humans and agents edit through the same store; the plugin is just a lens. Renderers are, in spirit, CSS for files.
1Try without installing
Download a
.html below and drag it onto the workbench drawer —
it loads for your browser session only (⏱), no admin needed. Templates (.json) load the same way.2Install for the team
Settings → Workbench extensions (admin): the plugin joins every channel's
renderer candidates; per-file bindings persist in
.workbench.json.3Official set is already there
The four official plugins ship preinstalled with every gateway release
(an Official badge in Settings) — the downloads here are for reference,
forking, and session-testing newer builds.
Official plugins preinstalled
Seeded by the gateway on startup (origin: system), updated with each release.
They cover the everyday shapes: todos, tables, boards, and document metadata.
☑️Checklistcheers-checklist.plugin.html
Markdown task lists (
- [ ] / - [x]) become a clickable checklist; a toggle rewrites exactly that line, so the file stays human- and agent-readable markdown.claims:
markdown containing task lines📊Tablecheers-table.plugin.html
A JSON array of objects becomes an editable table — columns inferred from row keys, cell edits written straight back. The standard answer for agent-maintained datasets.
claims:
json whose top level is an array🗂️Kanban (markdown)cheers-kanban-md.plugin.html
Markdown
## sections with task lines become kanban columns with draggable cards — the whole board is still one ordinary markdown file an agent can edit.claims:
markdown with ## headings + task lines📇Frontmatter formcheers-frontmatter.plugin.html
The YAML frontmatter of a markdown document becomes a structured form; the body stays untouched. Edit metadata without ever breaking the document.
claims:
markdown with a --- frontmatter blockExample plugins & scenario templates fork-friendly
Complete, commented reference implementations from
docs/arch/examples/.
Each pair (plugin + template) sets up a full scenario: the template seeds the files and
pins the agent's conventions, the plugin renders them.
🗺️Codemapcodemap.plugin.html
A Devin-style, agent-maintained map of your codebase: a pan/zoom node
canvas over
codemap/map.yaml with hover summaries, status colors
(explored / partial / stale) and click-to-jump into the bot's workspace at the exact line
(cheers:open locators). The YAML's header comments teach the agent how to maintain it —
instructions travel with the data. Edits write back as comment-preserving line patches.claims:
yaml at codemap/*.yaml with codemap + nodes keys · protocol 1📚Paper trackerlit-review.plugin.html
A literature-review table over
{"papers": [...]} JSON: title / authors / venue / year, a reading-status dropdown and star ratings — agents add papers, you triage them.claims:
json with a papers key🔍Code review boardcode-review.plugin.html
Renders a markdown review log (
## file sections, - [ ] [P0] findings) with severity badges and a progress bar; checking a finding rewrites its line in place.claims:
markdown containing [P0]/[P1]/[P2]🧪Starter kitmd-checklist + research-lab + SDK
The tutorial checklist plugin from the dev guide, the full research-lab scenario template (tables, kanban, metrics chart, pinned conventions), and the inline SDK every plugin can copy-paste.
start here if you're building your own
Security model in one line: a plugin runs in an opaque-origin iframe
(
sandbox="allow-scripts") and can only read and save the one file the host
assigns it — no tokens, no other files, no other channels. Host actions it can request
(cheers:open navigation, cheers:compose composer prefill) are pure UI:
every read passes normal authorization, and nothing is ever sent on a plugin's behalf.