clarify how to integrate 3rd party tools/editors with github copilot

[elasticdotventures]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

This page is incomplete/unclear

https://github.com/github/docs/blob/main/content/copilot/concepts/build-copilot-extensions/agents-for-copilot-extensions.md

There is a list of editors - how can I get another editor added as a tool that can integrate with github copilot in a method similar to IntelliJ.

What part(s) of the article would you like to see updated?

Is it possible to add additional editors & plugins that interface or delegate directly with copilot capabilities?
An example of this would be Aider -
https://aider.chat/docs/llms/github.html

Currently Aider can only integrate by lifting the credentials from an IntelliJ editor.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[elasticdotventures]

To be clear I'm asking about other editors such as Godot

RooCode
RooCodeInc/Roo-Code#5970

[elasticdotventures]

I found the code for https://github.com/github/CopilotForXcode and used an AI to digest the code and prepare this summary.
it seems the Github Copilot LSP implements a signin JSON RPC request.

│ Processed Files: │
│ - │
│ Core/Sources/GitHubCopilotViewModel/GitHubCopilotView │ │ Model.swift │
│ - │
│ Tool/Sources/GitHubCopilotService/LanguageServer/GitH │ │ ubCopilotRequest.swift │
│ - │
│ Tool/Sources/GitHubCopilotService/LanguageServer/GitH │ │ ubCopilotService.swift │
│ - Tool/Sources/Status/Status.swift │
╰──────────────────────────────────────────────────────────────────────╯
✦ - Initiation: User clicks "Sign In". GitHubCopilotViewModel.signIn()
is called.

• Device Flow: signIn() calls preSignIn(), which in turn calls
  GitHubCopilotService.signInInitiate(). This sends a SignInInitiate
  request to the Copilot language server.
• User-Side Auth: The server returns a userCode and verificationURL.
  The user opens the URL and enters the code to authorize the app on
  GitHub.
• Confirmation: The app calls
  GitHubCopilotService.signInConfirm(userCode:), sending a
  SignInConfirm request. A successful response contains the username
  and auth token.
• State Management: Status.shared.updateAuthStatus() is called to
  globally reflect the logged-in state. The token is stored for
  subsequent requests.
• Chat Access: Authenticated requests to the chat endpoint
  (CreateConversation, CreateTurn) are made through
  GitHubCopilotService. The service sends these requests to the
  language server, which proxies them to the GitHub Copilot API,
  adding the necessary authentication token to the headers.

[Sharra-writes]

@elasticdotventures Hi, thanks for opening an issue! This isn't really a question the docs team can answer and would be better handled by our support team. If you get an answer you think should be added to the docs, though, feel free to come back and open an issue to discuss it. 💛

[benaz14]

Moet ik u een bon geven Op zo 20 jul 2025 om 03:16 schreef Brian Horakh ***@***.***>

…

*elasticdotventures* left a comment (github/docs#39398) <#39398 (comment)> I found the code for https://github.com/github/CopilotForXcode and used an AI to digest the code and prepare this summary. it seems the Github Copilot LSP implements a signin JSON RPC request. │ *Processed Files:* │ │ - │ │ Core/Sources/GitHubCopilotViewModel/GitHubCopilotView │ │ Model.swift │ │ - │ │ Tool/Sources/GitHubCopilotService/LanguageServer/GitH │ │ ubCopilotRequest.swift │ │ - │ │ Tool/Sources/GitHubCopilotService/LanguageServer/GitH │ │ ubCopilotService.swift │ │ - Tool/Sources/Status/Status.swift │ ╰──────────────────────────────────────────────────────────────────────╯ ✦ - Initiation: User clicks "Sign In". GitHubCopilotViewModel.signIn() is called. - Device Flow: signIn() calls preSignIn(), which in turn calls GitHubCopilotService.signInInitiate(). This sends a SignInInitiate request to the Copilot language server. - User-Side Auth: The server returns a userCode and verificationURL. The user opens the URL and enters the code to authorize the app on GitHub. - Confirmation: The app calls GitHubCopilotService.signInConfirm(userCode:), sending a SignInConfirm request. A successful response contains the username and auth token. - State Management: Status.shared.updateAuthStatus() is called to globally reflect the logged-in state. The token is stored for subsequent requests. - Chat Access: Authenticated requests to the chat endpoint (CreateConversation, CreateTurn) are made through GitHubCopilotService. The service sends these requests to the language server, which proxies them to the GitHub Copilot API, adding the necessary authentication token to the headers. — Reply to this email directly, view it on GitHub <#39398 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3AP7KBNDJKAB7DUBTBEPXT3JLUXNAVCNFSM6AAAAACB4U5K36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJSGY3TINRWGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>