Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Post-restart suggestion to run `openclaw doctor --non-interactive` is not always actionable in heartbeat / approval-constrained contexts [1 comments, 1 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#69755•Fetched 2026-04-22 07:48:39
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Author
1yihui1yihui
Participants
1yihui1yihui
Timeline (top)
commented ×1

After a config patch / restart, OpenClaw can suggest a follow-up command like:

openclaw doctor --non-interactive

That suggestion is sensible in principle, but in some contexts (especially heartbeat-like or approval-constrained surfaces), the suggested command is not actually actionable from where the message is delivered.

The result is a broken follow-up loop:

  • the system gives a reasonable next step
  • but the current interaction surface cannot actually complete it
  • or execution hits approval constraints with no clean completion path

Root Cause

The issue is not that doctor exists or that approvals exist. The issue is that the recommendation is presented as if it were an immediate next step, even when the current surface/session cannot actually complete that step.

Fix Action

Fix / Workaround

After a config patch / restart, OpenClaw can suggest a follow-up command like:

I hit this after a config patch / restart on a local macOS OpenClaw setup.

OpenClaw reported the restart/config patch success and suggested running:

Code Example

openclaw doctor --non-interactive

---

openclaw doctor --non-interactive

---

Exec denied (... approval-timeout (allowlist-miss)): openclaw doctor --non-interactive
RAW_BUFFERClick to expand / collapse

Bug type

UX / operational follow-up flow

Beta release blocker

No

Summary

After a config patch / restart, OpenClaw can suggest a follow-up command like:

openclaw doctor --non-interactive

That suggestion is sensible in principle, but in some contexts (especially heartbeat-like or approval-constrained surfaces), the suggested command is not actually actionable from where the message is delivered.

The result is a broken follow-up loop:

  • the system gives a reasonable next step
  • but the current interaction surface cannot actually complete it
  • or execution hits approval constraints with no clean completion path

Real scenario

I hit this after a config patch / restart on a local macOS OpenClaw setup.

OpenClaw reported the restart/config patch success and suggested running:

openclaw doctor --non-interactive

But when trying to follow that suggestion from the current flow/context:

  • the command hit approval constraints
  • the surface was not a good place to complete that approval loop
  • the result was effectively a non-actionable recommendation

So the experience became: good advice, wrong place.

Expected behavior

One of these:

  1. If the current context can run the suggested command, present it normally.
  2. If the current context probably cannot complete it, say so explicitly.
  3. Route the user to the right place for follow-up (e.g. terminal or approvals-capable web UI).

For example:

  • "Recommended follow-up: run openclaw doctor --non-interactive in terminal/web UI with approvals available."
  • or: "Doctor check deferred because this surface cannot complete approvals."

Actual behavior

The restart/config-patch notice suggests a command that may not actually be executable from the current context, especially when approvals are involved.

This makes the post-restart flow feel less closed-loop than it should.

Why this matters

The issue is not that doctor exists or that approvals exist. The issue is that the recommendation is presented as if it were an immediate next step, even when the current surface/session cannot actually complete that step.

Suggested fix direction

  • Make restart sentinel follow-up messages more context-aware.
  • Distinguish between recommended and actionable here.
  • Provide explicit fallback guidance for constrained contexts.
  • Optionally prefer a lighter read-only health check in contexts where approval-capable execution is unavailable.

OpenClaw version

2026.4.15

Operating system

macOS 15 / Darwin 25.x

Install method

npm global

Model

N/A

Provider / routing chain

N/A

Logs, screenshots, and evidence

Representative failure pattern after following the recommendation:

Exec denied (... approval-timeout (allowlist-miss)): openclaw doctor --non-interactive

This was not a doctor correctness problem; it was an actionability / execution-context problem.

extent analysis

TL;DR

Modify the restart sentinel follow-up messages to be more context-aware, distinguishing between recommended and actionable steps.

Guidance

  • Review the current implementation of the restart sentinel follow-up messages to identify where the context awareness can be improved.
  • Consider adding conditional logic to check the current interaction surface and approval constraints before suggesting a follow-up command.
  • Provide explicit fallback guidance for constrained contexts, such as routing the user to a terminal or approvals-capable web UI.
  • Evaluate the option to prefer a lighter read-only health check in contexts where approval-capable execution is unavailable.

Example

# Pseudocode example of conditional logic for context-aware follow-up messages
if (current_surface == "terminal" && approvals_available) {
  suggest_command("openclaw doctor --non-interactive")
} else {
  suggest_command("Run 'openclaw doctor --non-interactive' in a terminal or web UI with approvals available")
}

Notes

The provided OpenClaw version, operating system, and install method may be relevant for reproducing the issue, but the suggested fix direction is focused on improving the context awareness of the restart sentinel follow-up messages.

Recommendation

Apply workaround: Modify the restart sentinel follow-up messages to be more context-aware, as this approach addresses the root cause of the issue and provides a better user experience.

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…

FAQ

Expected behavior

One of these:

  1. If the current context can run the suggested command, present it normally.
  2. If the current context probably cannot complete it, say so explicitly.
  3. Route the user to the right place for follow-up (e.g. terminal or approvals-capable web UI).

For example:

  • "Recommended follow-up: run openclaw doctor --non-interactive in terminal/web UI with approvals available."
  • or: "Doctor check deferred because this surface cannot complete approvals."
#agent setup#task chaining#parallel task#integration issue#index setup

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 Post-restart suggestion to run `openclaw doctor --non-interactive` is not always actionable in heartbeat / approval-constrained contexts [1 comments, 1 participants]