Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

'No copilot-instructions.md found' notice is misleading when global config exists

Closed Beginner friendly
#3,409 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
shell
Domain
cli

Research direction

Start by locating the Copilot CLI code that emits the “No copilot-instructions.md found” notice and review how it detects the global ~/.copilot/copilot-instructions.md file outside a repository. Update the notice to distinguish a missing repository-level file, then verify the behavior using the reproduction steps in the issue.

Written by the indexing model from the issue text.

Description

area:configuration
Describe the bug

When opening the Copilot CLI outside of a git repository, the notice No copilot-instructions.md found. Run /init to generate. is misleading. it implies no instructions file was found at all, even when a global ~/.copilot/copilot-instructions.md exists and is being used.

Affected version

GitHub Copilot CLI 1.0.49.

Steps to reproduce the behavior
  1. Create a global instructions file at ~/.copilot/copilot-instructions.md
  2. Open Copilot CLI from a directory that is not a git repository
  3. Observe the notice: No copilot-instructions.md found. Run /init to generate.
Expected behavior
  1. Create a global instructions file at ~/.copilot/copilot-instructions.md
  2. Open Copilot CLI from a directory that is not a git repository
  3. Observe the notice: No repository-level copilot-instructions.md found. Run /init to generate.
Additional context

No response

Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

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.

More from github/copilot-cli

All issues in github/copilot-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.