"Refactor real-time streams" #3
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
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refactor real-time streams by switching XMTP to global message and conversation streams and writing the agent database to '.xmtp/cli--.db3'
Implement global XMTP message and conversation streams, remove periodic refresh, and adjust DM peer resolution and message formatting. The agent writes to a new database path and filters read receipts.
📍Where to Start
Start with the XMTP hook initialization and stream setup in useXMTP.ts, focusing on
startGlobalMessageStream,startConversationStream, and the updated agent initialization.📊 Macroscope summarized 09d8137. 3 files reviewed, 2 issues evaluated, 1 issue filtered, 0 comments posted
🗂️ Filtered Issues
src/utils/formatters.ts — 0 comments posted, 1 evaluated, 1 filtered
isReadReceiptflags any message whose string content is exactly[readReceipt](line 6). Regular text messages can legally contain that literal, so those messages will be misidentified as read receipts and skipped, causing real user messages to disappear. [ Low confidence ]