Describe the feature or problem you'd like to solve
Copilot CLI already uses .agents/skills; please extend the same .agents convention to instructions, agents, and hooks in any opened folder, not just Git repos.
Proposed solution
This would let users standardize Copilot customizations under one root, .agents/, for any opened workspace/folder, whether or not it is a Git repository, instead of splitting them across .github/, .claude/, and ~/.copilot/.
This request is specifically about the .agents/ directory tree, not the root AGENTS.md file.
Requested default discovery additions:
- /.agents/instructions/**/*.instructions.md
- /.agents/agents/*.agent.md or the equivalent agent-file convention already used by the product
- /.agents/hooks/**/*.json (or the equivalent hook-file convention already used by the product)
- ~/.agents/instructions/**/*.instructions.md
- ~/.agents/agents/*.agent.md or the equivalent agent-file convention already used by the product
- ~/.agents/hooks/**/*.json (or the equivalent hook-file convention already used by the product)
Note: COPILOT_CUSTOM_INSTRUCTIONS_DIRS already allows additional instruction directories today; this request is to make .agents/instructions a zero-config default. If user-level custom agents or hooks are not already supported, those would be new capability, but the request is still to make .agents the canonical root.
Behavioral expectations:
- Works for any opened folder/workspace, including folders that are not Git repositories
- Works consistently with COPILOT_HOME
- Discovery is documented and deterministic
- No silent partial loading for a path family
- /help and docs reflect the exact supported .agents locations
Example prompts or workflows
- "Load the repo's coding rules from .agents/instructions automatically."
- "Use the release-notes agent from .agents/agents."
- "Run the startup hook from .agents/hooks when I open a plain folder like D:\work\MyProjectOutsideGit."
- "Keep my user-level instruction files under ~/.agents/ instead of splitting them across .copilot/ and .github/."
Additional context
Related but distinct: #2504 (cwd vs. git-root discovery within Git repos) and #1506 (configurable agents folder support). This request is about zero-config .agents defaults for any opened folder, Git or not.
This is additive parity, not a migration away from .copilot or .github.
If it is easier to triage, this could be split into separate issues for instructions / agents / hooks.
Describe the feature or problem you'd like to solve
Copilot CLI already uses .agents/skills; please extend the same .agents convention to instructions, agents, and hooks in any opened folder, not just Git repos.
Proposed solution
This would let users standardize Copilot customizations under one root, .agents/, for any opened workspace/folder, whether or not it is a Git repository, instead of splitting them across .github/, .claude/, and ~/.copilot/.
This request is specifically about the .agents/ directory tree, not the root AGENTS.md file.
Requested default discovery additions:
Note: COPILOT_CUSTOM_INSTRUCTIONS_DIRS already allows additional instruction directories today; this request is to make .agents/instructions a zero-config default. If user-level custom agents or hooks are not already supported, those would be new capability, but the request is still to make .agents the canonical root.
Behavioral expectations:
Example prompts or workflows
Additional context
Related but distinct: #2504 (cwd vs. git-root discovery within Git repos) and #1506 (configurable agents folder support). This request is about zero-config .agents defaults for any opened folder, Git or not.
This is additive parity, not a migration away from .copilot or .github.
If it is easier to triage, this could be split into separate issues for instructions / agents / hooks.