Chat UI Additional Features - Threads, Context & History
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3542117. -->
Reported by: [afoster](https://www.drupal.org/user/594458)
>>>
<p>In collaboration with the #AI-UX Drupal Slack group, we’ve been working on immediate UX improvements for the AI Chat, with the current design direction being a left-hand panel that pushes the admin UI to the right. (<a href="https://www.drupal.org/project/ai/issues/3531279">See issue #3531279</a>)</p>
<p>As part of those discussions, we have identified future improvements that could significantly enhance the AI Chat UX:</p>
<h4> 1. Context-aware chat – ability to specify whether the AI should act on:</h4>
<ul>
<li>The entire site</li>
<li>The current page/node</li>
<li>A specific field or UI element on the page</li>
<li>... likely more contexts needed ...</li>
</ul>
<h4> 2. Multiple chat threads</h4>
<ul>
<li>Switch between different conversations, each maintaining its own history.</li>
</ul>
<h4> 3. Reverting chat history</h4>
<ul>
<li>Ability to roll back a single chat 1 or more turns in the chat thread when the LLM output is not optimal</li>
<li>Whatever actions the agent did should also be unapplied to Drupal</li>
</ul>
<h4> 4. Persistence across navigation:</h4>
<ul>
<li>Ensure chat remains active across screen refreshes or navigation between pages to allow multi-page workflows. </li>
</ul>
<h3>Cursor Example Recording</h3>
<p>Cursor has similar requirements. I recorded a video of how they implemented these types of features. </p>
<p><a href="https://youtu.be/nYsDYRlDWx0">Cursor Demo Video</a></p>
<h3>Feedback Requested</h3>
<ul>
<li>What (if any) of these features should we focus on?</li>
<li>How do we think we can pass the context of "this page" to the chat similar to how it works in XB's AI chat? </li>
</ul>
> Related issue: [Issue #3533631](https://www.drupal.org/node/3533631)
> Related issue: [Issue #3531279](https://www.drupal.org/node/3531279)
issue