auto completion in script editor for embedded is an issue

Hello,
Whenever I'm trying to enter a script (whatever java, apple, shell ) there is an auto completion that either wipes out what I type : example if I'm trying to type File I end up with F..l. and similar things. Sometimes when deleting the last character and go back to the first one I can type the entire word...But forget about a whole script For the time being I'm trying to type in Bbedit and copy and paste, not very user friendly. I've read about the fact that I should disable auto-completion in Script Editor but no effect. I'm also using ScriptDebugger while it works and disabled there what I thought could interfere

short video to illustrate: I was trying to type Teel https://youtu.be/kSrfEuTYkxE
the video capture somewhat prevented any further action with the keybaord
And most of the time I've got to force quit Hazel when I'm in this situation

Thanks for your help in this

I'm with a Mac mini pro with Tahoe 26.4.1 (25E253) French parameters

It should follow Script Editor's preferences. I'll look into it to see if there was a change in the OS breaking this.

I just installed Hazel on a new MaxBook Neo with almost no other software, Script Editor completion disabled and the issue remains.

Just noticed that this seems to happen only when I start typing on the first line, If I start with a linefeed (return) then the typing seems to work OK ??
It's more complex, I'll try to make more comprehensive video. If in the middle of the script some letters will start the "dot" feature and reverting pack to first letter not always work. And I en up with the turning wheel and have to force quit...I'll put the link to the video when done ...

https://youtu.be/Z2Zi2biQHOo

This is still with the setting turned off in Script Editor, right?

Yes, I had mad a screen copy of script editor settings but I can't attach it here. I've tested before re-installing the apps that can auto-complete such as script debugger or others...
Am I the only one with this behavior ?

I can't replicate it on Sequoia and I'm having problems with my Tahoe install at the moment so can't test it. If anyone else has any data points on this, chime in.

would the logs show something of the input in the embedded scripts ?

Ok, finally got a chance to look into this. It seems that on Tahoe, they changed the default state. Before Tahoe, the setting was set to be off but on Tahoe, it's set to be on by default. I need to tweak the code to take this into account.

Fine, Thank you, I'll wait for the fix...

Apparently disabling functions at the keyboard settings level has fixed the problem

BTW, if you want to test the fix, email in to support. I can send you a link to a test build if you'd like.