You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] /export-session fails silently on Discord/channel-backed setup since v2026.5.28 #91431
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.
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
Run OpenClaw on Discord channel backend
Issue /export-session in any active session
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.
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:
Discord native commands carry a target session: The Discord native command context includes both the slash interaction SessionKey and CommandTargetSessionKey, preserving the channel/bound session that command handlers should operate on. (extensions/discord/src/monitor/native-command-context.ts:55, a04de1a0ceac)
Command state is retargeted before handlers run:initSessionState resolves CommandTargetSessionKey and substitutes it as the active session key before inline command handling, so channel-backed native commands reach /export-session on the target conversation session. (src/auto-reply/reply/session.ts:252, a04de1a0ceac)
Export handler writes and confirms the file:buildExportSessionReply resolves the export target, returns visible errors for missing sessions/files, writes the HTML export, and returns Session exported! with the output path and entry count. (src/auto-reply/reply/commands-export-session.ts:258, a04de1a0ceac)
Fix timestamp: The proof commit is fix(e2e): cancel timed out response reads, committed 2026-06-07T12:32:56+02:00. (f5935bbca15d)
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.
Activity
clawsweeper commentedon Jun 8, 2026
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-sessionchannel-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:
SessionKeyandCommandTargetSessionKey, preserving the channel/bound session that command handlers should operate on. (extensions/discord/src/monitor/native-command-context.ts:55, a04de1a0ceac)initSessionStateresolvesCommandTargetSessionKeyand substitutes it as the active session key before inline command handling, so channel-backed native commands reach/export-sessionon the target conversation session. (src/auto-reply/reply/session.ts:252, a04de1a0ceac)buildExportSessionReplyresolves the export target, returns visible errors for missing sessions/files, writes the HTML export, and returnsSession exported!with the output path and entry count. (src/auto-reply/reply/commands-export-session.ts:258, a04de1a0ceac)src/auto-reply/reply/session.test.ts:1266, a04de1a0ceac)src/auto-reply/reply/session.ts:252, f5935bbca15d)fix(e2e): cancel timed out response reads, committed 2026-06-07T12:32:56+02:00. (f5935bbca15d)Likely related people:
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.