Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Enter' key is interpreted as a new line instead of the end of the prompt. #79

Open
slimjimo opened this issue Jan 26, 2023 · 20 comments
Open

Comments

@slimjimo
Copy link

No description provided.

@ertoorule
Copy link

It can also be a key combination like shift+enter

@slimjimo
Copy link
Author

Yep, both the enter key and shift+enter are interpreted as starting a new line. No key/key combination on my keyboard allows for me to signal the end of the prompt, meaning I have to manually click the send button.

@aaajhs
Copy link

aaajhs commented Jan 28, 2023

I'm seeing the same behaviour. This was not the case just a few days ago, which leads me to think this is a bug.

@jnsw
Copy link

jnsw commented Feb 2, 2023

what do we do now?

@kleineluka
Copy link

Wait for the developer to fix it, although this project seems abandoned as of now. Maybe a fork or PR can do the trick.

@olerap
Copy link

olerap commented Feb 13, 2023

For now you can use tab to highlight the send button and then press enter.

@vincentor
Copy link

this annoys me too, hope to fix it soon.

@eddiewang
Copy link

to save someone some time just throw this in right at the top of before-input-event event:

        if (input.type !== "keyDown" && key == "Enter") {
          // press main > form > button
          contents.executeJavaScript(
            `document.querySelector('main form button').click()`
          );
        }

This is due to the ChatGPT mobile wanting to ensure Enter keypresses default to multi-line input.

@paulmoons
Copy link

to save someone some time just throw this in right at the top of before-input-event event:

        if (input.type !== "keyDown" && key == "Enter") {
          // press main > form > button
          contents.executeJavaScript(
            `document.querySelector('main form button').click()`
          );
        }

This is due to the ChatGPT mobile wanting to ensure Enter keypresses default to multi-line input.

Where? Can this be done by the end user?

@AccessRetrieved
Copy link

to save someone some time just throw this in right at the top of before-input-event event:

        if (input.type !== "keyDown" && key == "Enter") {
          // press main > form > button
          contents.executeJavaScript(
            `document.querySelector('main form button').click()`
          );
        }

This is due to the ChatGPT mobile wanting to ensure Enter keypresses default to multi-line input.

Put this in the index.js in the before-input-event and delete the forge.config.js file. It generates an error while running locally.

I just created an automator application that runs the app with npm run start and changed the app icon. Works perfectly now

vid.mp4

@AccessRetrieved
Copy link

to save someone some time just throw this in right at the top of before-input-event event:

        if (input.type !== "keyDown" && key == "Enter") {
          // press main > form > button
          contents.executeJavaScript(
            `document.querySelector('main form button').click()`
          );
        }

This is due to the ChatGPT mobile wanting to ensure Enter keypresses default to multi-line input.

Where? Can this be done by the end user?

Download the repo and run it locally.

@paulmoons
Copy link

Unfortunately, this is beyond my scope. I was hoping for something a little more userland. Ugh. Hopefully the author can apply the fix.

to save someone some time just throw this in right at the top of before-input-event event:

        if (input.type !== "keyDown" && key == "Enter") {
          // press main > form > button
          contents.executeJavaScript(
            `document.querySelector('main form button').click()`
          );
        }

This is due to the ChatGPT mobile wanting to ensure Enter keypresses default to multi-line input.

Put this in the index.js in the before-input-event and delete the forge.config.js file. It generates an error while running locally.

I just created an automator application that runs the app with npm run start and changed the app icon. Works perfectly now

@eddiewang
Copy link

@paulmoons I created a MR for this here #92 - if the maintainer merges and rebuilds, this should fix any issues you have with the Enter key.

Hopefully this helps!

@paulmoons
Copy link

@paulmoons I created a MR for this here #92 - if the maintainer merges and rebuilds, this should fix any issues you have with the Enter key.

Hopefully this helps!

Thanks!

@Midicii
Copy link

Midicii commented Feb 27, 2023

No Code Solution:

Screen.Recording.2023-02-27.at.3.37.26.AM.mov

@paulmoons
Copy link

No Code Solution:

Yeah, thanks. It's a nice solution but it needs to be applied every time the app starts as the screen size isn't remembered. Thanks though!

@ssapsu
Copy link

ssapsu commented Mar 1, 2023

No Code Solution:

you're really a genius.

@gmshrek
Copy link

gmshrek commented Mar 2, 2023

ChatGPT-Box.dmg

It supports custom enable and send shortcut keys.

@paulmoons
Copy link

Solution is here folks: https://goodsnooze.gumroad.com/l/menugpt

@katzkuma
Copy link

There's another no-code solution:
I've been using this key combination like Command + Enter. It works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests