openclaw - 💡(How to fix) Fix openclaw doctor: Claude CLI section reports irrelevant info for non-Claude-CLI agents [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73903Fetched 2026-04-29 06:13:30
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Timeline (top)
commented ×2closed ×1

openclaw doctor always reports the Claude CLI section against the default agent, even when that agent does not use Claude CLI as its backend. The reported Workspace and Claude project dir paths then look like Claude CLI is bound to that agent, which is misleading.

Root Cause

openclaw doctor always reports the Claude CLI section against the default agent, even when that agent does not use Claude CLI as its backend. The reported Workspace and Claude project dir paths then look like Claude CLI is bound to that agent, which is misleading.

Code Example

openclaw doctor

---

- Binary: /opt/homebrew/bin/claude.
- Headless Claude auth: unavailable without interactive prompting.
- OpenClaw auth profile: anthropic:claude-cli (provider claude-cli).
- Workspace: ~/.openclaw/workspace-coder (writable).
- Claude project dir: ~/.claude/projects/-Users-visionable--openclaw-workspace-coder (present).
RAW_BUFFERClick to expand / collapse

Summary

openclaw doctor always reports the Claude CLI section against the default agent, even when that agent does not use Claude CLI as its backend. The reported Workspace and Claude project dir paths then look like Claude CLI is bound to that agent, which is misleading.

Reproduction

Setup:

  • Default agent coder → backend = OpenAI Codex (not Claude CLI)
  • Agent xiaoao → backend = Claude CLI
  • Agent lite → backend = Gemini

Run:

openclaw doctor

Doctor section "Claude CLI" reports:

- Binary: /opt/homebrew/bin/claude.
- Headless Claude auth: unavailable without interactive prompting.
- OpenClaw auth profile: anthropic:claude-cli (provider claude-cli).
- Workspace: ~/.openclaw/workspace-coder (writable).
- Claude project dir: ~/.claude/projects/-Users-visionable--openclaw-workspace-coder (present).

The Workspace and Claude project dir paths are derived from the default agent's workspace, but coder does not use Claude CLI. The actually-relevant agent (xiaoao) and its ~/.openclaw/workspace / ~/.claude/projects/-Users-visionable--openclaw-workspace are never reported.

Expected

Either:

  1. Doctor should automatically scope the Claude CLI section to whichever agents have agentRuntime.id == "claude-cli" (skip the section if no agent uses Claude CLI).
  2. OR doctor should accept --agent <id> to explicitly scope all checks to one agent.

Both would prevent the current confusion where users assume Claude CLI is bound to their default agent.

Environment

  • OpenClaw 2026.4.26 (be8c246)
  • macOS Darwin 25.4.0

extent analysis

TL;DR

The openclaw doctor command should be modified to either automatically scope the Claude CLI section to agents using Claude CLI or accept an --agent flag to explicitly scope checks to one agent.

Guidance

  • The issue arises from openclaw doctor always reporting the Claude CLI section against the default agent, regardless of the agent's backend.
  • To mitigate this, consider modifying the openclaw doctor command to check the backend of each agent and only report the Claude CLI section for agents using Claude CLI.
  • An alternative solution is to add an --agent flag to the openclaw doctor command, allowing users to explicitly scope checks to a specific agent.
  • Verify the fix by running openclaw doctor with the modified command or flag and checking that the reported Workspace and Claude project dir paths match the expected agent.

Example

No code snippet is provided as the issue does not contain sufficient information to generate a specific code example.

Notes

The provided solution assumes that the openclaw doctor command can be modified to accommodate the suggested changes. If this is not possible, further investigation into the command's functionality and limitations may be necessary.

Recommendation

Apply workaround: Modify the openclaw doctor command to accept an --agent flag, allowing users to explicitly scope checks to a specific agent. This approach provides a more immediate solution and allows users to work around the current issue until a more permanent fix can be implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix openclaw doctor: Claude CLI section reports irrelevant info for non-Claude-CLI agents [2 comments, 3 participants]