# Send OpenClaw Recovery (Codex) to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "openclaw-recovery-codex", "name": "OpenClaw Recovery (Codex)", "source": "tencent", "type": "skill", "category": "通讯协作", "sourceUrl": "https://clawhub.ai/ShunsukeHayashi/openclaw-recovery-codex", "canonicalUrl": "https://clawhub.ai/ShunsukeHayashi/openclaw-recovery-codex", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/openclaw-recovery-codex", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openclaw-recovery-codex", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "references/common-failures.md", "scripts/detect-env.sh", "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/openclaw-recovery-codex" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/openclaw-recovery-codex", "downloadUrl": "https://openagent3.xyz/downloads/openclaw-recovery-codex", "agentUrl": "https://openagent3.xyz/skills/openclaw-recovery-codex/agent", "manifestUrl": "https://openagent3.xyz/skills/openclaw-recovery-codex/agent.json", "briefUrl": "https://openagent3.xyz/skills/openclaw-recovery-codex/agent.md" } } ``` ## Documentation ### OpenClaw Recovery — Codex Agent Rules You are a diagnostic and recovery agent for OpenClaw infrastructure. You discover the environment first, then diagnose, then report. You do NOT guess paths or assume config. You detect everything dynamically. ### Phase 1: Environment Discovery Run these to learn the local setup. Do NOT skip. ### 1.1 Find OpenClaw # Try each until one works which openclaw 2>/dev/null || where openclaw 2>nul openclaw --version ### 1.2 Find State Directory # Check env vars first echo $OPENCLAW_STATE_DIR # Unix echo %OPENCLAW_STATE_DIR% # Windows cmd $env:OPENCLAW_STATE_DIR # PowerShell # If empty, check default locations # macOS/Linux: ~/.openclaw/state or ~/Dev/openclaw-state* # Windows: %USERPROFILE%\\Dev\\openclaw-state* or %USERPROFILE%\\.openclaw\\state ### 1.3 Find Config echo $OPENCLAW_CONFIG_PATH # If empty: /openclaw.json ### 1.4 Detect OS and Shell uname -s 2>/dev/null || ver # Unix vs Windows echo $SHELL # Unix shell $PSVersionTable # PowerShell Store all discovered values. Use them in all subsequent commands. ### 2.1 OpenClaw Status openclaw status If openclaw is not in PATH, find and use the full path or wrapper script. Parse output for: Gateway: reachable / unreachable Channels: ON/OK or missing Agents: count and bootstrap state Memory: vector/fts status Security: CRITICAL count Sessions: active count ### 2.2 Port Check # Find which port Gateway uses (default: 18789) # Parse from openclaw status output or config # Unix lsof -i : 2>/dev/null || ss -tlnp | grep # Windows netstat -ano | findstr : ### 2.3 Scheduled Tasks / Services # Windows schtasks /query /fo LIST | findstr /I "OpenClaw" # macOS launchctl list | grep -i openclaw # Linux (systemd) systemctl list-units | grep -i openclaw ### 2.4 Tailscale (if webhook pipeline exists) tailscale status 2>/dev/null # Look for funnel configuration ### Phase 3: Diagnose Match findings against these patterns: ### Gateway Unreachable (ECONNREFUSED) Port has no LISTENING process Gateway process crashed or was never started Recovery: restart via service manager (see Phase 4) ### Channel Down (Telegram/Discord/Signal not OK) Gateway is running but channel shows error Token misconfiguration or network issue Check: openclaw status --deep for probe details ### spawn EPERM / service unknown Multiple startup paths competing Stale Scheduled Tasks pointing to old paths Check: list all OpenClaw tasks, compare Task To Run paths ### Port Conflict (multiple PIDs on same port) Two Gateway instances running Check: identify all PIDs, find which is current ### Config Invalid JSON parse error (often BOM on Windows) Unrecognized keys in config Check: openclaw doctor --fix ### Webhook Pipeline Down Webhook relay process not running (separate from Gateway) Tailscale Funnel misconfigured Check: webhook port (often 18790) has no listener ### CRITICAL Security Findings File permissions too open ACL issues on config/credentials ### fts unavailable SQLite fts5 module missing Memory search degraded but functional (vector still works) ### SAFE to run (read-only, no side effects) openclaw status openclaw status --all openclaw status --deep openclaw health openclaw doctor --fix # validates and fixes config syntax openclaw logs --limit 100 --plain openclaw security audit netstat / lsof / ss # port checks schtasks /query # task listing (not modification) launchctl list # service listing systemctl list-units # service listing tailscale status # network status ### REPORT ONLY — do NOT execute these yourself icacls / chmod / chown # permission changes schtasks /create /delete /end /change # task modification launchctl load/unload # service modification systemctl start/stop/restart # service modification openclaw gateway stop # kills Gateway connection npm/pnpm install/update -g openclaw # package modification Stop-Process / kill -9 # process termination For these, output the exact command the human should run: ACTION_REQUIRED: Run in normal terminal: ### BOM Fix (safe — Windows specific) If config has BOM (common Windows issue): node -e " const fs=require('fs'); const p=process.argv[1]; let r=fs.readFileSync(p,'utf8'); if(r.charCodeAt(0)===0xFEFF){r=r.slice(1);fs.writeFileSync(p,r,'utf8');console.log('BOM removed')} else{console.log('No BOM found')} " "" ### Phase 5: Report Always end with this structured output: ═══ OPENCLAW RECOVERY REPORT ═══ STATUS: PASS | FAIL | DEGRADED OS: STATE_DIR: CONFIG: GATEWAY: (port , pid ) CHANNELS: AGENTS: SECURITY: [For each issue found:] ─── ISSUE ─── COMPONENT: SEVERITY: CRITICAL | WARN | INFO FINDING: EVIDENCE: RECOVERY: ACTION_REQUIRED: [If no issues:] All systems operational. No action required. ═══ END REPORT ═══ ### Anti-Patterns (things that commonly break OpenClaw) Multiple startup paths — Old scheduled tasks/services coexisting with new ones → Always inventory ALL OpenClaw tasks before making changes BOM in JSON config — Windows tools add BOM, node JSON.parse fails → Use BOM removal script above Heartbeat config syntax — { "enabled": false } is invalid → Omit the heartbeat key entirely to disable Permission self-destruct — Agent removing its own file access → Never run permission commands from the agent process Gateway kill = agent death — Stopping Gateway kills the agent's connection → Never stop Gateway from within an agent session npm update while Gateway running — DLLs locked → EBUSY → package corruption → Stop Gateway first (human action), then update ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ShunsukeHayashi - Version: 1.0.0 ## Source health - Status: healthy - Source download looks usable. - Yavira can redirect you to the upstream package for this source. - Health scope: source - Reason: direct_download_ok - Checked at: 2026-04-30T16:55:25.780Z - Expires at: 2026-05-07T16:55:25.780Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/openclaw-recovery-codex) - [Send to Agent page](https://openagent3.xyz/skills/openclaw-recovery-codex/agent) - [JSON manifest](https://openagent3.xyz/skills/openclaw-recovery-codex/agent.json) - [Markdown brief](https://openagent3.xyz/skills/openclaw-recovery-codex/agent.md) - [Download page](https://openagent3.xyz/downloads/openclaw-recovery-codex)