# openclaw-maintainer

> Diagnose and self-heal an OpenClaw installation on Windows (gateway/service flapping, Feishu disconnects, browser CDP/headless issues, model auth 401/403/timeouts, Git conflicts/submodules, and GitHub push failures). Use when OpenClaw shows “Connection error”, frequent watchdog restarts, tool/API 401/404/429, “Invalid input[*].name … ^[a-zA-Z0-9_-]+$”, or when `git push` hangs/fails in `C:\Users\Administrator\.openclaw\workspace`.

- Author: SuperDamon
- Repository: SuperDamon-X/openclaw-workspace
- Version: 20260209191409
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/SuperDamon-X/openclaw-workspace
- Web: https://mule.run/skillshub/@@SuperDamon-X/openclaw-workspace~openclaw-maintainer:20260209191409

---

---
name: openclaw-maintainer
description: Diagnose and self-heal an OpenClaw installation on Windows (gateway/service flapping, Feishu disconnects, browser CDP/headless issues, model auth 401/403/timeouts, Git conflicts/submodules, and GitHub push failures). Use when OpenClaw shows “Connection error”, frequent watchdog restarts, tool/API 401/404/429, “Invalid input[*].name … ^[a-zA-Z0-9_-]+$”, or when `git push` hangs/fails in `C:\Users\Administrator\.openclaw\workspace`.
---

# OpenClaw Maintainer

## Workflow (fast)

Goal: get back to a stable, repeatable “green” state (gateway ok, Feishu ok, models usable, browser CDP ready, git clean).

0) Always start with a report (read-only)

```powershell
cd C:\Users\Administrator\.openclaw\workspace
powershell -NoProfile -ExecutionPolicy Bypass -File .\skills\openclaw-maintainer\scripts\report.ps1
```

If you suspect “API 冲突/401/403/timeout” or scheduled-task issues, run the deep report:

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -File .\skills\openclaw-maintainer\scripts\report.ps1 -Deep
```

1) Collect facts (quick triage, read-only)

Run the bundled triage script (read-only by default):

```powershell
cd C:\Users\Administrator\.openclaw\workspace
powershell -NoProfile -ExecutionPolicy Bypass -File .\skills\openclaw-maintainer\scripts\triage.ps1
```

Optional: check for common port conflicts (read-only):

```powershell
cd C:\Users\Administrator\.openclaw\workspace
powershell -NoProfile -ExecutionPolicy Bypass -File .\skills\openclaw-maintainer\scripts\ports.ps1
```

2) If gateway/service is flapping or “Connection error”

Run OpenClaw repair (safe defaults, non-interactive):

```powershell
cd C:\Users\Administrator\.openclaw
openclaw doctor --deep --repair --non-interactive
openclaw security audit --deep
```

Or run the bundled repair wrapper (includes optional gateway restart + browser ensure + health check):

```powershell
cd C:\Users\Administrator\.openclaw\workspace
powershell -NoProfile -ExecutionPolicy Bypass -File .\skills\openclaw-maintainer\scripts\repair.ps1 -Fix -ConfirmFix YES
```

If the watchdog keeps restarting, check `C:\Users\Administrator\.openclaw\watchdog.log` and confirm the scheduled task `OpenClaw Gateway (Interactive)` exists and points at `C:\Users\Administrator\.openclaw\gateway.cmd`.

3) If browser automation is unstable

This environment is configured for **chrome profile + headless**, but Chrome may be missing; OpenClaw will auto-detect Edge and still provide CDP.

Verify and start CDP:

```powershell
cd C:\Users\Administrator\.openclaw
openclaw browser status --json
openclaw browser start --browser-profile chrome --json
```

If `attachOnly=true`, starting a non-running profile will fail. Prefer `browser-profile chrome` (CDP `18793`) unless you explicitly run the relay/extension profile.

4) If models show 401/403/timeouts (API conflicts)

Probe providers and interpret:

```powershell
cd C:\Users\Administrator\.openclaw
openclaw models status --probe --probe-timeout 20000
```

Common meanings:
- `kimi-coding/*` `HTTP 401` => key expired/invalid; remove from fallbacks or rotate key.
- `anthropic/*` `HTTP 403 access_denied` => account/token lacks permission.
- `openai/*` `timeout` => network/proxy issue or outbound blocked; verify proxy and try again with higher timeout.

5) If `git push` cannot be done by OpenClaw

Root cause is almost always **missing non-interactive GitHub credentials**.

Preferred: SSH deploy key (no prompts). See: `references/github-push.md`.

If push is blocked by GitHub secret scanning (GH013), use the `git-secrets-guard` skill to scan and safely scrub history.

Fallback: PAT over HTTPS. Use `C:\Users\Administrator\.openclaw\workspace\scripts\push_origin.ps1` with `GITHUB_TOKEN`/`GH_TOKEN`.

See: `references/github-push.md`.

## Guardrails (security)

- Never paste/store tokens in git.
- Prefer “report-only” first; only run “fix mode” after reviewing the report.
- For any operation that edits `openclaw.json` / scheduled tasks / services, keep a backup and report exactly what changed.

## More scenarios

See `references/scenarios.md` for additional hypotheses and flows beyond the cases we’ve already hit in this workspace.