dsh-logbook

Every dsh plugin logs through ctx.logger, but the framework ships with a single 1000-record in-memory buffer that silently drops warn and debug records. A plugin can raise a warning about a real problem, and there is simply no way to see it—live or after the fact.

dsh-logbook registers a full-capture exporter and gives you two observation windows. The first is a stderr writer that, by default, passes through only warnings and errors so a healthy session stays quiet; you can widen the filter per plugin via a config map. The second is a /logs command in the chat that maintains a 2000-record ring covering all levels, with type-based filtering. It never writes to stdout, keeping the SDK and ACP protocol lane clear, and it attaches an error listener on the stderr handle so a closed pipe cannot crash the dsh process.

If you run dsh from the terminal, do not want to spin up a browser or a web panel, and need a reliable way to confirm that a plugin warned or errored, dsh-logbook is the lightest option—pure terminal plus chat, no web dependency, fully functional in headless environments.