Skip to content
Discussion options

You must be logged in to vote

@human5810, not as a built-in channel today. I do not see a current XMPP channel or a tracked XMPP feature issue.

The right next step is a feature request if you want this tracked. Useful scope details:

  • basic one-to-one XMPP messages only, or group chat/MUC too;
  • TLS requirements;
  • whether OMEMO/E2EE is required for the first slice;
  • how sender authorization should map into peer groups;
  • whether outbound-only, inbound-only, or full bidirectional chat is needed.

Until then, the workaround is to bridge XMPP into a supported surface, for example a webhook or another channel, and let ZeroClaw handle the message after it reaches that supported surface.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@CastelloBrancoTecnologia
Comment options

Answer selected by Audacity88
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants