URL query param to open chat with initial message

Hello

I would like to redirect my users with their query directly to chat gpt like:
https://chat.openai.com/chat?q=some+initial+question

I have new tab chrome extension and would like to provide ChatGPT like google on start page.

https://homey-app.online/

10 Likes

That would be an excellent idea to be implemented on ChatGPT App

1 Like

Will incorporate this feature in our software within a day when this is released!

2 Likes

For other searching for this knowledge, it has been implemented as requested.
Certainly appears to work for me.

2 Likes

It works with custom GPTs too!

Is this new functionality?

I used it for a little website of mine. It worked a week ago, but now it doesn’t. Anybody got updates on that?

1 Like

I am using this feature to begin new conversations with ChatGPT, but is there also a way to continue a running conversation? I have tried [base url] /c/ds92abfd-cb72-981a-bd0e-6dd134560ffe?q=Hello, but that didn’t work.

3 Likes

It would be great if we can have this feature working again!

I just tried it and it seems to work for me!

1 Like

How did you get this working for your custom GPT? I’m trying /g/g-my-custom-gpt-slug?q=some+query and it’s not working …

1 Like

To be clear, maybe you both can also write how it is not working for you.

For me, if I visit a URL with the q parameter (example URL below), the buggy behavior is as follows:

Example URL:

https://chatgpt.com/?q=Summarize%20https%3A%2F%2Ffrontendmastery.com%2Fposts%2Frethinking-react-best-practices%2F%20in%205%20bullet%20points
  1. Visit the URL above
  2. Initial message appears correctly
  3. Response from ChatGPT starts appearing
  4. After 2 or 3 seconds, it redirects back to the empty “new chat” view

Sometimes this is reversed (not ideal but much better, because the final page is :

  1. Visit the URL above
  2. The empty “new chat” view appears
  3. After 2 or 3 seconds, it redirects to a new chat
  4. Initial message appears correctly
  5. Response from ChatGPT appears correctly

This looks like an unintentional bug, not some new preventative measures introduced by OpenAI.