Clarify SDK architecture and in-process runtime transport #2804

Activity

1. github-actions commented on Oct 1, 2026

   

   github-actionsbot

   on Oct 1, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the report. I've labeled this as documentation.

   Gap: The root README.md architecture section says SDKs talk to the Copilot CLI server over JSON-RPC. That's only the default out-of-process transport. It doesn't mention the experimental in-process transport (native C ABI/FFI, no CLI child process), and it blurs the agent runtime with the CLI interface.

   Affected docs:

   • README.md (architecture section and diagram)
   • docs/setup/in-process-runtime.md (the detailed page to link to)
   • Possibly the per-language READMEs where they repeat the "SDK → CLI server" description.

   Suggested improvements:

   • Distinguish the Copilot agent runtime from the Copilot CLI interface.
   • Describe the default out-of-process JSON-RPC path.
   • Add a short note on the experimental in-process path (loads the Rust runtime through the C ABI, no child process).
   • Link to docs/setup/in-process-runtime.md for details.

   Open PR #2805 appears to address this.

   Generated by Documentation Handler for #2804 · copilot · auto · 13.9 AIC · ⌖ 5.31 AIC · ⊞ 6.8K · ◷
2. github-actions

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Oct 1, 2026