Pickaxes in a studio are related and typically use the same user information across pickaxes. Having users enter their information each time they use a different pickaxe is quite cumbersome. Either have a way for user to enter more profile information that can be use in the pickaxes, or have a way to save the user input and reuse them in another pickaxe will be tremendous.
If this is not possible in the Studio. I would like to have a way to pass user input information to the embedded app. I can query and store user information in my own application. But having the user enter the same information again in the pickaxe seems disjoint and unnecessary.
Basically, I want to build a dynamic RAG to store user information not at the time of pickaxe creation but at run time.
We are designing a system for “User Profiles” right now which is an attempt to do this. If you’re up for it, you should schedule a user feedback call with our designer. He is actively designing this feature and looking for user insight.
Is it still on the way? It would be great to have interaction between client custom instructions and from one pickaxe to an another. Or use the same chat to call several pickaxe step by step…Of course later multi agent will be greater!
I am also super interested to hear if this feature / functionality is coming soon. I am creating a studio which will have related tools, and would love for the ability to have some form of stored inputs from forms, which could then be used across multiple pickaxes. @admin_mike
I also would love to have this feature as initially requested. When I inquired about it in a support email, the feedback was that "user memory’ would not address this.
Is there any update on this request? This would be very helpful.
Any update on the user memory (I read that this is now rolling out)?
Will this cover my requirement anyway? (upload user resume once in a studio by the user and then use this resume across all PAs until updated? Currently, the user has to upload the resume over and over again for the different modules in the studio that require the resume information.
User Memory is only available in the Pro Tier currently as a beta feature. We’re gathering data on it, improving it, and will launch after we finish the studio redesign. User Memory will likely remain a Pro-only feature, though not sure.