最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

Has anyone been able to clone a custom copilot agent into the same dev env of the original? - Stack Overflow

programmeradmin0浏览0评论

Microsoft Learn documentation outlines how to export and import agents using what they call custom 'solutions.' You attach a copilot agent to the solution and you can push that agent to UAT or prod environments with a pipeline, all from studio. [][1] You can also download the bot file and share it with someone.

What I can't figure out is how to duplicate the bot in the same dev environment. One is a demo that shouldn't be touched, the other is our working copy.

I've tried the export/import workflow where you export the bot file and reimport as an unmanaged solution (so that it can be edited) and then publish the bot to have a copy appear in your studio UI but what happens is the import overwrites the exported solution and it becomes one and the same as your original agent. I've also tried changing the name of the demo agent prior to reimport so that they may be recognized as different solutions and the same overwriting occurred.

Anyone know a workaround?

Microsoft Learn documentation outlines how to export and import agents using what they call custom 'solutions.' You attach a copilot agent to the solution and you can push that agent to UAT or prod environments with a pipeline, all from studio. [https://learn.microsoft/en-us/microsoft-copilot-studio/authoring-solutions-import-export][1] You can also download the bot file and share it with someone.

What I can't figure out is how to duplicate the bot in the same dev environment. One is a demo that shouldn't be touched, the other is our working copy.

I've tried the export/import workflow where you export the bot file and reimport as an unmanaged solution (so that it can be edited) and then publish the bot to have a copy appear in your studio UI but what happens is the import overwrites the exported solution and it becomes one and the same as your original agent. I've also tried changing the name of the demo agent prior to reimport so that they may be recognized as different solutions and the same overwriting occurred.

Anyone know a workaround?

Share Improve this question edited Feb 19 at 12:55 desertnaut 60.5k32 gold badges155 silver badges182 bronze badges asked Feb 12 at 20:32 LoganLogan 155 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

I finally figured it out. You must first create a new agent, go through setup like normal. Add your knowledge base and logo and everything. Configure settings like generative orchestration on/off, authentication, etc. Then you need to open the solutions page and in the lefthand vertical tool bar navigate to library where you need to make a component collection. Only choose the developer-added custom topics and flows. If you include all topics in your collection, once you add it to your new (duplicate) agent, there will be two of all of the system-generated default topics. Once you have your collection, click into it and there is a large box in the top right that lets you add an existing agent. Once you select the new (duplicate) agent to the collection, navigate back to the copilot studio UI and click into the duplicate agent where you'll see all your topics populated instantly.

发布评论

评论列表(0)

  1. 暂无评论