u/djpadz

Out of nowhere, CarPlay happily announced that it was receiving battery information from my bZ. Did they finally fix EV reporting, or was this a fluke?

I'll be the first to admit that I tinker a lot with my crustacean ("I'll take things that sound dirty but aren't for $100, Alex"), but all of a sudden, the chat window in the macOS native app stopped responding. Here's what I know:

• I'm running 2026.5.18, but have seen this behavior with 2026.5.12 and 2026.5.7. I've kept version parity between my server and my client.
• Using the web UI or TUI work fine.
• I've unpaired and re-paired my Mac app.
• The app can do everything except chat; chat histories come up fine, I can make settings changes, etc. It's just that when I type a message, I get the ••• for about a tenth of a second and then it disappears without any response.
• I'm using a kiro gateway on my openclaw gateway, and I don't see the incoming message from the app chat making it to the kiro gateway (for the TUI and GUI both show the message going over to the kiro gateway).
• When sending messages from the app, they appear to come across with no sessionId or chatId.

I think that last point is part and parcel to the problem, but I've gotta imagine that I'd be seeing a lot more chatter about it if it was a widespread bug.

[edit] One more thing... Each time I launch the app, I get a node pairing prompt, twice. After approving them the prompts stop, but chat still doesn't work. When I try to approve the node pairing request via the CLI, I get:

nodes approve failed: GatewayClientRequestError: missing scope: operator.admin

(this happens even though my CLI instance definitely has the operator.admin scope.)

Does anybody have any ideas?

Thanks!