Discord Native /status Reports 'discord/undefined' and No Activity for Active Channel Sessions

User-Visible Manifestations

When executing the native Discord /status command in a guild channel with an active session, the following incorrect output is returned:

🦞 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)

In some observations, the session key shows the correct channel ID but metadata remains incorrect:

🧵 Session: agent:main:discord:channel:1490775030236450876 • no activity

Contrast with Working Message-Path Status

When the same channel’s session is queried via the normal message path (appending /status inside a regular message), the output is correct:

🦞 OpenClaw 2026.4.5 (3e72c03)
🧠 Model: openai-codex/gpt-5.4 · 🔑 oauth (...)
📚 Context: 50k/272k (18%)
🧵 Session: agent:main:discord:channel:1490775030236450876 • updated just now

Key Diagnostic Indicators

• Model field shows literal string discord/undefined instead of the configured model (e.g., openai-codex/gpt-5.4)
• Context field shows 0/... instead of actual usage percentage
• Session field shows no activity suffix instead of updated just now
• Session key may reference discord/slash:... instead of discord:channel:... with the correct channel ID

Environment Conditions

• OpenClaw version: 2026.4.5 (build 3e72c03)
• Install method: npm global
• Operating system: Linux 5.15.0-171-generic (x64)
• Discord mode: Guild-channel with native commands enabled
• Default agent model: openai-codex/gpt-5.4

Architectural Analysis

The bug stems from a missing session entry resolution in the native Discord command routing pipeline. The native /status command’s code path attempts to read routeState.sessionEntry to populate status metadata, but this property is never populated by the upstream route resolution function.

Code Flow Breakdown

1. Entry Point: Native Command Invocation

When a user invokes /status as a Discord native (slash) command, the request enters:

provider-DR2mO1YM.js → commands.runtime-CVX5D6kT.js → pi-embedded-DWASRjxE.js → status-yaHSTeGo.js

2. Session Resolution Failure

In provider-DR2mO1YM.js, the native /status branch references routeState.sessionEntry:

// Pseudocode representation of the problematic code path
const routeState = resolveDiscordNativeInteractionRouteState(interaction);
const sessionEntry = routeState.sessionEntry; // ← THIS IS UNDEFINED

if (!sessionEntry) {
    // Falls back to slash-payload metadata
    displayStatus(slashPayloadMetadata);
}

3. Route State Resolution Gap

The function resolveDiscordNativeInteractionRouteState() returns:

{
    route: "...",           // ✓ Provided
    effectiveRoute: "...",   // ✓ Provided
    binding: {...},         // ✓ Provided
    sessionEntry: undefined  // ✗ MISSING
}

The function provides routing metadata (route, effectiveRoute, binding) but never populates sessionEntry, leaving it as undefined.

4. Context Building with Hardcoded Fallbacks

When sessionEntry is undefined, buildDiscordNativeCommandContext() executes with missing data. This function:

• Hardcodes the provider as literal string "discord"
• Fails to resolve the actual configured model from agent configuration
• Cannot lookup the active channel session from the session store

5. Cascading Failure to Status Display

The status rendering engine receives:

{
    provider: "discord",
    model: undefined,       // Results in "discord/undefined"
    contextUsage: 0,        // Results in "0/200k (0%)"
    sessionKey: "discord/slash:..." // Wrong session type
}

Why the Message Path Works

The normal message-path status lookup uses a different code path that:

1. Resolves the channel ID from the message context
2. Queries the session store directly for agent:main:discord:channel:{channelId}
3. Extracts the actual model, context usage, and last activity timestamp from the stored session entry

This path bypasses the broken resolveDiscordNativeInteractionRouteState() function entirely.

Session Key Discrepancy Explained

The session key shows discord/slash:{interactionId} instead of discord:channel:{channelId} because:

• The fallback path uses the interaction's command ID as the session identifier
• It never resolves to the parent channel's session entry
• The correct path would derive the channel ID from the interaction's channel context

Temporary Workaround (Immediate)

Until the fix is deployed, use the message-path status query:

Before (Broken - Native Command):

/status

After (Working - Message Path):

any message content /status

This forces the message routing path which correctly resolves the channel session.

Permanent Fix (For Maintainers)

The fix requires modifications to two functions in the Discord native command pipeline:

Fix 1: Populate sessionEntry in Route Resolution

File: provider-DR2mO1YM.js (or equivalent bundle)

Before:

function resolveDiscordNativeInteractionRouteState(interaction) {
    return {
        route: determineRoute(interaction),
        effectiveRoute: determineEffectiveRoute(interaction),
        binding: resolveBinding(interaction)
        // sessionEntry is missing
    };
}

After:

function resolveDiscordNativeInteractionRouteState(interaction) {
    const channelId = interaction?.channel_id || interaction?.channelId;
    const sessionKey = channelId 
        ? `agent:main:discord:channel:${channelId}`
        : null;
    
    return {
        route: determineRoute(interaction),
        effectiveRoute: determineEffectiveRoute(interaction),
        binding: resolveBinding(interaction),
        sessionEntry: sessionKey ? sessionStore.get(sessionKey) : null
    };
}

Fix 2: Handle Missing Model in Status Context

File: buildDiscordNativeCommandContext function

Before:

function buildDiscordNativeCommandContext(sessionEntry) {
    return {
        provider: "discord",
        model: sessionEntry?.model || undefined,
        // ...
    };
}

After:

function buildDiscordNativeCommandContext(sessionEntry, routeState) {
    // If sessionEntry is missing from routeState, attempt direct lookup
    const resolvedSession = sessionEntry || (
        routeState?.binding?.channelId 
            ? sessionStore.get(`agent:main:discord:channel:${routeState.binding.channelId}`)
            : null
    );
    
    return {
        provider: resolvedSession?.provider || "discord",
        model: resolvedSession?.model || getDefaultAgentModel(),
        // ...
    };
}

Fix 3: Derive Correct Session Key for Status Display

File: status-yaHSTeGo.js (status rendering)

Before:

function resolveStatusSessionKey(routeState) {
    if (routeState.sessionEntry) {
        return routeState.sessionEntry.key;
    }
    return `discord/slash:${interaction.id}`;
}

After:

function resolveStatusSessionKey(routeState) {
    if (routeState.sessionEntry) {
        return routeState.sessionEntry.key;
    }
    // Fallback to channel-based key, not slash interaction ID
    const channelId = routeState.binding?.channelId;
    return channelId 
        ? `agent:main:discord:channel:${channelId}`
        : `discord/slash:${interaction.id}`;
}

Test Case 1: Native Command Status in Active Channel Session

Setup:

• Ensure a session exists for a known channel ID (e.g., 1490775030236450876)
• Verify session has non-zero context usage

Execution:

/status

Expected Output:

🦞 OpenClaw 2026.4.5 (3e72c03)
🧠 Model: openai-codex/gpt-5.4 · 🔑 oauth (...)
📚 Context: 50k/272k (18%)
🧵 Session: agent:main:discord:channel:1490775030236450876 • updated just now
📌 Tasks: 0 active · 5 total · agent-local
⚙️ Runtime: direct · Think: off · elevated
🪢 Queue: collect (depth 0)

Pass Criteria:

• Model field shows openai-codex/gpt-5.4 (not discord/undefined)
• Context shows non-zero percentage
• Session key references discord:channel:{channelId}
• Session shows updated just now (not no activity)

Test Case 2: Comparison with Message-Path Status

Execution:

What's the current status? /status

Verification: The native command output and message-path output should show identical:

• Model name
• Context percentage
• Session key
• Last activity timestamp

Test Case 3: New Session Status (No Active Channel Session)

Setup: Invoke /status in a channel with no prior session.

Expected Output:

🧵 Session: agent:main:discord:channel:{channelId} • no activity

Pass Criteria:

• Session key still shows discord:channel:{channelId} (not discord/slash:...)
• Model field should show configured default model (not discord/undefined)

Test Case 4: Guild vs DM Channel Behavior

Execution: Test /status in both guild text channels and DM channels.

Pass Criteria: Both channel types should show consistent session resolution behavior with correct channel-based session keys.

Automated Verification Script

#!/bin/bash
# Verify Discord native /status fix

EXPECTED_MODEL="openai-codex/gpt-5.4"
CHANNEL_ID="1490775030236450876"
EXPECTED_SESSION_PREFIX="agent:main:discord:channel:${CHANNEL_ID}"

# Capture /status output (requires Discord API or test harness)
STATUS_OUTPUT=$(get_discord_status_output)

# Check Model field
if echo "$STATUS_OUTPUT" | grep -q "Model: $EXPECTED_MODEL"; then
    echo "✓ Model field correct"
else
    echo "✗ Model field incorrect"
    exit 1
fi

# Check Session key format
if echo "$STATUS_OUTPUT" | grep -q "Session: $EXPECTED_SESSION_PREFIX"; then
    echo "✓ Session key correct"
else
    echo "✗ Session key incorrect"
    exit 1
fi

# Check for no-activity indicator should NOT be present
if echo "$STATUS_OUTPUT" | grep -q "• no activity"; then
    echo "✗ Still showing 'no activity' for active session"
    exit 1
else
    echo "✓ Activity status correct"
fi

echo "All verifications passed"

Environment-Specific Traps

1. DM Channels vs Guild Channels

• Symptom: Fix works in guild channels but DM sessions show discord/undefined
• Cause: DM channels may have different ID formats or session key structures
• Mitigation: Ensure session key derivation handles both channel and dm prefixes

2. Multiple Sessions Per Channel

• Symptom: Status shows wrong model's data for multi-agent setups
• Cause: Channel may have multiple concurrent sessions with different agents
• Mitigation: The fix should respect the agent dimension in session keys (e.g., agent:main:...)

3. Cached Route State

• Symptom: Fix appears to work but reverts after bot restart
• Cause: Old route state may be cached in memory
• Mitigation: Clear session store cache or restart the OpenClaw process completely

4. Native Command vs Message Command Conflict

• Symptom: Both native and message-path /status show incorrect data
• Cause: The session store lookup may be failing independently of the route resolution
• Debug: Verify session store is accessible and contains entries for the target channel

User Misconfigurations

5. Missing Agent Configuration

• Symptom: Model shows discord/undefined even after fix
• Cause: No default agent model configured in ~/.openclaw/openclaw.json
• Fix: Ensure agents.default.model is set:

{
  "agents": {
    "default": {
      "model": "openai-codex/gpt-5.4"
    }
  }
}

6. Discord Native Commands Not Enabled

• Symptom: Native /status never executes the native command path
• Cause: Native commands disabled in Discord Developer Portal or OpenClaw config
• Fix: Enable native commands in both Discord app settings and OpenClaw config

7. Interaction Endpoint URL Misconfigured

• Symptom: Native commands return generic errors or fall through to message handlers
• Cause: Incorrect INTERACTIONS_ENDPOINT_URL pointing to wrong deployment
• Fix: Verify endpoint URL matches the deployed OpenClaw instance

Version-Specific Considerations

8. Build Hash Mismatch

• Symptom: The fix references files with different hash suffixes than installed version
• Cause: Version 2026.4.5 may have multiple builds
• Verification: Confirm build hash in status output matches expected fix target

Logically Connected Error Patterns

• discord/undefined model display — General symptom of session entry resolution failure across any command path that relies on route state
• no activity session status — Indicates session store lookup returned null or stale entry
• unknown API key indicator — Correlated symptom when session metadata is missing provider/key information
• Slash command vs message command divergence — Related to inconsistent routing between Discord interaction types

Historical Context

• Session key format changes (v2026.x) — Earlier versions may have used different session key structures, causing lookup failures when mixing versions
• Native command beta limitations — Native commands feature was noted as beta; this bug may be related to incomplete session binding implementation
• Channel vs DM session handling — Prior issues with DM sessions not persisting correctly may share root cause patterns with this bug

Related GitHub Issues

• Session metadata missing for native commands — General tracking issue for native command context propagation
• Discord provider model resolution — Provider-specific model resolution failures across Discord command types
• Route state lifecycle management — Issues with route state not being properly maintained across interaction phases

Diagnostic Commands for Related Issues

# Check session store contents
openclaw session list --filter discord

# Verify route resolution in debug mode
DEBUG=openclaw:route openclaw start

# Dump session entry for target channel
openclaw session dump agent:main:discord:channel:1490775030236450876