>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3559504. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Toggling between AI Context local tasks losing content<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Blocked by: </strong>[#XXXXXX] (New issues on new lines)<br> <strong>Additional Collaborators: </strong> @username1, @username2<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This is a core issue, so not sure what to do here, but this is annoying, so we should keep it in mind when doing the redesign/rearchitecture.</p> <p><strong>Steps to reproduce:</strong></p> <ol> <li>Requires <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_context/issues/3555225" title="Status: Closed (fixed)">#3555225: Add a single global context, making Vienna Driesnote AI demos much simpler</a></span> (will be committed on 23 Nov 2025)</li> <li>Fill in the global context and then click on "Contexts" local task</li> <li>Go back to Global AI Context, and your global context content will be gone</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>TBD</p> <p>We are going through a full redesign/rearchitecture so it's not clear that the global context will remain like it is now, but this is a general issue that we should keep in mind when redesigning.</p> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <p>January 2026 (before Drupal CMS 2.0)</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Keep in mind during redesign</li> <li>If global (or similar forms) are remaining, keep this UX issue in mind when redesigning</li> <li>If needed, create a workaround or find a core/contrib workaround to help with this</li> </ul> > Related issue: [Issue #3559379](https://www.drupal.org/node/3559379) > Related issue: [Issue #3555225](https://www.drupal.org/node/3555225)