Skip to content

[Bug] /export-session fails silently on Discord/channel-backed setup since v2026.5.28 #91431

Closed

Description

@OUTLAWORACLETX

Environment

  • OpenClaw: 2026.5.28 through 2026.6.5 (all versions after 2026.5.12 affected)
  • Platform: macOS arm64 (Mac Mini M4)
  • Runtime: Discord channel backend
  • Node: v25.x

Symptom
/export-session and /export commands execute with no output and no error.
Command appears to complete, but no HTML file is produced. No error message,
no partial output, no log entry. Completely silent failure.

Confirmed working: v2026.5.12 — export functions correctly.
Confirmed broken: v2026.5.28, v2026.6.5 — silent no-op.

Not the same as #90844 (which is CLI/ACP backend missing assistant turns —
our setup is Discord/channel mode and produces no output at all, not partial output).

Not fixed by #90873 (template copy path fix — asset path issue is not our symptom).

Steps to reproduce

  1. Run OpenClaw on Discord channel backend
  2. Issue /export-session in any active session
  3. No file is created, no error is shown

Expected: HTML export file written to sessions/ directory with confirmation message.
Actual: Silent no-op, exit 0.

Activity

  1. clawsweeper commented on Jun 8, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I did a careful shell check against current main, and this is already implemented.

    Current main already implements the central Discord/channel-backed export behavior: native command turns carry the real target session into command handling, and the export handler now writes the HTML file or returns a visible error instead of silently doing nothing. The fix is current-main-only in this checkout; no release tag contains the proof commit yet.

    So I’m closing this as already implemented rather than keeping a duplicate issue open.

    Review details

    Best possible solution:

    Keep the current generic native command target-session handling on main and let the next release carry it; the separate CLI/ACP transcript completeness work remains tracked at #90844.

    Do we have a high-confidence way to reproduce the issue?

    No current-main failing repro was established. Source and regression coverage show current main targets the channel session for native commands and returns export success/error text, while the proof commit is not in the latest release tag inspected.

    Is this the best way to solve the issue?

    Yes. The current generic command-target session routing is the maintainable fix because it keeps /export-session channel-agnostic instead of adding Discord-specific export logic.

    Security review:

    Security review: No patch security review applies to this issue triage.

    AGENTS.md: found and applied where relevant.

    What I checked:

    Likely related people:

    • Vincent Koc: Current history/blame attributes the target-session routing, export command implementation, Discord native command context, and related regression test lines to the same proof commit. (role: recent area contributor; confidence: medium; commits: f5935bbca15d; files: src/auto-reply/reply/session.ts, src/auto-reply/reply/commands-export-session.ts, extensions/discord/src/monitor/native-command-context.ts)

    Codex review notes: model gpt-5.5, reasoning high; reviewed against a04de1a0ceac; fix evidence: commit f5935bbca15d, main fix timestamp 2026-06-07T12:32:56+02:00.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.
    on Jun 8, 2026
  3. locked as resolved and limited conversation to collaborators on Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions