-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
openclaw doctor does not indicate which agent's auth state it is reporting when multiple agent stores exist #71867
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
When multiple agent stores exist (e.g. \�gents/main\ and \�gents/coder), \openclaw doctor\ reports auth status without identifying which agent's store the result comes from. This makes it impossible to diagnose per-agent auth drift without inspecting files manually.
Version
OpenClaw 2026.4.23 (a979721)
Context
OpenClaw stores per-agent auth tokens in separate files:
When agent stores diverge (e.g. \�gents/coder\ has a valid token, \�gents/main\ has an expired one), doctor reports the stale state without identifying which agent is the source. This sent debugging in the wrong direction for an extended time.
Expected Behavior
Doctor output should include the agent id being checked, e.g.:
\
Model auth (agent: main)
Model auth (agent: coder)
\\
Or at minimum, call out when auth state differs between agent stores.
Actual Behavior
Doctor reports a single generic auth status line with no indication of which agent's store was checked.
Impact
Medium — makes debugging per-agent auth drift significantly harder, especially for users with multiple agents (main, coder, operator, etc.)