Skip to content

Log inputs and outputs of shell activities #2984

Description

@mcodilla

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:sessionsSession management, resume, history, session picker, and session statearea:toolsBuilt-in tools: file editing, shell, search, LSP, git, and tool call behavior

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions