sourcegraph
PUT THE "@" SYMBOL BACK BELOW THE TEXT BOX AND LEAVE.IT.ALONE
Version
1.98.2
Describe the bug
Whilst the chat below speaks for itself, I reiterate that this is an absolutely ridiculous UI/UX change that no one asked for.
Consider especially new users who have never ever used Cody for the first time. As I said, it was the first thing that I (and many others) look for. Anyone can go to GPT/Claude etc. directly to paste in code. We use this tool specifically to be able to directly and EASILY add file context ourselves.
Kids DO use this app. Not everyone is a cognitive genius. For most humans when you remove something that has always been there, the first thing they think when they cannot find it again or see that it simply changed appearance. Is that it was removed.
You guys have been pushing some really aggressive and frankly very reckless changes recently in addition to all the downtime. Maybe it's time to take a lesson of the "If it ain't broke, don't fix it" line. (Also give us Deepseek back).
Thanks (and posted specifically because an employee of Sourcegraph told me to)
Expected behavior
Normal cognitive human beings need a button to know that it is possible to add file context to the chat. It is a feature that ChatGPT/Claude etc. all have visible. It makes no sense to remove it in Cody and make the user think it doesn't immediately exist.
Those of us with EU keyboards are also not in favour of having to press ALT_GR+2 to get the "@" symbol anyway. It's a highly annoying keyboard combo on our keyboards vs. the American SHIFT+2. Which makes a mouseclick for EU users much more efficient in this case anyway.
ELI5: Just leave the button alone! You aren't out of space and it isn't hurting anyone.
Additional context
I opened up Cody. Was told to update the extension (as I am every day basically lol) and of course my "@" button disappears. First thing I think is that it has been removed because I cannot find it again. Because there is a file and folder in my chat, I now thought it is a bug that they are still there.
This is just a terrible design change from every single angle. Just put it back for goodness sake and leave it alone. Understand that not everyone using this application is a genius and basic accessibility UI/UX principles should be upheld.
See also this: https://uxplanet.org/ui-ux-design-removing-core-features-26a37fbf461e
and this: https://www.smashingmagazine.com/2024/05/hidden-vs-disabled-ux/
tl;dr - Show what is NEEDED. There is no clutter here.
