John Lindquist

Awesome, thanks, super helpful. Are you the admin of the machine you're on? Or using VPN? This line is curious: ``` Error: EROFS: read-only file system, open ``` It's due...

Can you try this fix? https://github.com/johnlindquist/kit/issues/984#issuecomment-1379993381 The line: `[2023-01-18 11:55:31.554] [info] node missing` is saying that something went wrong setting up node at `%USERPROFILE%\.knode`.

@Dyvd4 Does this happen every time you try to open the prompt? Does quitting and trying again fix it?

@Dyvd4 Thanks for getting back to me. Do you see anything suspicious in either of these logs that may hint at the original error? Main.log: %USERPROFILE%\AppData\Roaming\Kit\logs\main.log Kit.log: %USERPROFILE%.kit\logs\kit.log

@Dyvd4 If you could create a gist of each, then paste the links here, that would be great!

You'll also need to manually start the keyboard watcher to snippets to run: 

You may need to hide the prompt first: ```js // Name: Testing Keyboard Type import "@johnlindquist/kit" await hide() await keyboard.type(`Hello world!`) ``` [Open testing-keyboard-type in Script Kit](https://scriptkit.com/api/new?name=testing-keyboard-type&url=https://gist.githubusercontent.com/johnlindquist/74998181cc29d7a9e99a76af366d8cb6/raw/44471b82a865ed2823d9ec6ebccdf471bcd699ca/testing-keyboard-type.js") Also, some apps...

@danielo515 If you adjust your log level to "silly", do you see it tracking your keystrokes in ~/.kit/logs/kit.log? 

Yeah, it's definitely possible. Does this fix it?  I can try and add some logic of something like: "if hasn't detected a keystroke in...

I would trying quitting Kit.app then disabling/re-enabling permissions, then re-opening Kit.app. OSX permissions can be finicky