openclaw - 💡(How to fix) Fix [Bug]: Discord native /status reports discord/undefined and no activity for active channel session [1 participants]

[Bug]: Discord native /status reports discord/undefined and no activity for active channel session

Bug type Behavior bug (incorrect output/state without crash)

Beta release blocker No

Summary Discord native /status in a guild channel reports discord/undefined, zero context, and no activity for the target channel session even when the channel session is active and normal in-message status paths show real session usage.

Steps to reproduce

1. Run OpenClaw 2026.4.5 with Discord native commands enabled in a guild channel workspace.
2. Use native Discord /status by itself inside a guild channel that already has an active session.
3. Observe that the returned status card shows the channel session key but reports discord/undefined, 0 context, and no activity.
4. In the same channel, trigger status through a normal message path, for example appending /status inside a regular message.
5. Observe that the message-path status can show the expected live session usage/model information for the same channel.

Expected behavior Native Discord /status should report the same active channel-session model, context, and activity state as the normal in-message status path for that same guild channel session.

Actual behavior Native Discord /status returns a status card with incorrect metadata, including:

• Model: discord/undefined
• Context: 0/...
• Session: agent:main:discord:channel:<channelId> • no activity

Observed example session key: agent:main:discord:channel:1490775030236450876

OpenClaw version 2026.4.5 (build 3e72c03 observed in /status output)

Operating system Linux 5.15.0-171-generic (x64)

Install method npm global

Model openai-codex/gpt-5.4

Provider / routing chain openclaw -> discord native command session -> openai-codex

Additional provider/model setup details Default agent model is openai-codex/gpt-5.4 with openai-codex/gpt-5.4-mini fallback configured in ~/.openclaw/openclaw.json. Discord runs in guild-channel mode with native commands enabled. The issue is specific to native Discord /status; normal channel-message execution paths can show the expected session metadata.

Logs, screenshots, and evidence

Wrong native /status output observed in Discord:
🦞 OpenClaw 2026.4.5 (3e72c03)
🧠 Model: discord/undefined · 🔑 unknown
📚 Context: 0/200k (0%) · 🧹 Compactions: 0
🧵 Session: agent:main:discord:slash:332887877048598528 • no activity
📌 Tasks: 0 active · 5 total · agent-local
⚙️ Runtime: direct · Think: off · elevated
🪢 Queue: collect (depth 0)

Later observed wrong output with corrected target session key but still bad metadata:
Session: agent:main:discord:channel:1490775030236450876 • no activity

Observed healthy status from the normal channel-session path:
🧠 Model: openai-codex/gpt-5.4 · 🔑 oauth (...)
📚 Context: 50k/272k (18%)
🧵 Session: agent:main:discord:channel:1490775030236450876 • updated just now

Source analysis from installed 2026.4.5 bundle:
- Live native Discord /status path:
  provider-DR2mO1YM.js -> commands.runtime-CVX5D6kT.js -> pi-embedded-DWASRjxE.js -> status-yaHSTeGo.js
- In provider-DR2mO1YM.js native /status branch, code references routeState.sessionEntry
- resolveDiscordNativeInteractionRouteState returns route/effectiveRoute/binding metadata but not sessionEntry
- When sessionEntry is missing, status falls back to slash payload values
- buildDiscordNativeCommandContext hardcodes Provider: "discord" and does not provide a real model
- This matches the observed user-visible output: discord/undefined and empty/no-activity session state

Impact and severity Affected: Discord guild-channel users using native /status Severity: Annoying to workflow-blocking for debugging, because native /status cannot be trusted in affected channels Frequency: Observed repeatedly in the same guild channel Consequence: Operators get incorrect status/debug information and must use a message-path workaround instead of the native command

Additional information Observed workaround: appending /status inside a normal channel message can hit a healthier path and show the expected channel-session metadata.

Grounded implementation clue from bundle inspection:

• The native Discord /status branch appears to use target session key routing inconsistently and/or attempts to read a nonexistent routeState.sessionEntry
• The remaining bad output is consistent with falling back to slash-session payload metadata instead of loading the real target channel session entry from store