fix: restore detailed chat-mode replies#601
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Answered in chat.delivery placeholder during assistant recoverysourceReply.textas the visible assistant answerRoot Cause
In webchat/direct chat, OpenClaw sends the human-facing answer through the
messagetool, then Codex emits a private final assistant message:Answered in chat.CrewCmd was treating that private final as the chat answer and recovery selected it before the later delivery-mirror message.Verification
pnpm test src/lib/chat-recovery.test.ts src/app/api/chat/route.test.tsnpx tsc --noEmitfor the staged filesNotes
The branch was rebased on current
origin/mainin a clean temporary worktree before pushing. The main checkout still has unrelated pre-existing mobile changes that are not included in this PR.