`canSendRequest` returns undefined on activation even though constent has been given

[benibenj]

Testing #213552

Used Cat sample extension to test this. Please correct me if I misunderstood something

1. Added the following code to the end of the activate method (so it runs on activation)

vscode.lm.selectChatModels({ family: 'gpt-3.5-turbo' })!.then(models => {
        if (models.length > 0) {
            const [first] = models;
            const response = context.languageModelAccessInformation.canSendRequest(first)
            console.log('Can send request:', response);
        } else {
            console.log('No chat models available');
        }
    });

2. Run extension

   • Log: Can send request: undefined => This is expected, consent has not been given yet

3. Send a chat message using the @cat participant (@cat Hello World)

   • Consent is requested => Accept

4. Restart the extension

   • 🐍 Log: Can send request: undefined

Consent has been given by now, so the expected response would be true?
When sending another @cat Hello World message, consent is not requested again.

[jrieken]

Nice find!

[vscodenpa]

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been releaased