You can now pass thread fields through the chat widget — so context about who's chatting arrives with the conversation, not after it.

Pass any thread field value in your widget initialization and it will be set on the thread automatically when a customer starts a chat. Your team opens the thread and the relevant context is already there: which product they're on, what plan they're using, which page they were on, whatever your team needs to triage and respond well.

This closes a gap that existed between Plain's API and the chat widget. Thread fields were already first-class in Plain — you could set them programmatically on email or API threads — but chat-initiated threads had no equivalent. Now the widget is consistent with the rest of the platform.