microsoft / microsoft/copilot-for-eclipse

[Feat] Enable access to the Problems view

Open
#187 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Currently Copilot does not have access to the Problems view. See conversation between my and copilot

{
  "conversationId": "93893c7b-bbe7-4883-bd20-f6927884647a",
  "title": "Checking for Errors in Eclipse",
  "requesterUsername": "tamasmiklossy",
  "responderUsername": "GitHub Copilot",
  "turns": [
    {
      "message": {
        "text": "Do you have access to the Problems view?"
      },
      "references": [],
      "ignoredSkills": [],
      "userLanguage": "en",
      "source": "panel",
      "model": "Claude Sonnet 4.6",
      "chatMode": "Agent",
      "customChatModeId": "Agent",
      "needToolCallConfirmation": true,
      "turnId": "122bac16-1a90-4da8-91b8-aee332d5d013",
      "role": "user",
      "timestamp": "2026-05-13T10:49:46.104340Z"
    },
    {
      "reply": {
        "annotations": [],
        "references": [],
        "hideText": false,
        "notifications": [],
        "followups": [],
        "errorMessages": [],
        "editAgentRounds": [
          {
            "roundId": 1,
            "reply": "No, I don\u0027t have direct access to the Eclipse Problems view. However, I can use the `get_errors` tool to check for compile/lint errors in specific files. Would you like me to check a particular file for errors?",
            "toolCalls": []
          }
        ],
        "panelMessages": [],
        "steps": [],
        "agentMessages": [],
        "data": {},
        "modelName": "Claude Sonnet 4.6",
        "billingMultiplier": 1.0
      },
      "suggestedTitle": "Checking for Errors in Eclipse",
      "turnId": "7c421a13-1ace-495a-b01b-44732a7856e5",
      "role": "copilot",
      "timestamp": "2026-05-13T10:49:46.298088800Z"
    }
  ],
  "creationDate": "2026-05-13T10:49:46.071703600Z",
  "lastMessageDate": "2026-05-13T10:49:50.284442600Z"
}

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 by examining how the existing get_errors tool is exposed to Copilot and how Eclipse's Problems view reports diagnostics. Define the integration needed for Copilot to access the Problems view, then verify it with an agent conversation like the attached example.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.