Repository navigation
Conversation
This was referenced Oct 4, 2026
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
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
Work around the Desktop API's current
chatIDsmessage-search truncation sobeeper messages search --chat ...does not silently return only one message per chat.What changes
When one or more
--chatselectors are supplied, the CLI now:chatIDsfrom/v1/messages/searchSearches without
--chatare unchanged.Why
beeper/desktop-api-mcp#2 documents that the server's
chatIDsfilter silently caps results to one message per chat and marks the response complete. That is especially dangerous for agents because incomplete history looks authoritative.This keeps the CLI honest while the server-side defect remains open.
Merged chats
For merged chats, member chat IDs are included in the client-side match set. Account narrowing is disabled for that case so messages from member chats on different accounts are not accidentally excluded.
Tests
Adds a command-level local-server test that proves:
--chatdoes not sendchatIDsto message search