Skip to content

Move the agent monitor to psf-monitor - #28

Merged
thisguymartin merged 1 commit into
mainfrom
chore/move-monitor-to-psf-monitor
Oct 5, 2026
Merged

thisguymartin merged 1 commit into
mainfrom
chore/move-monitor-to-psf-monitor

Conversation

@thisguymartin

Copy link
Copy Markdown
Owner

Closes #27

What changed

The agent monitor moved to its own plugin, psf-monitor. pstack users who want the live view install that plugin next to pstack. pstack itself loses the monitor skill.

  • Remove skills/monitor/ and skills/poteto-mode/scripts/monitor/, and drop monitor from the scripts' test and typecheck runs.
  • Keep pstack-runner's lane journal unchanged. docs/reference.md now documents it as the contract psf-monitor reads: lane.json schema version 1, stream.jsonl, receipt.json, and SIGTERM to the runner pid as the cancel path.
  • Point README, USAGE, provider-dispatch, CHANGES, UPSTREAM-FLEX, and NOTICE at psf-monitor.

psf-monitor was built from this repo's monitor at 71f51a1. It adds server-side pstack-only filtering, with no --all, and page controls to cancel a lane, copy a resume command, toggle the journal, and stop the monitor.

Verification

  • Bun tests, strict typecheck, static invariants, and plugin validation pass.
  • The exact candidate is installed in every affected harness.
  • The changed behavior passes from each real user surface.
  • The installed version, action, and observed result appear below.

Checks run on 259c1b1: bun run test passed 208 of 208, bun run typecheck passed, the manifest parse and PSTACK_STATIC_ONLY=1 bash tests/skill-collision-repro.sh passed, and claude plugin validate . passed.

Live evidence:

Still needed for this candidate: install the branch in Claude Code and Codex, confirm pstack:monitor is gone, and confirm a pstack-runner lane still journals and appears in psf-monitor.

Already observed with the installed pstack 1.5.0 runner, whose journal code this PR changes only in a comment, and psf-monitor 0.1.1 installed in Claude Code:

  • /psf-monitor:monitor from a fresh Claude Code process ran the launcher and printed the link.
  • A pstack-runner Codex lane labeled psf live cancel test appeared as running. Clicking Cancel lane and then Confirm turned it cancelled, with receipt status: cancelled, signal: SIGTERM.

A pull request without live evidence remains a draft. Do not merge, tag, release, or roll it out.

The monitor now lives in its own plugin, thisguymartin/psf-monitor.
Remove the monitor skill and scripts/monitor, drop them from the
scripts' test and typecheck runs, and point the docs at psf-monitor.

pstack-runner keeps writing the lane journal, which psf-monitor reads.
docs/reference.md now documents the journal as the contract between
the two.
@thisguymartin
thisguymartin marked this pull request as ready for review October 5, 2026 04:22
@thisguymartin
thisguymartin merged commit 3d3492d into main Oct 5, 2026
1 check passed
thisguymartin pushed a commit that referenced this pull request Oct 5, 2026
…tor)

Main moved the agent monitor to its own repository, psf-monitor (#28).
Take that: drop the in-repo pstack-monitor plugin this branch had split
out, with its marketplace entries, CI steps, check.sh steps, .gitignore
line, and static checks. Keep main's psf-monitor docs and lane journal
wording; keep this branch's rename, intake, diff-behavior, doc fixes,
check.sh, and LIVE-GATE.md, with the monitor row replaced by a lane
journal check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LSWNeBzAMt5FQZVziZCGLs
@thisguymartin
thisguymartin deleted the chore/move-monitor-to-psf-monitor branch October 6, 2026 05:10
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.

Move the agent monitor to its own repo (psf-monitor)

1 participant