Repository navigation
feat(headless): capabilities for the daemon and CLI - #4215
Merged
Merged
Conversation
sendMessage can now be told which message it replies to or corrects, instead of only taking that from the chat's UI state.
Sending XEP-0444 reactions moves from the web UI into headless, so that clients other than the web UI can react to messages.
jcbrand
force-pushed
the
headless-from-daemon
branch
from
November 3, 2026 06:21
cfc87c7 to
73f6f13
Compare
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.
The headless capabilities that
@converse/daemonand@converse/cli(#4200) need, split out so they can land on their own. None of them are daemon-specific, so the web UI can use them too.New in headless
api.contacts.resolve: resolve a name to roster contactsapi.rooms.discover: list the rooms a MUC service hosts, following XEP-0059 pagingsendMessageoptions to reply to, or correct, a given messageapi.reactions.send: send XEP-0444 reactions, encrypted when the chat uses OMEMOapi.archive.search: XEP-0431 full-text search of the server archive. Matches are held in their conversations, with placeholders for the history around them that isn't fetched yet.fetchArchivedMessagesreturns the archive query's answerMessage.getArchiveIDandMessage.getReferenceIDFixes
afterMessageCreatedlisteners after the reactions plugin get the messageapi.rooms.openwith a list of JIDs no longer throws aReferenceErrorsendMessagerefuses to correct a message that isn't an editable one of oursKnown gap
An archive search leaves a room's private messages out, because there's no correct place to hold them yet. They used to land in a 1:1 chat with the room's JID. Holding them in the occupant's chat is follow-up work.