@ Command broken in Custom GPTs - Filed a Bug report to OpenAI.

Holger Morlok

Aug 1 (edited) • AI Hacks/ Tools

Sadly enough, the @ command’s busted in custom GPTs rn, seems like since /agent or /study mode came around the corner.

Hint: For everyone not knowing: also in a Custom GPT you can use the @ key to call other GPTs.

Workaround:

Even though it's still very restrictive compared to what you can do in a Custom GPT:

use regular chats - @ works there, just wait a sec for tons of GPTs.

Voice responses are glitchy too (clicks, no replies, or sounding weirdly robotic etc.).

ChatGPT 5 precursor? Who knows.

I filed a bug report with OpenAI ‘cause reporting’s selfishly helpful:

fixes what bugs you and helps us all!

My 2025 tally:

1 major EC card reader bug:

(crashed connections across Switzerland/Europe, needing reboots)

I was greeted with contempt, firstly. Because I got the response like: "It works for us."

BUT, they finally fixed it in the end.

38 Visual Studio/VS Code bugs (e.g., resetting to Windows default language on updates):

3 OpenAI bugs:

1 for the broken @ now in the Custom GPT.

1 Like, Google Drive access broke ‘cause of an invalid API key. <- fixed.

1 for Custom GPTs, Or, try saving a Custom GPT with long conversation starters using weird chars like #@ - it crashes with vague errors like ‘An error occurred.’ Annoying for newbies, right?

and more.

This is not to boast. BUT, to make you aware of how many bugs there are that either no one knows yet about or doesn't know how to handle. We want them gone. :-) Just imagine how many people one fix or issue you'll tell developers about may help you AND others in return....

On the other side this shows what we think how many bugs are there, actually.

When we think or hope: Everything should be running smoothly.

Really? I bet you can sing a song about that, like it's sooo much not the case. LOL.

OpenAI needs better parsing or clearer messages!

Then there’s this gem, in case how weirds bugs can get and still the cause is very apparent later on:

Drinking Coke crashes application

---

One Developer reports working for a project team delivering a financial compliance application.

Shortly after delivery, the helpdesk received a support ticket where an end user described an issue with the web application, saying:

‘it crashes every time I drink Coke.’

The issue was initially dismissed as a joke, and ignored. But when the user persisted, adding that the application worked fine when he drank coffee, a member of the project team decided to look into the issue.

It turned out that the online web form had a time-out feature that caused the application to log out when the page was left idle for longer than 15 minutes.

As the Coke vending machine was on the 11th floor, it would take the user a good 15 minutes to get there and back. The coffee machine, however, was just a few cubicles away...

Bugs suck, lol, but reporting them saves us all (sorry for the French!).

File your own bug reports, it’s not boasting, it’s helping everyone! Only if you want to for sure.

And, who knows? It may even encourage people to send bug reports about the app you've developed and already help to make it soooo much better.

Share workarounds below to keep our projects moving.

Creators are killing it!

P.S.: Sorry, for my still very bad English and sometimes getting way too technical. LOL.

AI assistant tool wipes out entire company database | Gravitas

https://youtu.be/Y44UCaFCkbg?si=YKrr-S73Fl7Fons-

6 comments