microsoft / microsoft/modernize-cli

Installing and using the modernize CLI leaves a persistent error in every Copilot chat session

Open
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
20
Forks
7
PR merge metrics
No merged PRs in 30d

Description

After installing the modernize CLI and running a single assessment, every subsequent GitHub Copilot
chat session in VS Code emits this error on every tool call:

bash: hooks/scripts/track-telemetry.sh: No such file or directory

The error is persistent and machine-wide. It appears in brand-new chat sessions, in unrelated
workspaces, and has nothing to do with modernization work. It continues indefinitely after the
modernize CLI has exited.

Image

Steps to reproduce

  1. Remove all modernization VS Code extensions (vscjava.migrate-java-to-azure,
    ms-dotnettools.upgrade-agent)
  2. Run modernize in a terminal
  3. Create an assessment
  4. Open a new Copilot chat in VS Code and ask it to list .md files
  5. The error appears — and recurs on every tool call from then on

Step 1 rules out the VS Code extensions entirely; the CLI alone is sufficient to reproduce.

Expected

Using the modernize CLI should not affect unrelated Copilot chat sessions.

Actual

Running an assessment installs the upgrade-agent@upgrade-agent-plugins Copilot plugin into global
state (~/.copilot/) without prompting. That plugin registers a PostToolUse hook which fails on
every tool call in every Copilot host on the machine. The plugin persists after modernize exits, and
nothing in the README indicates it will be installed.

Root cause

The failing hook itself is tracked upstream:

  • microsoft/upgrade-agent-plugins#33
  • microsoft/upgrade-agent-plugins#34

Filing here because the silent global plugin install is modernize CLI behaviour, and would remain a
concern even once those are fixed.

Workaround

rm -rf ~/.copilot/installed-plugins/upgrade-agent-plugins

Environment

macOS · modernize 1.0.74 · Copilot CLI 1.0.80

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the assessment with modernize 1.0.74, then inspect the global ~/.copilot/installed-plugins/upgrade-agent-plugins state and the linked upstream hook issues #33 and #34. No repository file or test is named in the report. Done means an assessment no longer leaves an unsolicited persistent PostToolUse hook affecting unrelated Copilot sessions.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.