-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Log inputs and outputs of shell activities #2984
Copy link
Copy link
Open
Labels
area:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session statearea:toolsBuilt-in tools: file editing, shell, search, LSP, git, and tool call behaviorBuilt-in tools: file editing, shell, search, LSP, git, and tool call behavior
Metadata
Metadata
Assignees
Labels
area:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session statearea:toolsBuilt-in tools: file editing, shell, search, LSP, git, and tool call behaviorBuilt-in tools: file editing, shell, search, LSP, git, and tool call behavior
Type
Fields
Give feedbackNo fields configured for Feature.
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