Just wanted to chime in with my experiences: my Custom GPT has instructions to make links out of titles of topics loaded from my API. When it is TOLD to do it, it makes valid links. But if it decides ON ITS OWN to create a link, the links don’t work. Still trying to figure out how I can tell it to always create the link as I tell it to and when I tell it to rather than on its own.
2 Likes
Hey folks, thanks for flagging this. We have resolved a few issues around generation URL’s. There are a few known edge cases that don’t work well:
- Having the model construct full URL’s on the fly (you should instead pass the full URL back in an Action response)
- Having the model fill in URL details (same as above, you should pass in the full URL and all UTM parameters)
4 Likes
Is there any way to get this functionality to work within standard ChatGPT using Custom Instructions as it had in the past? If the model is provided with an exact link, it can provide a clickable version without issue, but dynamically generated links don’t work.
Specifically, my CI instruct the model to include a Google Search query in markdown format at the end of each response. The formatting is without issue, but not clickable, I’m assuming due to some security feature introduced which originally broke the feature. I can provide the model with the exact link it already generated and all of a sudden it can generate a clickable version.
I’m trying to create a CustomGPT that uses a dummy action to echo the link to the model, allowing it to create a clickable version, but I wish there was an easier way.
Hi, and thanks for your feedback.
I don’t think it is solved. I have a GPT that is instructed to do a search with Bing and just select the best matching search results and provide these links as found by Bing together with a summary. Some of the links are clickable, some are not. It appears to be completely random.
(As a software developer, I’m wondering about how much artificial intelligence is really needed to generate a clickable link…)
Hope OpenAI is able to fix it, because it is very annoying and makes the whole thing somehow unusable for many use cases.
1 Like
Good to see some activity here. But it’s really limiting to force the action to pass the UTM’s. It also removes any dynamic aspect that can be added to the URL via tha actual chat occurring. In short it’s too limiting. Also, really no api I know of has UTM’s with the response…
I am still struggling to get links to work in my Custom GPTs on the web UI. They work sometimes, but not all the time, as they should. They work fine in the Android App all the time.
I have tried Markdown (which is what works sometimes), HTML-like anchor links and even some things that ChatGPT suggested, but none works consistently.
I’ll re-read this thread, but it’s really disheartening.
3 Likes
Still not working for me, but it use to…
If I look at my GPT’s generated response in Chrome Inspector, I can see the anchor, but there is no “href=” text.
I need this fixed as I use the feature to run a TAP DB query after it is created by my custom GPT.
I haven’t used Actions so I don’t understand your response. Can you clarify?
This is an issue in GPT4 as well. The links are not clickable - I can see that when the GPT is generating them, it is actually adding the link, so it is a problem most likely with how the text generated is formatted later. For example:
The href is missing from the link, and it looks just like this: Google Adsense
I have done a bit of testing and it seems to be specifically subpages of a domain are problematic. You can see my chat here:
I hyperlink to google is possible, but not to the adsense subpage.
Same with goodreads. A subpage link gets parsed somehow to remove the link.
This should be easily fixable by openai’s FE team, let’s hope they see this and resolve it.
There may be other intricacies but this is the pattern i could find.
Edit: interestingly enough, in my shared link none of the links are clickable, but in my actual chat the homepages of the websites were proper hyperlinks and clickable.
I’m also struggling with generated links not being clickable. Frustrating because a) I can literally see it type out the URL and then shorten it into a hyperlink and then not being able to click on it. It did the work! And then where did it go?! b) it makes takes away some critical use cases that we all hope was possible with the bing search integration. For example, one of my custom GPTs provides book recommendations and then does an internet search and provides a link where the user can purchase the book (hoping to add affiliate links soon). So the GPT just can’t do half the job if the links aren’t clickable…
For what it’s worth, as a workaround, I’ve been modifying my prompts to say ‘share the generated link and also provide the URL so the user can copy and paste it into a browser’ which helps but not a foolproof instruction and also not as user-friendly as being able to just click on a link.
5 Likes
This isn’t the fix to the issue, however there is a work around where you can grab the link(s) without asking the GPT to provide them again, although it’s not very elegant.
Under the GPTs response you can click the clipboard icon to copy the raw-text format of the markdown GPT used. These links were not visible in the response nor were they clickable (although highlighted blue and provided mouse hover events just like they should have been clickable links).
Unfortunately you will need to likely paste the text in a text editor of some sort to be able to then copy the URLs, but at least this can help solve your concern that re-requesting already provided data affecting rate limits.
How GPT displayed it:
Raw Text Copied to Clipboard Shows Links:
Certainly! Here are the clickable links for the libraries and packages for managing command line arguments in a .NET Framework console application:
1. CommandLineParser: [GitHub Link](https://github.com/commandlineparser/commandline) 2. System.CommandLine: [GitHub Link](https://github.com/dotnet/command-line-api) 3. McMaster.Extensions.CommandLineUtils: [GitHub Link](https://github.com/natemcmaster/CommandLineUtils) 4. NDesk.Options: This library doesn't have a direct GitHub page, but you can find references to it in various legacy .NET projects. 5. Mono.Options: As part of the Mono project, it doesn't have a separate GitHub page, but it is available on NuGet [here](https://www.nuget.org/packages/Mono.Options/)
6 Likes