Skip to content

feat: plamen monitor <interval> — status-heartbeat command for running audits#19

Open
yeahChibyke wants to merge 1 commit into
PlamenTSV:mainfrom
yeahChibyke:feat/monitor-command
Open

feat: plamen monitor <interval> — status-heartbeat command for running audits#19
yeahChibyke wants to merge 1 commit into
PlamenTSV:mainfrom
yeahChibyke:feat/monitor-command

Conversation

@yeahChibyke

Copy link
Copy Markdown

Implements #18. Adds a plamen monitor <minutes> [path] command that arms a periodic status heartbeat over an already-running V2 audit, via the Claude Code Monitor tool.

  • No driver changes — reads only artifacts the driver already writes (_v2_checkpoint.json, _stdio_*.log, _plamen.log, AUDIT_REPORT.md).
  • Emits a report immediately on arm, then every <minutes> (default 15), plus event-driven PROGRESS / ALERT-STALL, and a terminal DONE / ALERT-DEAD when the driver exits.
  • Claude backend onlyMonitor has no Codex (codex exec) equivalent; the mode documents this and points Codex users at tail -f.
  • scripts/plamen_monitor.sh is the generalization of a watcher already battle-tested against live Thorough-mode runs.

🤖 Generated with Claude Code

Adds a Claude-backend command that arms a periodic status heartbeat over a
running V2 audit via the Claude Code Monitor tool. Reads only artifacts the
driver already writes (_v2_checkpoint.json, _stdio_*.log, _plamen.log,
AUDIT_REPORT.md) — no driver changes. Emits an immediate report, then one
every <interval> minutes, plus PROGRESS / ALERT-STALL events and a terminal
DONE / ALERT-DEAD. Codex backend has no Monitor equivalent, so the mode is
documented Claude-only with a tail-the-log fallback.

Implements PlamenTSV#18.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@yeahChibyke yeahChibyke requested a review from PlamenTSV as a code owner June 20, 2026 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants