GitHub profilePlugins by mbgulden
2 plugins by mbgulden in the catalog, most-starred first.
mbguldenagent-checkpointDurable progress checkpoints for long, budget-capped Hermes runs: at 50% of a run's budget the plugin tells the agent to persist everything found so far, and at 80% of the time budget / 90% of the turn budget it persists the checkpoint itself — a checkpoint file plus, in kanban runs, a task comment — evaluated at tool-call boundaries and by a per-session watchdog thread, with interval checkpoint coverage for uncapped runs. It guarantees a paper trail, not completion. Disclosures: no network calls; reads the kanban DB read-only for cap discovery; writes checkpoint files under $HERMES_HOME/agent-checkpoints/ and posts kanban task comments through the kanban_comment tool (dispatched via the plugin context; core sets the author and redacts the body, and the plugin names itself in the comment header); runs one daemon watchdog thread per session, exiting at session end; uses one private core import (hermes_cli.goals.load_goal) that draws a warning, never a failure, from hermes plugins validate; no credentials, no telemetry, no self-update. Disclosure — injects budget-checkpoint reminders into the prompt via pre_llm_call at 50% of a run's budget; at 80% time / 90% turns (and every uncapped_interval_seconds, default 1800, on runs with no cap) a per-session watchdog thread and the tool hooks write <run-id>.md under $HERMES_HOME/agent-checkpoints/ and, in kanban runs, post a task comment through the kanban_comment tool (core sets the author and redacts the body); reads the kanban DB read-only for the task's runtime cap; uses one private core import (hermes_cli.goals.load_goal); no network calls, credentials, telemetry or self-update.Communityautomationmbguldenkanban-streamLive-stream Hermes kanban worker activity to a Telegram ops channel: one edit-in-place message per task with rolling tool-call history, elapsed timer, tokens/sec, thinking indicator, and a pinned final state (done/blocked). Mid-task steering via task comments — /steer from Telegram through the bundled companion daemon, or straight from the board. Ships disabled by default; needs a dedicated ops bot (KANBAN_STREAM_BOT_TOKEN + KANBAN_STREAM_ALLOWED_USERS). Outbound calls go only to api.telegram.org; reads the kanban DB read-only; no telemetry, no self-update. Disclosure — sends kanban task titles, summaries and tool names with command/path snippets to the Telegram chat you configure via your own bot; the optional steer daemon posts allowlisted Telegram users' /steer text as task comments that reach the running worker.Communityautomation
