LLM Wiki

Appearance

Built 26/04/16 13:13commit cc1e88d

OpenClaw Field Notes ​

中文 | English

Summary ​

This section records operational lessons learned from real OpenClaw usage: integration surprises, loader constraints, pairing and permission failures, provider configuration issues, and the concrete fixes that turned vague symptoms into repeatable playbooks.

It is intentionally different from wiki/sources/: these pages are maintained field notes derived from lived incidents, not just summaries of external source material.

What Belongs Here ​

  • Issues reproduced on a real OpenClaw machine rather than only described in docs.
  • Failure modes where the visible symptom and the real root cause differed.
  • Fixes that should be reusable by other operators or assistants.
  • Notes that bridge official behavior, local configuration, and operational reality.

Current Notes ​

Maintenance Rules ​

  • Keep each note tightly scoped to one failure pattern.
  • Separate symptom, root cause, confirmation steps, and fix.
  • Prefer concrete file paths, exact error strings, and observed config snippets over vague recollections.
  • Treat this section as a shared destination for operator knowledge that has already proved durable enough to survive beyond one local debugging session.
  • Do not treat the wiki as the first landing zone for fresh lessons. New lessons should usually be captured first in an internal learnings system, then promoted here once they are mature, reusable, and sanitized.
  • When the field note changes user-facing navigation or durable repo practice, update index.md, index.zh.md, overview.md, overview.zh.md, and log.md.

Review Loop ​

  • During normal llm-wiki maintenance, review internal learnings for lessons that are now mature enough to deserve a shared field note.
  • Prefer promoting one or two high-value notes over doing a broad retrospective dump.
  • If no recent lesson is mature, reusable, and sanitized enough, make no change.