Expose the LLM response text from the Assist Pipeline as:

[ondrom111]

Describe the feature

There is currently no variable, event, or hook that contains the LLM response.
This means:

• The last spoken sentence cannot be saved to an entity
• It cannot be translated
• It cannot be displayed on a dashboard
• It cannot be logged
• It cannot be used in automations
• It cannot be processed further in any way

For example, if a user wants to say “translate” and have Home Assistant translate the last LLM reply, this is impossible because the reply text is not available anywhere.

Requested solution

Expose the LLM response text from the Assist Pipeline as:

• a variable (e.g., {{ conversation.response }}), or
• an event (e.g., conversation.response), or
• a way to run an action in the “LLM Response” step with access to the response variable.

Any of these would allow automations to work with the actual text returned by the LLM.

• Language learning (translate last sentence)
• Accessibility features
• Logging conversations
• Displaying responses on dashboards
• Sending responses via notifications
• Debugging LLM behavior
• Advanced automations based on LLM output

Thank you for considering this feature.

Example commands

For example, if a user wants to say “translate” and have Home Assistant translate the last LLM reply, this is impossible because the reply text is not available anywhere.

Use cases

Assist Pipeline already receives the LLM response internally, but Home Assistant does not expose it.
Making the response available to automations would unlock many powerful use cases and significantly improve the flexibility of the Assist system.

Anything else?

No response

[speedracer-chris]

Hi -

I would also really like this feature or something similar for a project I am working on. I would like some method of logging the assist conversation either as events as described here, or a simple switch that turns on logging to a file appending each assist conversation to the end of a text file.

My use case is for storing memory for the assist pipeline, and while it works ok real-time during a conversation, what I would like to do is parse the full log with a powerfull local LLM after the fact and extract critical information that I can store for Assist to use on the next conversation all locally of course.

Thanks!