microsoft / microsoft/copilot-for-eclipse

[Bug] Conversation templates and skills do not update dynamically on project lifecycle changes

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

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Description

Currently, when Eclipse starts with an empty workspace (or when projects are imported, opened, closed, or deleted during a session), conversation templates, including slash commands (/), custom prompts, and skills, do not update until Eclipse is completely restarted.

Root Cause
  1. ChatCompletionService initializes its workspace list using LSPEclipseUtils.getWorkspaceFolders(), which holds a static startup snapshot from LSP4E and does not update when projects are imported or opened at runtime.
  2. ChatCompletionService does not register an IResourceChangeListener on ResourcesPlugin.getWorkspace(), so project lifecycle events (adding, removing, opening, or closing projects) never trigger a re-fetch of templates from the language server.

(Note: There is also an upstream language server issue where conversation/templates skips global skills when workspaceFolders is empty, but the Eclipse client must also dynamically refresh its templates whenever workspace projects change).

Steps to Reproduce
  1. Start Eclipse with an empty workspace (no open projects).
  2. Open Copilot Chat and type / in the input box (observe the initial command list).
  3. Import or open a project containing prompts (.github/prompts/) or skills (.github/skills/).
  4. Type / in Copilot Chat again.

Expected behavior:
The newly imported project's prompts and skills appear in the / completion list dynamically.

Actual behavior:
The completion list remains unchanged until Eclipse is restarted.

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.

Research direction

Start in ChatCompletionService, especially its use of LSPEclipseUtils.getWorkspaceFolders(), then inspect how ResourcesPlugin exposes project lifecycle events. Reproduce with an empty workspace and import or open a project containing .github/prompts/ or .github/skills/. Done means the slash-command list refreshes without restarting Eclipse.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.