<!--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> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=463862) </details> <!--IssueSummary end--> Following the work in https://gitlab.com/gitlab-org/gitlab/-/issues/455023 we need to update our editor extensions to support the new `ai_features` scope tokens. Part of this is started for jetbrains but we might need to mark 1 more GraphQL type as `ai_features` per https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin/-/merge_requests/447#note_1922570082 . This is just a matter of [adding `scopes` annotation to the required fields](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149039/diffs?pin=f3269ec7528912e6638b34436ea3bc737c4d8cc3#f3269ec7528912e6638b34436ea3bc737c4d8cc3_22_28) and [adding `authorization_scopes` to the required types](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149039/diffs?pin=813162450c708a69b234465d7644a07b76976032#813162450c708a69b234465d7644a07b76976032_10_10). Now that GraphQL supports fine grained access. We just need to work out exactly which GraphQL queries are minimally needed to make the extension work for each extension. Also since the VS Code extension supports lots more things that aren't related to Duo then we'l also need to recognise that using an `ai_features` token would not support all functionality of the extension.