openclaw/extensions/logbook
Peter Steinberger a94a7b2768
chore(release): close out 2026.9.5 on main (#151823)
* chore(release): close out 2026.9.5 on main

* chore(release): align GitHub plugin with 2026.9.5 closeout
2026-09-19 01:37:16 -07:00
..
assets feat: give every plugin a compact chat activity icon (#147333) 2026-09-13 13:49:51 -07:00
src fix(memory): reduce CPU work during index sync (#150602) 2026-09-17 01:33:59 -07:00
index.test.ts refactor(logbook): run SQLite operations in owned workers (#144982) 2026-09-11 16:00:03 -07:00
index.ts feat: automatically update idle headless nodes (#151545) 2026-09-18 06:20:27 -07:00
openclaw.plugin.json feat: group bundled plugin settings by authored manifest metadata (#149331) 2026-09-16 22:03:41 -07:00
package.json chore(release): close out 2026.9.5 on main (#151823) 2026-09-19 01:37:16 -07:00
README.md feat(plugins): prepare three bundled plugins for catalog publication (#150291) 2026-09-16 13:58:37 -07:00

@openclaw/logbook

An automatic work journal for OpenClaw. Logbook captures periodic screen snapshots from a paired node, builds a timeline of your day, and produces standup summaries and answers grounded in that timeline.

The standalone package requires OpenClaw 2026.9.5 or newer. Logbook is also included in OpenClaw and disabled by default. Enable it only after reviewing the capture and model setup in the Logbook guide.

You need a connected screen-capture node, a compatible structured vision route, and a working default agent model. The guide covers node permissions, model authentication, configuration, and the Control UI timeline.

Enabling Logbook opts into screen capture unless captureEnabled is set to false. Screenshots can contain sensitive information: sampled frames go to the configured observation model, and derived activity text goes to the default agent model. Storage remains on the Gateway. Frame retention defaults to 14 days; timeline cards and observations are retained.

Use openclaw plugins inspect logbook --runtime --json to inspect registration and the dashboard status to check capture and analysis outcomes. Installation alone does not establish node permissions or model authentication.