Answer: Use stdio mode when an editor, IDE, or script spawns Copilot CLI directly as a subprocess; it is the default and recommended setup for IDE integration. Use TCP mode when a client needs to reach the server over a socket instead of a pipe, such as from a separate process or container, or when connecting to a longer-lived server on a known port. Status: Confirmed Entry: tool/github-copilot/integrations/stdio-vs-tcp-mode Revision: 2 Digest: sha256:9cc1eb8705a4d4ee (changes whenever the content changes) Timeline: Created: 2026-11-13T03:31:41Z Last changed: 2026-11-17T13:32:29Z (default TCP bind address: — → 127.0.0.1) Last verified: 2026-11-20T13:13:07Z Next check: 2026-11-21T13:13:07Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of stdio mode recommendation | Use stdio mode when an editor, IDE, or script spawns Copilot CLI directly as a subprocess. | [1] | 2026-11-20 stdio default status | This is the default and the recommended setup for IDE integration | [1] | 2026-11-20 TCP mode recommendation | Use TCP mode when a client needs to reach the server over a socket instead of a pipe | [1] | 2026-11-20 default TCP bind address | 127.0.0.1 | [1] | 2026-11-20 Sources: [1] GitHub. "Copilot CLI ACP server - GitHub Docs". https://docs.github.com/en/copilot/reference/copilot-cli-reference/acp-server Role: primary. Accessed: 2026-11-20T13:13:07Z Quote: "Use stdio mode when an editor, IDE, or script spawns Copilot CLI directly as a subprocess." (Supports: stdio mode recommendation) Quote: "This is the default and the recommended setup for IDE integration" (Supports: stdio default status) Quote: "Use TCP mode when a client needs to reach the server over a socket instead of a pipe" (Supports: TCP mode recommendation) Quote: "By default it binds to the loopback address 127.0.0.1 ." (Supports: default TCP bind address) Snapshot SHA-256: 1fc71b7fe37bccd4f250adc28d773068cfca909441dcca0b2c6a70ba9a6c2bc7 (captured 2026-11-18T13:09:06Z) 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:09:06Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:13:07Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:13:07Z Last attempt: 2026-11-20T13:13:07Z Notes and limitations: Extracted automatically from a single official source (section "Choosing between stdio and TCP"). Related: https://latestn.com/tool/github-copilot/integrations/supported-connector-services Which services are supported as GitHub Copilot connectors? https://latestn.com/tool/github-copilot/integrations/supported-integrations Which integrations does GitHub Copilot support? https://latestn.com/tool/github-copilot/integrations/third-party-coding-agents Which third-party coding agents can I use with GitHub Copilot? https://latestn.com/tool/github-copilot/integrations/set-up-mcp-servers How do I set up MCP servers to use with GitHub Copilot agent mode? https://latestn.com/tool/github-copilot/integrations/share-knowledge-with-spaces How can I share knowledge with teammates using GitHub Copilot Spaces? https://latestn.com/tool/github-copilot/integrations/start-acp-server How do I start the GitHub Copilot CLI ACP server? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:32:29Z | changed | default TCP bind address: — → 127.0.0.1 | [1] 2026-11-17T13:32:29Z | changed | mutual exclusivity: passing both --stdio and --port is rejected → — | [1] 2026-11-17T13:32:29Z | changed | TCP default bind address: 127.0.0.1 → — | [1] 2026-11-13T03:31:41Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/integrations/stdio-vs-tcp-mode/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/integrations/stdio-vs-tcp-mode POST: https://latestn.com/dispute/tool/github-copilot/integrations/stdio-vs-tcp-mode with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/integrations/stdio-vs-tcp-mode?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Should I use stdio mode or TCP mode for the GitHub Copilot CLI ACP server? Revision 2, last verified 2026-11-20T13:13:07Z. https://latestn.com/tool/github-copilot/integrations/stdio-vs-tcp-mode (accessed 2026-11-21T09:53:35Z). @misc{LatestN_tool_github_copilot_integrations_stdio_vs_tcp_mode_r2, title = {Should I use stdio mode or TCP mode for the GitHub Copilot CLI ACP server?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/integrations/stdio-vs-tcp-mode}}, note = {Revision 2; digest sha256:9cc1eb8705a4d4ee; last verified 2026-11-20T13:13:07Z; accessed 2026-11-21T09:53:35Z} } 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/integrations/stdio-vs-tcp-mode