From d9b7c0d905bde95abe60cd13a22e59036fa6e753 Mon Sep 17 00:00:00 2001 From: dtzp555 Date: Mon, 30 Mar 2026 20:50:17 +1000 Subject: [PATCH] =?UTF-8?q?docs:=20add=20Known=20Issues=20=E2=80=94=20/ocp?= =?UTF-8?q?=20Unknown=20skill=20workaround?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Documented the intermittent "Unknown skill: ocp" issue caused by OpenClaw gateway session routing bug (#26895). Workaround: /new followed by /ocp restart. Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 68346dd..736c327 100644 --- a/README.md +++ b/README.md @@ -317,6 +317,27 @@ openclaw gateway restart - Session management with `--resume` - Full tool access, system prompt, MCP config support +## Known Issues + +### `/ocp` command returns "Unknown skill: ocp" + +The `/ocp` plugin command may intermittently stop working and return "Unknown skill: ocp". This is caused by an OpenClaw gateway bug where internal session routing interferes with plugin command dispatch ([openclaw/openclaw#26895](https://github.com/openclaw/openclaw/issues/26895)). + +**Workaround:** Send `/new` to reset the session, then `/ocp restart` to restart the proxy: + +``` +/new +/ocp restart +``` + +This reliably restores the plugin. The issue may recur after some time — repeat the workaround as needed. + +**Important:** +- Do **not** add `ocp` to agent `skills` lists in `openclaw.json` — this creates a routing conflict and makes the problem worse. OCP should only be registered as a **plugin**. +- Do **not** place a `SKILL.md` file in the workspace skills directory for ocp — same conflict. + +We are tracking the upstream fix. This section will be updated when it is resolved. + ## License MIT