# OpenClaw Investigation Report

**Date:** 2026-04-30
**Agent:** OpsMan (LFCS Project Manager / Site Superintendent)
**Runtime:** OpenClaw 2026.4.26

---

## 1. Config Backup

**Status:** COMPLETED

```
/root/.openclaw/openclaw.json.bak.20260430 (10392 bytes)
```

---

## 2. Hermes Relationship

**Question:** Are you and Hermes running as two completely separate agents on this VPS?

**Answer:** YES — completely separate agents, no inter-process communication.

| Check | Result |
|-------|--------|
| Hermes process visible? | YES — pid 2763217 (hermes gateway), pid 2763313 (WhatsApp bridge) |
| hermes CLI works? | YES — v0.11.0 (2026.4.23) |
| ACP plugin enabled? | NO — `plugins.entries.acpx.enabled: false` in config |
| Can I delegate to Hermes? | NO — no protocol link configured |

**Hermes cron jobs (NOT on OpsMan):**
- lfcs-am-lookahead
- lfcs-eod-summary
- lfcs-weekly-programme
- opsman-watchdog-hourly (paused)

These are LFCS jobs sitting on Hermes that should migrate to OpsMan once cron is wired.

---

## 3. API Keys

| Key | Status |
|-----|--------|
| MINIMAX_API_KEY | PRESENT |
| OPENAI_API_KEY | PRESENT |
| OPENROUTER_API_KEY | PRESENT |
| ANTHROPIC_API_KEY | MISSING |
| DEEPSEEK_API_KEY | MISSING |
| KIMI_API_KEY | MISSING |
| MOONSHOT_API_KEY | MISSING |
| NOUS_API_KEY | MISSING |
| GLM_API_KEY | MISSING |
| MISTRAL_API_KEY | MISSING |

---

## 4. Fallback Chain — PROPOSED (Not Applied)

**Current chain:**
- Primary: minimax/MiniMax-M2.7
- Fallback 1: minimax/MiniMax-M2.5
- Fallback 2: deepseek/deepseek-v4-pro

**Proposed new chain:**
- Primary: minimax/MiniMax-M2.7
- Fallback 1: minimax/MiniMax-M2.5
- Fallback 2: deepseek/deepseek-v4-flash  (cheaper, faster)
- Fallback 3: deepseek/deepseek-v4-pro   (full power)

**Rationale:** DeepSeek V4 Flash is significantly cheaper (~$0.10/M input vs $2.00/M) and faster. Use as a middle tier before escalating to Pro.

---

## 5. Skills Audit

**System skills loaded:** 54

```
1password
apple-notes
apple-reminders
bear-notes
blogwatcher
blucli
bluebubbles
camsnap
canvas
clawhub
coding-agent
discord
eightctl
gemini
gh-issues
gifgrep
github
gog
goplaces
healthcheck
himalaya
imsg
mcporter
model-usage
nano-pdf
node-connect
notion
obsidian
openai-whisper
openai-whisper-api
openhue
oracle
ordercli
peekaboo
sag
session-logs
sherpa-onnx-tts
skill-creator
slack
songsee
sonoscli
spotify-player
summarize
taskflow
taskflow-inbox-triage
things-mac
tmux
trello
video-frames
voice-call
wacli
weather
xurl
```

**Custom skills in workspace:** NONE

### Recommended LFCS Custom Skills

| Skill | Summary |
|-------|---------|
| lfcs-job-scaffold | Create new job folder structure from brief (11 folders, 00-brief.md, Job-Tracker.md) |
| lfcs-variation-register | Log VO, chase sign-off, update at-risk status |
| lfcs-docket-check | Verify signed docket exists before billing dayworks |
| lfcs-rfi-manager | Log RFIs, track open/closed status, chase replies |
| lfcs-rate-card | Calculate invoice lines from hours (tier breakdown) |
| lfcs-daily-diary | Append-only daily site diary entry builder |
| lfcs-job-tracker | Update hours/materials/costs on Job Tracker markdown |

---

## 6. Cron Jobs — GAP CONFIRMED

**OpsMan cron jobs:** NONE (empty)

**Gap confirmed:** All LFCS cron jobs (am-lookahead, eod-summary, weekly-programme, watchdog) are on Hermes, not OpsMan.

---

## 7. Vault Audit

| Check | Result |
|-------|--------|
| /home/ccuser/vault/ exists? | YES |
| Readable? | YES — root:root, 755 |
| Writable? | YES — test write succeeded |
| Has LFCS folder? | NO |
| Contents | 00-Brain-Dump/, 09-Agent-Output/ |

**Recommendation:** LFCS should stay SEPARATE from RateRight vault. Keep /home/ccuser/opsman-work/ standalone. Different use case, different lifecycle.

---

## 8. Update Check

| Current | Latest available |
|---------|----------------|
| 2026.4.26 | 2026.4.27 |

Update available via `openclaw update --dry-run`.

---

## 9. Reasoning Leak — ROOT CAUSE FOUND

**Flag:** `thinkingDefault` in agents.defaults

**Current value:** `null` (not set)

**Effect:** When `thinking` is enabled by user, reasoning steps are sent as separate messages on Telegram.

**Fix:** Set `agents.defaults.thinkingDefault: "off"` to always hide reasoning in channel output.

**Location in config:**
```
agents.defaults.thinkingDefault: null   # ← change to "off"
```

---

## 10. Legacy References

| Check | Found? |
|-------|-------|
| Service name = clawdbot-opsman | YES — but that's just systemd naming |
| config has "clawdbot" | NO |
| config has "moltbot" | NO |
| config has "clawd-3" | NO |
| config has "clawd-2" | NO |

**Result:** No legacy model strings in config. Clean.

---

## 11. Self-Recovery

**Service:** clawdbot-opsman.service

| Property | Value |
|----------|-------|
| Enabled | YES |
| Main PID | 2126568 |
| Start time | 2026-04-29 17:30:31 |
| Uptime | 23h (healthy) |
| Restart policy | systemd (automatic) |

**Crashes in last 7 days (from journalctl):**

Multiple crashes on 2026-04-29 (Apr 29), all before the 17:30 restart:
- Multiple "Invalid config at /root/.clawdbot-opsman/openclaw.json" failures
- Multiple auto-restarts by systemd (working as designed)
- No crashes after 17:30 on Apr 29

**Assessment:** Self-recovery is WORKING. Crashes were config-related (fixed now).

---

## 12. Honest Summary

### What's WORKING
- Telegram channel (active, connected to Rocky 7377499346)
- Gateway service up 23h
- Config loads correctly
- Systemd restart policy works (crash recovery tested)
- Workspace /home/ccuser/opsman-work/ accessible
- All LFCS project files present (AGENTS.md, USER.md, SOUL.md, lfcs-standards/)
- Skills loading (54 system skills)
- No legacy model references

### What's BROKEN
- No cron jobs (Hermes has LFCS cron jobs that belong here)
- No WhatsApp (disabled, Hermes has a WhatsApp bridge but it's separate)
- ACP disabled (cannot delegate to Hermes)
- Reasoning leak to Telegram (thinkingDefault not set to "off")

### What's STALE
- Update available: 2026.4.27 available but not applied
- No custom skills (LFCS rules in AGENTS.md not promoted to SKILL.md)
- No Job Tracker Google Sheet (still markdown)

### Overlaps with Hermes
- BOTH have LFCS in their context
- Hermes has WhatsApp bridge, cron jobs, and is physically present on same VPS
- OpsMan is the "on-site capture-and-recall" assistant
- Hermes appears to be the "desk" assistant with more automation
- Roles not cleanly split yet — needs coordination

---

**End of Report**