[wpfleger96]

Relay WebSocket clients in this repo now send a User-Agent of the form <name>/<version> on the upgrade request. The version comes from the build.

Client	User-Agent
buzz-acp	buzz-acp/<crate version>
buzz-cli	buzz-cli/<crate version>
buzz-ws-client (default)	buzz-ws-client/<crate version>
buzz-pairing-cli	buzz-pairing-cli/<crate version>
buzz-audio-client (default)	buzz-audio-client/<crate version>
mobile (relay and huddle sockets)	Buzz-Mobile/<app version>

• buzz-ws-client: every connect path sends the default. A User-Agent in the caller's connect_with_headers headers replaces it, so other consumers can identify themselves without any new API. buzz-cli uses this to send its own name.
• buzz-audio-client: keeps a User-Agent already on the host-supplied request, and adds its default otherwise.
• Mobile: openRelayWebSocket sets the HTTP client's userAgent, which also covers the huddle transport. Startup fills in the app version from package_info_plus. Until that resolves, the value is Buzz-Mobile.

Each client has a test asserting the header on the upgrade request.

[github-actions]

🔐 Codex Security Review

Note: This is an automated, security-focused review generated by Codex.
Use it as a supplement to human review; false positives are possible.

Scope

• Exact PR diff: f3b127e3af5c14d2314faa2b63556c3f51ec6743...cf304085c1b8e363318903b613b29f37f6f4e250
• Model: gpt-6.1-sol

💡 Click "edited" above to see earlier reviews for this PR.

---

Review Summary

Overall Risk: NONE

No concrete security, correctness, or reliability findings in the authorized PR range. The changes preserve authentication headers, host routing, and existing redirect protections.

Findings

No concrete security, correctness, or reliability findings were identified.

Notes

• Review used read-only source inspection. Builds and tests were not run, as instructed.

---

_{Generated by Codex Security Review |
Requested by: @wpfleger96 |
Workflow run}