Why it shows "AI Features are disabled for this file." when I Ctrl+K?

Bug Reports
1

In 0.46.9, no matter which file type it is (.py .bat .vbs even .txt), it always shows “AI Features are disabled for this file.”

It works well in 0.44.11 and 0.45.17.

2 Likes
2

+1
I just updated and and can confirm exact the same behaviour, although I got it with commit message file. I’m however also seeing a lots of other instabilities with agent as well - not showing conversation output but still making changes in the background…

3

… seems to be mainly Sonnet 3.7 related problem with this:

{“toolCallComposer”:{“modelIntent”:“claude-3.7-sonnet”}}

4

I meet this issue also. after update 0.46.9. when I edit .md file, Ctrl+k show “AI Features are disabled for this file.”
but I used Ctrl+k in .py file. this feature is ok

5

same here.

6

not working codebase .

7

same here

8

Same happens in .git/COMMIT_EDITMSG. I have used cmd+K to generate commit messages based on my input but now it’s prevented and I get “AI Features are disabled for this file.” :confused:

1 Like
9

same here

10

Hey, sorry about this, looking into it now!

3 Likes
11

I encountered a similar issue when directly opening the file (I was editing a .tex file) and using Command + K. However, when I opened it as a project (by opening the upper-level folder), it seemed to work normally.

12

I notice this fails 100% of the time (get the message “AI Features are disabled for this file.”) with any model on any file that starts with a .

13

Good catch, reproduced this myself! Will have a fix out soon.

5 Likes
14

Awesome. I can’t get it to modify files under a .github folder. Was going crazy.

15

For your information, I tested release 0.46.10, and it is working now. The issue appears to be linked to a bug where having a dot prefix in the folder name causes everything to stop working.

Possibly related discussion: Simple 'apply' in chat does not work (0.46.9)

1 Like
16

This was my first observation of this as well

1 Like
17

I’ve had the same problem. No dot prefix to the file or any folder. However adding its directory as workspace folder fixed it.

18

I am also experiencing this issue. It happens when a file is either outside the workspace, or one of the parent folders starts with a period. The former is easily fixable but the latter is not. Any bugfix ETA? Thanks!