Repository navigation
Show and tell: ZeroClaw for CyberOps with XMPP, browser voice, and scoped credentials #12414
CastelloBrancoTecnologia
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We run ZeroClaw as an internal CyberOps assistant. Three things made a difference in day-to-day use: reaching the agent from our chat clients, using voice in the browser, and letting tools authenticate without placing passwords or API keys in the conversation. These are open upstream contributions we have been testing in our deployment.
XMPP for operator chat · #11847
We wanted to reach the agent from the desktop and phone clients we already use. In a test deployment, configure an XMPP account and server, choose the TLS mode that matches your server, and allow only your test JID. Send the agent a read-only question from a desktop or mobile client. For optional legacy OMEMO, verify device fingerprints before trusting them. We tested with Gajim and Conversations.
Browser voice · #12269
Voice is useful when a keyboard is inconvenient or when you want to hear the reply. In a paired browser, open Settings → Browser voice and audio, choose the language and recognition mode, then use the microphone in chat. Enable reading and pick a narrator to hear the answer. The silence timer can send a recognized utterance automatically. Feedback on browser and OS combinations would be useful, especially for on-device recognition.
Scoped credentials in the WebUI · #12408 (draft)
We wanted operators to register a credential outside the chat and let the HTTP tool use it at an explicitly configured HTTPS origin. In Settings → Secrets, add a test API token or HTTP Basic credential, set the origin, and ask the agent to make a read-only request using the alias. Remove the alias and repeat the request to verify revocation. We tested local Bearer, X-API-Key, and HTTP Basic against a protected fixture. The draft also includes external vault references and setup help. We verified OpenBao certificate authentication and scoped KV access at the service level. Live coverage for the other external providers is welcome.
If you try one of these, please share the OS, browser or XMPP client, the PR revision, and any setup step that was unclear. Reproducible problems and implementation feedback are especially useful on the relevant PR. Use disposable credentials and sample endpoints in any screenshots or logs you share.
WebUI screenshots
Browser voice language picker in dark mode.
Scoped API credential form and OpenBao setup help, with a sample alias and destination.
All reactions