microsoft / microsoft/Power-CAT-Copilot-Studio-Kit
Feature request: Option to turn on conversation transcripts for developer environments
@psimolin is already working on this.
Since May 25, 2026.
- Dominant language
- TypeScript
- Stars
- 450
- Forks
- 95
- Avg merge
- 26m
- Merged PRs (30d)
- 5
Description
Problem statement
When using the Copilot Studio Kit, All the agents in a tenant are available in agent inventory but only a fraction of the can have conversations analyzed and debugged because developer environments do not have conversation transcripts.
Without conversation transcripts in developer environments, makers are not able to understand how their agent works or performs prior to deploying it in sandbox or production environments. And if issues are found in sandbox and production environments then they cannot reproduce the problem in the developer environment and use Conversation Analyzer or the Agent Debugger to understand the problem more deeply.
Background: Conversation transcripts used to be available for developer environments but for the last year or so, they have not been available.
Proposed solution
Admins should be able to turn on conversation transcript storage for a developer environment
Benefits:
- Empower makers to understand what is happening with their agents before deployment to test and production
- Empower makers reproduce issues seen and taste and production environments and then use tools from the Copilot Studio kit to understand those issues more deeply
- Provide makers with analytics and developer environments so they can learn how to understand their agents
- Provide admins with more conversation transcript data so they can become more proficient Conversation analysis and agent debugging
Additional context
This might seem like a platform product request, but I am creating this issue to facilitate investigation from the Copilot Studio Kit team to see if there is some backend way to turn on conversation transcripts for developer environments. And if there is not then I can make the request direct to the product team(s).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.