Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`skillDirectories` setting from `settings.json` is not honored in ACP mode (`copilot --acp`)

Aberta
  • Algo errado?
#4,700 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
72/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
shell
Domínio
cli

Direção de pesquisa

Comece pelo ponto de entrada copilot --acp e compare sua descoberta de skills com o copilot interativo, usando a configuração skillDirectories em ~/.copilot/settings.json como entrada. Reproduza com initialize, session/new e session/prompt; considera-se concluído quando o ACP expõe as skills personalizadas configuradas junto com as skills do projeto, pessoais e integradas.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:configuration area:non-interactive
Describe the bug

~/.copilot/settings.json supports a skillDirectories array for registering
additional custom skill source directories. These directories' skills are
correctly discovered and listed when running the interactive copilot CLI,
but do not show up when the same user/config runs in ACP mode
(copilot --acp, e.g. via the Zed editor's ACP integration).

Affected version

Copilot CLI 1.0.82

Environment
  • OS: Windows
  • ACP client: Zed editor (copilot --acp)
  • Windows Terminal: copilot.exe --acp
Steps to reproduce

  1. Add a skillDirectories entry to ~/.copilot/settings.json, e.g.:

    {
  "skillDirectories": [
    "C:\\Users\\<user>\\ai_space\\skill_groups\\workflow_skills",
    "C:\\Users\\<user>\\ai_space\\skill_groups\\shorthand_skills",
    "C:\\Users\\<user>\\ai_space\\skill_groups\\ddstack_skills"
  ]
}

Each directory contains one or more <skill-name>/SKILL.md skills.

  1. Run interactive copilot, then copilot skill list (or /skills list).
    Result: skills from all skillDirectories entries appear under a
    "Custom skills:" heading, alongside project (.github/skills/) and
    personal (~/.copilot/skills/) skills. Confirmed working — e.g.
    workflow-design, shorthand-crew, principle-fix-root-causes, etc. all
    listed (43 custom skills total in our test).

  2. Independently, spawn copilot.exe --acp as a subprocess and drive it
    directly over stdio with raw JSON-RPC (bypassing any client like Zed
    entirely, to rule out client-side filtering):

    • initialize → session/new (with the same cwd) → session/prompt
      asking the agent to "list every skill name available to you right now,
      grouped by category, without invoking any tool."

    Result: the agent's response only lists project (12 skills),
    user/personal (5 skills), and builtin (2 skills) categories. The
    custom category empty, none of the 43 skills sourced from skillDirectories, does
    not appear in its own self-reported system context.

Expected behavior

ACP mode should discover and expose the same skill set as interactive mode,
including all directories configured via skillDirectories in
settings.json, since both entry points read the same global config file.

Actual behavior

ACP mode does not surface any skillDirectories-sourced skills, with no
error, warning, or other indication that the setting was skipped.

Additional context
  • settings.json and config.json are unmodified between the two runs —
    same file, same user, same machine.
  • Personal (~/.copilot/skills/) and project (.github/skills/) skills
    do load correctly in ACP mode, so this isn't a total skill-loading
    failure — it's specific to the skillDirectories custom-path mechanism.
  • Reproduced twice: once via a live Zed → copilot --acp session, and once
    via a standalone hand-rolled ACP client script, ruling out a
    client-specific (Zed) cause.
Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
17h 6min
PRs com merge (30d)
5

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/copilot-cli

Todas as issues de github/copilot-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.