claudetools/.claude/memory/feedback_no_botalerts_internal_rmm.md at 90407171126ff5af46cd00a533deca8de0b2a4e4

Files

Mike Swanson d0cbf6126e docs: record Claude-Builder=PLUTO mapping + infra working-feedback memories

- Pluto memory/wiki/machine notes: Unraid VM "Claude-Builder" == hostname PLUTO ==
  172.16.3.36 (same box); RMM-agent access path when SSH key unauthorized; now also
  builds the GuruConnect Windows agent + hosts a Gitea Actions runner.
- New feedback memories: post #bot-alerts only for client/ticket-affecting RMM commands;
  proceed autonomously through routine infra/build prerequisites.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-29 10:37:44 -07:00

1.2 KiB

Raw Blame History

name, description, metadata

name

description

metadata

feedback_no_botalerts_internal_rmm

Post

type
feedback

The /rmm skill instructs "post a one-line #bot-alert after every dispatch." Mike does NOT want #bot-alerts for internal infrastructure / dev-tooling commands — e.g. installing a Gitea Actions runner on PLUTO, CI/build orchestration on build VMs, inventory/recon during setup.

The rule (Mike, 2026-05-29): post a #bot-alert ONLY when the RMM command directly affects a client endpoint or a ticket (remediation, a client machine change, ticket-linked work). For everything else — internal infra, build/CI orchestration, dev-tooling, recon/inventory (e.g. the PLUTO build-runner setup) — SKIP the alert.

Why: keeps #bot-alerts signal-high — it's a client/ticket activity feed, not a build log.

How to apply: When dispatching via /rmm or the GuruRMM command API, ask "does this touch a client/ticket?" If no, do NOT call post-bot-alert.sh. Overrides the skill's blanket "alert after every dispatch" rule. Related: reference_pluto_build_server.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History