At this point Claude and Fibery are one unit for me which I’m constantly switching in between. I have adjusted to telling it “Start task #3454” and he goes. Similarly, he/she/it talks to me back in numbers as well (mentioning #3454 as a clickable link).
Sometimes though I have to find an entity with that number, fast. The global search does not allow that right now: For example, entering “133” or “#133” finds lots of entities that have this number, just not the ID first.
Proposed solution: Prioritize searches that start with a hashtag (at least) like #133 to find the next entities that have this number, then show everything else.
This would be very helpful. We often need to search by ID (it’s the easiest thing to pass around). The other frustrating thing is automations often give UUIDs which require a separate step to retrieve the name etc. to be able to search.