Can I remove a Pickaxe from a Studio without deleting it totally?

Migrated to new Pickaxe v2. I want to reorganise a Studio, but I can’t seem to remove Pickaxes from the Studio without deleting them completely from the account, or at least that’s what the text seems to imply.

You can remove Pickaxes from a studio, but you must move them to another Studio. Just select “duplicate to” then choose the studio you want to move it to. THen delete it.

Also, if you simply want your Pickaxe to now show up in the Studio website that is even easier. Just click on the Pickaxe, and then under Details click on the Location section. This lets you decide whether you want it to be included in your Studio website or only as a direct link.

1 Like

I see that duplicating a Pickaxe doesn’t always copy over the knowledge base. Or is that just a lag in system updating links to the underlying vector database? A Pickaxe without its curated knowledgebase feels weird.

Hey Mike, This is confusing me. Am I right in thinking that if I had a single pickaxe in V1 tied to multiple studios that in the migration to V2 they were automatically duplicated into all the studios?

If that’s the case and I have the same pick axe in three studios currently and delete one of them inside one of the three studios the other two with the same name wouldn’t be deleted?

Ideally I think you guys should consider making the pickaxes link to studios similar to the new knowledge base system. Where each bot has a panel where you can select which studios it should show up in. That way if say we are white labeling tool sets using studios we can improve the core function of a single tool and those changes would be reflected across all of the studios where we’ve included that tool.

Those are certainly good suggestions. We scoped an entire version that worked exactly like that. Ultimately this system is the cleanest that will allow the most functionality as we add more features to the products.

Re your question- Yes. If a Pickaxe was in multiple studios, it’s been duplicated in the migration so that there’s a unique version in each studio.