Chat autonaming

Questions
1

How to force Pickaxe name chats in a particular name? I really need to control this. For example:

  1. Initial CBT session.
  2. Then depending on Pickaxe settings.
2

There is no way to directly control the chat auto-naming in the current system.

3

I see. Okay. :slightly_smiling_face:
Hope you will consider this function, though I understand that’s far from a priority.

4

If not a method for renaming the chats to something useful, can we at least have less of this naming convention:

  • The user is seeking
  • The user is focused
  • The user is training
  • The user requested

The issue here, Mike, is that in a relatively narrow sidebar, most of the text is consumed with these messages making it virtually impossible to navigate your chats.

Personally, when I use my own Pickaxe, I write something like ‘U15 1500m Plan:’ and then my query after the ‘:’, as this typically forces the pickaxe to name the chat with this. However, whilst its a fix for my use, its not a slick UI/User Journey and when a user has ten or so conversarions all starting with “The User requested…” its not helpful to them at all!

4 Likes
5

Can’t agree more. This naming convention is not very user-friendly at all. Esp considering that the conversation name is truncated after about 25 characters in the left panel - leaving very little signal to the user as to what the topic of the conversation was when coming back to look for a past conversation.

This is obviously amplified by the fact that conversations cannot be deleted - so the sheer amount of noise plus the lack of signal makes the UX very difficult to have confidence it.

As a platform enabling those that hope to build things for other users, I would offer that it’s very important to understand the end-end users. These are not your customers, rather the customers of your customers. I am trying to be constructive here, I am not criticizing. But it’s these small things that are preventing me from deploying solutions on pickaxe. Small things matter in product/ux.

I hope you consider this feedback in context of your roadmap.

3 Likes
6

I’ll fix this. I believe the issue is once we released the AI summary system for conversations in the backend, we started piping the first 40 characters of that summary into the end-users nav bar as conversation titles.

3 Likes
7

Following, I’m also looking for this. I set a naming convention in the prompt frame and it works for the chat window but looking at how to set the history/conversation title.