Skip to content

Status of implementing features provided in the vscode copilot, like custom instructions? #101

Description

Vscode is maintained by Microsoft, and so is this. It seems like the copilot features in vscode are getting a lot of attention, but this Eclipse plugin is barely keeping up. For instance, I realize now that the ".github/copilot-instructions.md" that we create in our enterprise is only used by vscode copilot. This Eclipse plugin doesn't use it by default. There are also additional more discrete instructions files, but again, this is only used in vscode. What is the plan for achieving parity with the vscode features?

Activity

  1. ethanyhou commented on Mar 12, 2026

    @ethanyhou
    Contributor
  2. tamasmiklossy commented on Jul 2, 2026

    @tamasmiklossy

    David M. Karr (@davidmichaelkarr): I think the .github/copilot-instructions.md already loaded into the context automatically, see the merged PR #136

    Sheng Chen (@jdneo): can you confirm that? What is not clear to me where the .github\copilot-instructions.md file should be located? Directly under the git root (<gitroot>/.github/copilot-instructions.md) or in a project that is loaded into the workspace (<gitroot>/<projectThatIsLoadedIntoTheWorkspace>/.github/copilot-instructions.md) ?

    CC: Andrey Loskutov (@iloveeclipse)

  3. jdneo commented on Jul 3, 2026

    @jdneo
    Member

    Currently both git root and IProject's root will take effect. But I strongly recommend to put it under git root, which is the common location where .github locates.

  4. tamasmiklossy commented on Jul 30, 2026

    @tamasmiklossy

    Sheng Chen (@jdneo): thanks for clarifying this. However Copilot says that it does not have access to <gitroot>/.github/copilot-instructions.md if it’s not imported into the workspace. So putting the file under <gitroot>/.github/copilot-instructions.md has no effect.

    Image Image

    Or do I misunderstand it ?

  5. jdneo commented on Jul 30, 2026

    @jdneo
    Member

    Ah yes, if you only partially import a sub module into the workspace, then the real root is invisible because it is not in workspace.

  6. tamasmiklossy commented on Jul 30, 2026

    @tamasmiklossy

    Would it be possible to make copilot aware of the <gitroot>/.github/copilot-instructions.md files independent of whether it is imported into the workspace or not?

  7. ArneDeutsch commented on Sep 29, 2026

    @ArneDeutsch

    I have implemented a discovery mechanism of custom instructions/skills/agents etc. that works similar as in VS code. For details see the PR: #466

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions