Greptile Summary

Sanitized assistant NO_REPLY silent tokens from chat history responses to hide internal control messages from users.

• Added sanitizeSilentReplyTextForHistory function that detects and strips NO_REPLY tokens exclusively from assistant messages
• Applied filtering consistently across three message formats: string content, text fields, and content block arrays
• Sanitization occurs after directive stripping and truncation in the chat history pipeline
• User messages containing "NO_REPLY" are explicitly preserved unchanged
• Added comprehensive test coverage verifying all three message formats and role-based filtering

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The implementation is straightforward, well-structured, and follows existing codebase patterns. The logic correctly differentiates between assistant and user messages, handles all content formats, and includes thorough test coverage with multiple edge cases (whitespace variations, different content structures). The regex patterns in isSilentReplyText are properly designed to avoid false positives. The sanitization order (directive stripping → truncation → silent token removal) is logical and preserves data integrity.
• No files require special attention

_{Last reviewed commit: e223ad2}

Investigated the Windows shard failure and pushed a narrow fix to this PR branch.\n\nRoot cause: mutates ; on CI this can race under concurrent test execution and occasionally make undiscoverable in .\n\nFix: run this test suite sequentially () so env-mutating plugin-loader tests do not interleave.\n\nCommit: 9554dfd\n\nCould you re-run the failed Windows checks?

Correction with full details:\n\nInvestigated the Windows shard failure and pushed a narrow fix to this PR branch.\n\nRoot cause: src/plugins/loader.test.ts mutates OPENCLAW_BUNDLED_PLUGINS_DIR; on CI this can race under concurrent test execution and occasionally make memory-core undiscoverable in preserves package.json metadata for bundled memory plugins.\n\nFix: run this test suite sequentially (describe.sequential) so env-mutating plugin-loader tests do not interleave.\n\nCommit: 9554dfd\n\nPlease re-run the failed Windows checks.

Thanks for the PR! Multiple PRs address issue #27238. Keeping #27258 as the earliest submission. Closing to reduce noise. This is an AI-assisted triage review. If we got this wrong, feel free to reopen — happy to revisit.