Answer: Once a session is created, you can list the active plugins to confirm a directory was picked up correctly by calling the plugins list RPC and iterating over the results. Plugins loaded via --plugin-dir appear in this list with their cache path set to the directory you provided. Status: Confirmed Entry: tool/github-copilot/troubleshooting/inspect-loaded-plugins Revision: 2 Digest: sha256:cc70097853384ba8 (changes whenever the content changes) Timeline: Created: 2026-11-16T12:52:26Z Last changed: 2026-11-18T13:03:37Z (Plugin dir behavior: — → --plugin-dir) Last verified: 2026-11-20T13:08:31Z Next check: 2026-11-21T13:08:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Method | await session. rpc . plugins . list () | [1] | 2026-11-20 Iteration | for ( const plugin of plugins. plugins ) | [1] | 2026-11-20 Logging | console . log ( ` ${plugin.name} ( ${plugin.enabled ? "enabled" : "disabled" } )` ); | [1] | 2026-11-20 Plugin dir behavior | --plugin-dir | [1] | 2026-11-20 Marketplace tagging | Marketplace installs are tagged with their registry source. | [1] | 2026-11-20 Sources: [1] GitHub. "Plugin directories - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/features/plugin-directories Role: primary. Accessed: 2026-11-20T13:08:31Z Quote: "const plugins = await session. rpc . plugins . list ();" (Supports: Method) Quote: "for ( const plugin of plugins. plugins ) {" (Supports: Iteration) Quote: "console . log ( ` ${plugin.name} ( ${plugin.enabled ? "enabled" : "disabled" } )` );" (Supports: Logging) Quote: "Plugins loaded via --plugin-dir appear in this list with their cache path set to the directory you provided." (Supports: Plugin dir behavior) Quote: "Marketplace installs are tagged with their registry source." (Supports: Marketplace tagging) Snapshot SHA-256: 0a0a80614c6cac5411c22977a9fdb81fe25025f17ba051258f8d35cd62c9e977 (captured 2026-11-18T13:03:35Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:03:37Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:08:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:08:31Z Last attempt: 2026-11-20T13:08:31Z Notes and limitations: Extracted automatically from a single official source (section "Inspecting which plugins loaded"). Related: https://latestn.com/tool/github-copilot/troubleshooting/invalid-json-example-response What does a GitHub Copilot response look like when fixing invalid JSON? https://latestn.com/tool/github-copilot/troubleshooting/local-cli-limitations What are the limitations of the GitHub Copilot SDK local CLI setup? https://latestn.com/tool/github-copilot/troubleshooting/mcp-server-agent-mode-problems How do I resolve Copilot agent mode problems when using the GitHub MCP server? https://latestn.com/tool/github-copilot/troubleshooting/handle-api-rate-limits-2 How do I handle API rate limits when using GitHub Copilot? https://latestn.com/tool/github-copilot/troubleshooting/health-checks-session-cleanup How do I set up health checks and session cleanup for GitHub Copilot SDK backend services? https://latestn.com/tool/github-copilot/troubleshooting/in-process-runtime-limitations What are the limitations of running the GitHub Copilot runtime in process? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:03:37Z | changed | Plugin dir behavior: — → --plugin-dir | [1] 2026-11-18T13:03:37Z | changed | Plugin dir cache path: Plugins loaded via --plugin-dir appear in this list with their cache path set to the directory you provided. → — | [1] 2026-11-16T12:52:26Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/troubleshooting/inspect-loaded-plugins/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/troubleshooting/inspect-loaded-plugins POST: https://latestn.com/dispute/tool/github-copilot/troubleshooting/inspect-loaded-plugins with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/troubleshooting/inspect-loaded-plugins?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How can I inspect which GitHub Copilot plugins loaded? Revision 2, last verified 2026-11-20T13:08:31Z. https://latestn.com/tool/github-copilot/troubleshooting/inspect-loaded-plugins (accessed 2026-11-21T09:53:10Z). @misc{LatestN_tool_github_copilot_troubleshooting_inspect_loaded_plugins_r2, title = {How can I inspect which GitHub Copilot plugins loaded?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/troubleshooting/inspect-loaded-plugins}}, note = {Revision 2; digest sha256:cc70097853384ba8; last verified 2026-11-20T13:08:31Z; accessed 2026-11-21T09:53:10Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/troubleshooting/inspect-loaded-plugins