<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=592230) </details> <!--IssueSummary end--> ##### **UX flow** * Button to trigger Duo chat with prompt for permission suggestions * Button copy similar to “Set token scope with Duo” * Duo chat opens with prompt for user to type in their use case * Similar to “troubleshoot” interaction in failed job * User types their use case in Duo chat * Duo chat returns permission results and UI form populates with permissions * User can interact with Duo for any changes to the permission selection and this repopulates form (subtraction/addition) **Designs** | Button location to trigger Duo chat | |-------------------------------------| | {width=516 height=359} | ##### Approaches 1. If you use the chat widget (could give us structure output) - no changes in AI gateway 1. Con: Parse output from chat needs to be done in FE 2. Using AI gateway with unit primitive (a dedicated prompt for gPAT) 1. Pro: Parse output is easier https://gitlab.slack.com/archives/C06LWENL58F/p1772624322421009