Describe the feature or problem you'd like to solve
I see that copilot cli already logs tool execution events witin the session state folder, but the input and output contents are not populated
Proposed solution
I believe it will benefit copilot cli and its users to trace what happened. When copilot makes parallel calls the complexity increases exponentially and without structured logging, it makes it difficult to verify corrected or diagnose when or where failures occur
Example prompts or workflows
- "I want to replay just the shell commands Copilot ran"
- "Copilot used the wrong file/path... When did that happen?"
- "Why is my file broken after I had copilot refactor it?{
Additional context
No response
Describe the feature or problem you'd like to solve
I see that copilot cli already logs tool execution events witin the session state folder, but the input and output contents are not populated
Proposed solution
I believe it will benefit copilot cli and its users to trace what happened. When copilot makes parallel calls the complexity increases exponentially and without structured logging, it makes it difficult to verify corrected or diagnose when or where failures occur
Example prompts or workflows
Additional context
No response