azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-06-12 05:57:38

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-12 05:57:38
This commit is contained in:
Mike Swanson
2026-06-12 05:58:05 -07:00
parent d1e02293c5
commit fd99ee327c
47 changed files with 1825 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.claude/commands/rmm.md
View File

@@ -157,6 +157,8 @@ Show: hostname, os_type, online/offline, client_name (from `site_name`/`client_n
Use `python` only when explicitly writing a Python script. Use `script` for saved scripts (not covered in this skill).
**VALID `command_type` values ONLY: `shell`, `powershell`, `python`, `script`, `claude_task` (plus alias `cmd` → shell = cmd.exe).** The agent deserializes `command_type` into a Rust enum; an UNKNOWN value (e.g. a made-up type) fails the agent's whole-message JSON parse and the command is **silently dropped — no ack, no result, no error** — which is indistinguishable from a network black-hole and has caused a long mis-diagnosis. On Windows: `powershell` runs powershell.exe (UTF-8 output fixed in-agent); `shell` or `cmd` runs cmd.exe. If a dispatched command sits un-acked forever, FIRST suspect an invalid `command_type` before chasing the network. (Newer agents NAK an unparseable command so it fails fast with a clear stderr instead of black-holing.)
### Basic dispatch
```bash

1
.claude/memory/MEMORY.md
View File

@@ -132,3 +132,4 @@
- [gururmm session-logs are in a submodule](gururmm-session-logs-submodule-save.md) — commit in the submodule + `git push origin HEAD:main` (GURU-5070 CAN push over HTTP now); then advance the parent gitlink
- [Use `python` not `python3` on GURU-5070](python3-shim-use-python.md) — `python3` in Git bash hits the flaky MS Store shim; real interpreters are `python` (3.12) / `py` (3.14). coord.py + wiki-compile work via `python`; the coord lock IS claimable here
- [Beast = primary GuruRMM Windows build host](gururmm-beast-windows-build-host.md) — GURU-BEAST-ROG (i9), reached from .30 via Tailscale-on-.30 at 100.101.122.4 as guru; Pluto is the fallback (`attempt_build beast || attempt_build pluto`). WiX must be 4.x (v6+ = OSMF); Beast NuGet needed nuget.org added
- [GuruRMM command_type gotcha](reference_gururmm_command_type.md) — only shell/powershell/python/script/claude_task (+cmd alias); unknown type silently dropped, looks like a black-hole

25
.claude/memory/reference_gururmm_command_type.md Normal file
View File

@@ -0,0 +1,25 @@
---
name: reference_gururmm_command_type
description: GuruRMM agent only accepts specific command_type values; an unknown type is silently dropped (looks like a black-hole)
metadata:
type: reference
---
GuruRMM agent `CommandType` (agent/src/transport/mod.rs) accepts ONLY: `shell`,
`powershell`, `python`, `script`, `claude_task` — plus alias `cmd` → shell
(added 2026-06-12). On Windows: `powershell` runs powershell.exe (UTF-8 output
fixed in-agent, so the old "-OutputEncoding not recognized" quirk is gone);
`shell`/`cmd` runs cmd.exe.
A command with an UNKNOWN `command_type` fails the agent's whole-message serde
parse; pre-2026-06-12 the error was logged-and-ignored and the command was
**silently dropped — no ack, no result** — indistinguishable from a NAT/proxy
black-hole. On 2026-06-12 a `command_type:"cmd"` (no variant then) caused a long
mis-diagnosis (7 multi-AI rounds, packet captures, a pfSense SNAT change) of
"PST agents can't receive commands" — the agents ran `powershell` commands fine
the whole time. The agent now also NAKs an unparseable command (CommandAck +
error CommandResult) so it fails fast instead of black-holing.
**How to apply:** When a dispatched command sits un-acked/never-completes,
FIRST verify `command_type` is one of the valid values before chasing the
network/proxy. Never send a made-up type. See [[reference_gururmm]].