Answer: GitHub Copilot surfaces work together because some context, permissions, and configuration carry between surfaces, and a single piece of work can move between surfaces. The surfaces also share the same foundation, being powered by the same SDK and platform primitives. Status: Confirmed Entry: tool/github-copilot/features/surfaces-work-together Revision: 3 Digest: sha256:9a417960b0f73e11 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:22:08Z Last changed: 2026-11-18T12:52:51Z (Organization policies: — → administrator policies apply across most surfaces developers use) Last verified: 2026-11-20T12:59:00Z Next check: 2026-11-21T12:59:00Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Shared configuration | your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot | [1] | 2026-11-20 Work movement | A single piece of work can move between surfaces. | [1] | 2026-11-20 Shared foundation | powered by the same SDK and platform primitives | [1] | 2026-11-20 Organization policies | administrator policies apply across most surfaces developers use | [1] | 2026-11-20 Sources: [1] GitHub. "Where to use GitHub Copilot - GitHub Docs". https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot Role: primary. Accessed: 2026-11-20T12:59:00Z Quote: "your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot" (Supports: Shared configuration) Quote: "A single piece of work can move between surfaces." (Supports: Work movement) Quote: "The Copilot experiences you use across surfaces are all powered by the same SDK and platform primitives." (Supports: Shared foundation) Quote: "administrator policies apply across most surfaces developers use" (Supports: Organization policies) Snapshot SHA-256: e013e8dd79583a03267119fb28c605a13379c033915da8e793efac1b5359e8cb (captured 2026-11-18T12:52:51Z) 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-18T12:52:51Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:59:00Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:59:00Z Last attempt: 2026-11-20T12:59:00Z Notes and limitations: Extracted automatically from a single official source (section "How the surfaces work together"). Related: https://latestn.com/tool/github-copilot/features/synthesize-research How can GitHub Copilot help synthesize research? https://latestn.com/tool/github-copilot/features/synthesize-research-prompt How do I use GitHub Copilot to synthesize research? https://latestn.com/tool/github-copilot/features/template-example-prompt What does an example GitHub Copilot template prompt and response look like? https://latestn.com/tool/github-copilot/features/summarize-pull-request How do I get a summary of a pull request with GitHub Copilot? https://latestn.com/tool/github-copilot/features/supported-hook-events Which hook events does GitHub Copilot support, such as sessionStart, preToolUse, and agentStop? https://latestn.com/tool/github-copilot/features/supported-image-formats Which image file formats does GitHub Copilot image input support? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:52:51Z | changed | Organization policies: — → administrator policies apply across most surfaces developers use | [1] 2026-11-18T12:52:51Z | changed | Shared foundation: — → powered by the same SDK and platform primitives | [1] 2026-11-18T12:52:51Z | changed | Work movement: — → A single piece of work can move between surfaces. | [1] 2026-11-18T12:52:51Z | changed | Shared configuration: — → your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot | [1] 2026-11-18T12:52:51Z | changed | cross-surface settings: your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot → — | [1] 2026-11-18T12:52:51Z | changed | shared foundation: the same SDK and platform primitives → — | [1] 2026-11-18T12:52:51Z | changed | work movement: A single piece of work can move between surfaces. → — | [1] 2026-11-18T12:52:51Z | changed | shared configuration: Some context, permissions, and configuration can carry between surfaces. → — | [1] 2026-11-16T12:42:18Z | changed | cross-surface settings: — → your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot | [1] 2026-11-16T12:42:18Z | changed | shared foundation: — → the same SDK and platform primitives | [1] 2026-11-16T12:42:18Z | changed | work movement: — → A single piece of work can move between surfaces. | [1] 2026-11-16T12:42:18Z | changed | shared configuration: — → Some context, permissions, and configuration can carry between surfaces. | [1] 2026-11-16T12:42:18Z | changed | Administrator policies: administrator policies apply across most surfaces developers use → — | [1] 2026-11-16T12:42:18Z | changed | Cross-surface settings: your plan, custom instructions, agent skills, and connected MCP servers apply across the places where you use Copilot → — | [1] 2026-11-16T12:42:18Z | changed | Shared foundation: the same SDK and platform primitives → — | [1] 2026-11-16T12:42:18Z | changed | Work movement: A single piece of work can move between surfaces. → — | [1] 2026-11-16T12:42:18Z | changed | Shared configuration: Some context, permissions, and configuration can carry between surfaces. → — | [1] 2026-11-13T03:22:08Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/features/surfaces-work-together/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/features/surfaces-work-together POST: https://latestn.com/dispute/tool/github-copilot/features/surfaces-work-together with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/features/surfaces-work-together?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do GitHub Copilot surfaces work together? Revision 3, last verified 2026-11-20T12:59:00Z. https://latestn.com/tool/github-copilot/features/surfaces-work-together (accessed 2026-11-21T09:52:33Z). @misc{LatestN_tool_github_copilot_features_surfaces_work_together_r3, title = {How do GitHub Copilot surfaces work together?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/features/surfaces-work-together}}, note = {Revision 3; digest sha256:9a417960b0f73e11; last verified 2026-11-20T12:59:00Z; accessed 2026-11-21T09:52:33Z} } 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/features/surfaces-work-together