@@ -7,9 +7,13 @@ read_when:
77 - Reviewing what diagnostics data is recorded or redacted
88---
9910-OpenClaw can create a local diagnostics zip that is safe to attach to bug
11-reports. It combines sanitized Gateway status, health, logs, config shape, and
12-recent payload-free stability events.
10+OpenClaw can create a local diagnostics zip for bug reports. It combines
11+sanitized Gateway status, health, logs, config shape, and recent payload-free
12+stability events.
13+14+Treat diagnostics bundles like secrets until you have reviewed them. They are
15+designed to omit or redact payloads and credentials, but they still summarize
16+local Gateway logs and host-level runtime state.
13171418## Quick start
1519@@ -29,6 +33,45 @@ For automation:
2933openclaw gateway diagnostics export --json
3034```
313536+## Chat command
37+38+Owners can use `/diagnostics [note]` in chat to request a local Gateway export.
39+Use this when the bug happened in a real conversation and you want one
40+copy-pasteable report for support:
41+42+1. Send `/diagnostics` in the conversation where you noticed the problem. Add a
43+ short note if it helps, for example `/diagnostics bad tool choice`.
44+2. OpenClaw sends the diagnostics preamble and asks for one explicit exec
45+ approval. The approval runs `openclaw gateway diagnostics export --json`.
46+ Do not approve diagnostics through an allow-all rule.
47+3. After approval, OpenClaw replies with a pasteable report containing the local
48+ bundle path, manifest summary, privacy notes, and relevant session ids.
49+50+In group chats, an owner can still run `/diagnostics`, but OpenClaw does not
51+post the diagnostic details back into the shared chat. It sends the preamble,
52+approval prompts, Gateway export result, and Codex session/thread breakdown to
53+the owner through the private approval route. The group only gets a short notice
54+that the diagnostics flow was sent privately. If OpenClaw cannot find a private
55+owner route, the command fails closed and asks the owner to run it from a DM.
56+57+When the active OpenClaw session is using the native OpenAI Codex harness,
58+the same exec approval also covers an OpenAI feedback upload for the Codex
59+runtime threads OpenClaw knows about. That upload is separate from the local
60+Gateway zip and appears only for Codex harness sessions. Before approval, the
61+prompt explains that approving diagnostics will also send Codex feedback, but it
62+does not list Codex session or thread ids. After approval, the chat reply lists
63+the channels, OpenClaw session ids, Codex thread ids, and local resume commands
64+for the threads that were sent to OpenAI servers. If you deny or ignore the
65+approval, OpenClaw does not run the export, does not send Codex feedback, and
66+does not print the Codex ids.
67+68+That makes the common Codex debugging loop short: notice the bad behavior in
69+Telegram, Discord, or another channel, run `/diagnostics`, approve once, share
70+the report with support, then run the printed `codex resume <thread-id>` command
71+locally if you want to inspect the native Codex thread yourself. See
72+[Codex harness](/plugins/codex-harness#inspect-a-codex-thread-from-the-cli) for
73+that inspection workflow.
74+3275## What the export contains
33763477The zip includes:
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。