Log inputs and outputs of shell activities
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### 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
1. "I want to replay just the shell commands Copilot ran"
2. "Copilot used the wrong file/path... When did that happen?"
3. "Why is my file broken after I had copilot refactor it?{
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.