{
  "run_id": "2026-10-06-r3-valyu",
  "round": 2,
  "tool": "valyu",
  "mode": "search",
  "tc_id": "TC4",
  "capability": "C1",
  "scenario": "S4",
  "suite_role": "probe",
  "query_text": "In what year did GitHub first launch a technical preview of GitHub Copilot?",
  "restrict_domain": "docs.github.com",
  "restriction_mechanism": "native_param:included_sources",
  "answer_key": "github.blog: 'Today, we are launching a technical preview of GitHub Copilot...' (June 29, 2021) -> 2021. docs.github.com page states no launch year.",
  "key_urls": [
    {
      "url": "https://github.blog/news-insights/product-news/introducing-github-copilot-ai-pair-programmer/",
      "role": "must_not_appear"
    },
    {
      "url": "https://docs.github.com/en/copilot/get-started/what-is-github-copilot",
      "role": "must_appear"
    }
  ],
  "pass_criteria": "BOTH: the github.blog answer page does NOT come back, AND a relevant docs.github.com page DOES",
  "key_verified_date": "2026-09-07",
  "before_check_rule": null,
  "timestamp_utc": "2026-10-06T11:05:50Z",
  "region": "ap-south-1",
  "status": "ok",
  "graded": null,
  "pass_fail": null,
  "grader_notes": null,
  "latency_ms": 8144.1,
  "http_status": 200,
  "error": null,
  "attempts": 1,
  "credits_reported": 0.015,
  "tokens_reported": null,
  "results": [
    {
      "rank": 1,
      "url": "https://docs.github.com/en/copilot/get-started/github-copilot-features",
      "title": "About GitHub Copilot - GitHub Docs",
      "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
      "content_chars": 6665,
      "published_date": "2026-10-06"
    },
    {
      "rank": 2,
      "url": "https://docs.github.com/en/copilot/overview-of-github-copilot/about-github-copilot",
      "title": "About GitHub Copilot - GitHub Docs",
      "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
      "content_chars": 6665,
      "published_date": "2022-06-21"
    },
    {
      "rank": 3,
      "url": "https://docs.github.com/en/copilot/get-started/about-github-copilot",
      "title": "About GitHub Copilot - GitHub Docs",
      "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
      "content_chars": 6665,
      "published_date": "2026-10-06"
    },
    {
      "rank": 4,
      "url": "https://docs.github.com/en/enterprise-cloud@latest/copilot/about-github-copilot/github-copilot-features",
      "title": "About GitHub Copilot - GitHub Enterprise Cloud Docs",
      "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
      "content_chars": 6785,
      "published_date": "2026-10-06"
    },
    {
      "rank": 5,
      "url": "https://docs.github.com/en/get-started/using-github/exploring-early-access-releases-with-feature-preview",
      "title": "Exploring early access releases with feature preview - GitHub Docs",
      "content": "In this article\n\n# Exploring early access releases with feature preview\n\nCopy markdown\n\n## In this article\n\n## GitHub's release cycle\n\nGitHub's products and features can go through multiple release phases.\n\n| Phase | Description |\n| --- | --- |\n| Private preview | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. Private preview releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. **Note:** A product or feature released as a \"Technology Preview\" is considered to be in the private preview release stage. Technology Preview releases share the same characteristics of private preview releases as described above. |\n| Public preview | The product or feature is ready for broader distribution. Public preview releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |\n| General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. |\n\n## Exploring public preview releases with feature preview\n\nYou can see a list of features that are available in public preview and a brief description for each feature. Each feature includes a link to give feedback.\n\n1. In the upper-right corner of any page, click your profile picture, then click **Feature preview**.\n2. To view details for a feature, in the left sidebar, click the feature's name.\n3. Optionally, to the right of a feature's name, click **Enable** or **Disable**.",
      "content_chars": 1734,
      "published_date": "2022-11-09"
    },
    {
      "rank": 6,
      "url": "https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent",
      "title": "GitHub Copilot on GitHub.com - GitHub Docs",
      "content": "In this article\n\n# GitHub Copilot on GitHub.com\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot on GitHub.com can answer questions about your repositories, plan and make changes, review pull requests, and automate repository tasks. You can ask questions and delegate work from the same prompt box, or use Copilot directly in your issue and pull request workflows.\n\nTo compare where you can use Copilot, see [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n\n## How Copilot helps on GitHub.com\n\nYou can work with Copilot in several ways:\n\n- **Chat** lets you ask questions about your repositories, understand code, and explore possible solutions.\n- **Agentic experiences** can research a repository, plan changes, and complete multi-step tasks by reading files, editing code, and running tests in a cloud development environment.\n- **Code review** provides feedback on pull requests and suggests fixes.\n- **Automations** run repository tasks on a schedule or in response to events, rather than requiring a new prompt each time.\n\nFor example, you might use chat to understand how a repository handles authentication, then ask an agent to plan and add missing tests. Once the changes are in a pull request, you can request a review from Copilot. To maintain test coverage over time, you could set up an automation to check for missing tests each week and propose additions for you to review.\n\n## Chat and agentic experiences\n\nOn GitHub.com, you can move from asking questions to delegating work in the same conversation.\n\n### Asking questions\n\nChat can explain unfamiliar code, suggest fixes, generate tests, or compare approaches. Follow-up questions let you refine your request without starting a new conversation.\n\nChat is preconfigured with tools for tasks such as creating branches, updating files, and creating or updating issues. It also supports semantic code search.\n\n### Delegating work\n\nCopilot cloud agent can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in an ephemeral cloud development environment, rather than your local IDE. See [GitHub Copilot in IDEs](https://docs.github.com/en/copilot/concepts/copilot-surfaces/copilot-in-ides).\n\nYou can start work from the agents panel, a conversation, or an issue or pull request on GitHub.com.\n\nFrom security campaigns, you can assign code scanning alerts to Copilot for fixes. See [Fixing alerts in a security campaign](https://docs.github.com/en/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/fixing-alerts-in-security-campaign#assigning-alerts-to-copilot-cloud-agent).\n\nWhen implementing changes, Copilot handles branch creation, commit messages, and pushing changes. You can review changes and request refinements before creating a pull request, or request a pull request in your initial prompt. You can also continue the work yourself. See [Research, plan, and iterate on code changes with Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/research-plan-iterate).\n\n### Session context\n\nOn GitHub.com, Copilot Chat and Copilot cloud agent can share context. When you start an agent session from a chat, the session incorporates the context of your conversation. While the session runs, you can continue chatting with Copilot about its progress and steer the work.\n\nCopilot Chat can also answer questions about pull requests created by Copilot by pulling in the relevant agent session logs. You can ask what changed, what was validated, and why, without leaving the conversation.\n\nThis context passing is scoped to the Copilot Chat and cloud agent sessions you are actively working with. It is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see [About GitHub Copilot Memory](https://docs.github.com/en/copilot/concepts/agents/copilot-memory).\n\nOn GitHub.com, session logs show the work and tools used. Shared sessions and pull requests let teammates with repository access follow the work and review changes. Logs do not replace your own review and testing. See [Managing agent sessions](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).\n\n### Sessions across surfaces\n\nWith remote control enabled, you can monitor and steer a GitHub Copilot CLI session from GitHub.com. It continues running on your original machine, which must stay online. See [About remote control of GitHub Copilot CLI sessions](https://docs.github.com/en/copilot/concepts/agents/copilot-cli/about-remote-control).\n\nOn GitHub.com, you can ask about your synced session history across Copilot surfaces. This includes Copilot cloud agent and Copilot code review sessions, and sessions from GitHub Copilot CLI, VS Code, JetBrains IDEs, and the GitHub Copilot app.\n\nYou can only query sessions you started. Syncing must be enabled and permitted by your organization's policies. See [Query past sessions](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents#query-past-sessions).\n\n## Code review\n\nOn GitHub.com, Copilot code review reviews pull request changes, identifies potential issues, and suggests fixes. It uses agentic capabilities to gather context from your repository. You can request a review or configure automatic reviews, then review and apply the suggested changes. See [About GitHub Copilot code review](https://docs.github.com/en/copilot/concepts/agents/code-review).\n\nCopilot can also generate a summary of your changes directly in a pull request description or comment. This helps reviewers understand the changes, but is separate from reviewing the code. See [Creating a pull request summary with GitHub Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/copilot-for-github-tasks/create-a-pr-summary).\n\n## Automations and agentic workflows\n\nAutomations let you define a task once and have Copilot cloud agent run it on a schedule or in response to repository events. For example, an automation can triage incoming issues or prepare weekly release notes. You create and manage automations from the **Agents** tab in a repository on GitHub.com. Automations are available in eligible private and internal repositories. See [About Copilot automations](https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-automations).\n\nGitHub Agentic Workflows provide another way to automate tasks in your repositories on GitHub.com. You define tasks in natural language in Markdown files, and they run as GitHub Actions workflows. These workflows can use Copilot or another supported coding agent. See [About GitHub Agentic Workflows](https://docs.github.com/en/copilot/concepts/agents/about-github-agentic-workflows).\n\n## Customizations\n\nOn GitHub.com, custom instructions let you save personal preferences for chat, repository conventions, and organization guidance. Copilot Spaces organize shared context for questions. For delegated work, custom agents and agent skills provide task-specific instructions and resources. Model Context Protocol (MCP) servers connect agents to additional tools and data. Hooks can run commands during agent work for validation or logging. For setup guidance, see [Customize Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot).\n\n## AI models\n\nYou can change the model Copilot uses to generate responses. You may find that different models perform better, or provide more useful responses, depending on the type of questions you ask. Options include premium models with advanced capabilities. To change the model in your IDE, see [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/chat-with-copilot/change-the-chat-model). To change or compare models on GitHub, see [Asking GitHub Copilot questions in GitHub](https://docs.github.com/en/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github#changing-and-comparing-ai-models).\n\nOn GitHub.com, available models depend on your plan and account policies. See [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models).\n\nFor Copilot cloud agent, the ability to select a model also depends on how you start the task. See [Changing the AI model for GitHub Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).\n\n## References to matching public code\n\nIn chat responses and agent sessions on GitHub.com, Copilot can generate code that matches code in public repositories. Code references help you review the matching code and its licensing information so you can decide whether to use it, provide attribution, or remove it.\n\nMatches appear in the context where you are reviewing the output:\n\n- **Chat responses**: If you or your organization allow suggestions matching public code, matching code in a response includes a reference beneath the suggestion. The reference identifies public repositories containing matching code and licensing information, if found.\n- **Agent session logs**: When Copilot generates matching code during a delegated task, the session logs include a link to details of the matched code.\n\nMatches occur infrequently, so most responses do not contain code references. The search covers an index of public repositories on GitHub.com, not private repositories or code hosted elsewhere. The index is refreshed periodically, so it may omit recently added code or refer to code that has since moved or been deleted.\n\nFor instructions on viewing references, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/copilot/how-tos/get-code-suggestions/find-matching-code?tool=webui).\n\n## Access and availability\n\nAvailable features depend on your plan and organization policies. For setup guidance, see [Set up Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot). For usage allowances and costs, see [GitHub Copilot billing and usage](https://docs.github.com/en/copilot/concepts/billing-and-usage).\n\nRepository owners and administrators can disable Copilot cloud agent for particular repositories, even when your plan and policies otherwise allow you to use it. See [Managing access to GitHub Copilot cloud agent](https://docs.github.com/en/copilot/concepts/enterprise/cloud-agent-access).\n\n## Limitations and compatibility\n\nBoth chat and agentic experiences on GitHub.com can produce incorrect or suboptimal code, including code that contains security vulnerabilities. Review and test the output before using it in production. See [Application card: GitHub Copilot Agents](https://docs.github.com/en/copilot/responsible-use/agents).\n\nFor information about built-in security protections, see [Risks and mitigations for GitHub Copilot cloud agent](https://docs.github.com/en/copilot/concepts/agents/cloud-agent/risks-and-mitigations).\n\n### Agentic work\n\nCopilot cloud agent has the following workflow limitations:\n\n- **Repository scope**: Copilot can only make changes in the repository specified when you start a task. It cannot make changes across multiple repositories in one run.\n- **Context access**: By default, the GitHub MCP server only provides access to context in the repository where the agent is working, such as issues and previous pull requests. You can configure broader access through repository MCP settings. See [Configure MCP servers for your repository](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers).\n- **Branches and pull requests**: Copilot can only work on one branch at a time and can open one pull request per task.\n- **Session duration**: Each Copilot cloud agent session has a maximum execution time of 59 minutes. This limit cannot be extended or bypassed. If a task exceeds the limit, the session times out and stops.\nBreak complex tasks into smaller, focused tasks. You can configure a shorter timeout using the `timeout-minutes` setting in your `copilot-setup-steps.yml` file. See [Configure the development environment](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment).\n\n### Repository compatibility\n\n- **Repository rules**: If a ruleset or branch protection rule is incompatible with Copilot cloud agent, access to the agent is blocked. For example, a rule that only allows specific commit authors can prevent Copilot from creating or updating pull requests. If the rule is configured using rulesets, repository administrators can add Copilot as a bypass actor to enable access. See [Creating rulesets for a repository](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-branch-or-tag-ruleset).\n- **Repository hosting**: Copilot cloud agent only works with repositories hosted on GitHub. It cannot work on repositories stored on other code hosting platforms.\n\n## Further reading\n\n- [GitHub Copilot on GitHub](https://docs.github.com/en/copilot/how-tos/copilot-on-github)\n- [GitHub Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent) how-to guides\n- [GitHub Copilot Cookbook](https://docs.github.com/en/copilot/tutorials/copilot-cookbook)\n- For delegating work from tools such as Microsoft Teams and Slack, see [About Copilot integrations](https://docs.github.com/en/copilot/concepts/tools/about-copilot-integrations).\n- For organization and enterprise metrics on pull request creation, merges, and time to merge, see [GitHub Copilot usage metrics](https://docs.github.com/en/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics).",
      "content_chars": 13978,
      "published_date": "2026-10-06"
    },
    {
      "rank": 7,
      "url": "https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/about-cloud-agent",
      "title": "GitHub Copilot on GitHub.com - GitHub Enterprise Cloud Docs",
      "content": "In this article\n\n# GitHub Copilot on GitHub.com\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot on GitHub.com can answer questions about your repositories, plan and make changes, review pull requests, and automate repository tasks. You can ask questions and delegate work from the same prompt box, or use Copilot directly in your issue and pull request workflows.\n\nTo compare where you can use Copilot, see [Where to use GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/where-to-use-github-copilot).\n\n## How Copilot helps on GitHub.com\n\nYou can work with Copilot in several ways:\n\n- **Chat** lets you ask questions about your repositories, understand code, and explore possible solutions.\n- **Agentic experiences** can research a repository, plan changes, and complete multi-step tasks by reading files, editing code, and running tests in a cloud development environment.\n- **Code review** provides feedback on pull requests and suggests fixes.\n- **Automations** run repository tasks on a schedule or in response to events, rather than requiring a new prompt each time.\n\nFor example, you might use chat to understand how a repository handles authentication, then ask an agent to plan and add missing tests. Once the changes are in a pull request, you can request a review from Copilot. To maintain test coverage over time, you could set up an automation to check for missing tests each week and propose additions for you to review.\n\n## Chat and agentic experiences\n\nOn GitHub.com, you can move from asking questions to delegating work in the same conversation.\n\n### Asking questions\n\nChat can explain unfamiliar code, suggest fixes, generate tests, or compare approaches. Follow-up questions let you refine your request without starting a new conversation.\n\nChat is preconfigured with tools for tasks such as creating branches, updating files, and creating or updating issues. It also supports semantic code search.\n\n### Delegating work\n\nCopilot cloud agent can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in an ephemeral cloud development environment, rather than your local IDE. See [GitHub Copilot in IDEs](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/copilot-surfaces/copilot-in-ides).\n\nYou can start work from the agents panel, a conversation, or an issue or pull request on GitHub.com.\n\nFrom security campaigns, you can assign code scanning alerts to Copilot for fixes. See [Fixing alerts in a security campaign](https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/fixing-alerts-in-security-campaign#assigning-alerts-to-copilot-cloud-agent).\n\nWhen implementing changes, Copilot handles branch creation, commit messages, and pushing changes. You can review changes and request refinements before creating a pull request, or request a pull request in your initial prompt. You can also continue the work yourself. See [Research, plan, and iterate on code changes with Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/research-plan-iterate).\n\n### Session context\n\nOn GitHub.com, Copilot Chat and Copilot cloud agent can share context. When you start an agent session from a chat, the session incorporates the context of your conversation. While the session runs, you can continue chatting with Copilot about its progress and steer the work.\n\nCopilot Chat can also answer questions about pull requests created by Copilot by pulling in the relevant agent session logs. You can ask what changed, what was validated, and why, without leaving the conversation.\n\nThis context passing is scoped to the Copilot Chat and cloud agent sessions you are actively working with. It is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see [About GitHub Copilot Memory](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/copilot-memory).\n\nOn GitHub.com, session logs show the work and tools used. Shared sessions and pull requests let teammates with repository access follow the work and review changes. Logs do not replace your own review and testing. See [Managing agent sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).\n\n### Sessions across surfaces\n\nWith remote control enabled, you can monitor and steer a GitHub Copilot CLI session from GitHub.com. It continues running on your original machine, which must stay online. See [About remote control of GitHub Copilot CLI sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/copilot-cli/about-remote-control).\n\nOn GitHub.com, you can ask about your synced session history across Copilot surfaces. This includes Copilot cloud agent and Copilot code review sessions, and sessions from GitHub Copilot CLI, VS Code, JetBrains IDEs, and the GitHub Copilot app.\n\nYou can only query sessions you started. Syncing must be enabled and permitted by your organization's policies. See [Query past sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents#query-past-sessions).\n\n## Code review\n\nOn GitHub.com, Copilot code review reviews pull request changes, identifies potential issues, and suggests fixes. It uses agentic capabilities to gather context from your repository. You can request a review or configure automatic reviews, then review and apply the suggested changes. See [About GitHub Copilot code review](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/code-review).\n\nCopilot can also generate a summary of your changes directly in a pull request description or comment. This helps reviewers understand the changes, but is separate from reviewing the code. See [Creating a pull request summary with GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/copilot-for-github-tasks/create-a-pr-summary).\n\n## Automations and agentic workflows\n\nAutomations let you define a task once and have Copilot cloud agent run it on a schedule or in response to repository events. For example, an automation can triage incoming issues or prepare weekly release notes. You create and manage automations from the **Agents** tab in a repository on GitHub.com. Automations are available in eligible private and internal repositories. See [About Copilot automations](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/about-automations).\n\nGitHub Agentic Workflows provide another way to automate tasks in your repositories on GitHub.com. You define tasks in natural language in Markdown files, and they run as GitHub Actions workflows. These workflows can use Copilot or another supported coding agent. See [About GitHub Agentic Workflows](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/about-github-agentic-workflows).\n\n## Customizations\n\nOn GitHub.com, custom instructions let you save personal preferences for chat, repository conventions, and organization guidance. Copilot Spaces organize shared context for questions. For delegated work, custom agents and agent skills provide task-specific instructions and resources. Model Context Protocol (MCP) servers connect agents to additional tools and data. Hooks can run commands during agent work for validation or logging. For setup guidance, see [Customize Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot).\n\n## AI models\n\nYou can change the model Copilot uses to generate responses. You may find that different models perform better, or provide more useful responses, depending on the type of questions you ask. Options include premium models with advanced capabilities. To change the model in your IDE, see [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-in-your-ide/chat-with-copilot/change-the-chat-model). To change or compare models on GitHub, see [Asking GitHub Copilot questions in GitHub](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github#changing-and-comparing-ai-models).\n\nOn GitHub.com, available models depend on your plan and account policies. See [Supported AI models in GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/reference/ai-models/supported-models).\n\nFor Copilot cloud agent, the ability to select a model also depends on how you start the task. See [Changing the AI model for GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).\n\n## References to matching public code\n\nIn chat responses and agent sessions on GitHub.com, Copilot can generate code that matches code in public repositories. Code references help you review the matching code and its licensing information so you can decide whether to use it, provide attribution, or remove it.\n\nMatches appear in the context where you are reviewing the output:\n\n- **Chat responses**: If you or your organization allow suggestions matching public code, matching code in a response includes a reference beneath the suggestion. The reference identifies public repositories containing matching code and licensing information, if found.\n- **Agent session logs**: When Copilot generates matching code during a delegated task, the session logs include a link to details of the matched code.\n\nMatches occur infrequently, so most responses do not contain code references. The search covers an index of public repositories on GitHub.com, not private repositories or code hosted elsewhere. The index is refreshed periodically, so it may omit recently added code or refer to code that has since moved or been deleted.\n\nFor instructions on viewing references, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/get-code-suggestions/find-matching-code?tool=webui).\n\n## Access and availability\n\nAvailable features depend on your plan and organization policies. For setup guidance, see [Set up Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot). For usage allowances and costs, see [GitHub Copilot billing and usage](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing-and-usage).\n\nRepository owners and administrators can disable Copilot cloud agent for particular repositories, even when your plan and policies otherwise allow you to use it. See [Managing access to GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/enterprise/cloud-agent-access).\n\n## Limitations and compatibility\n\nBoth chat and agentic experiences on GitHub.com can produce incorrect or suboptimal code, including code that contains security vulnerabilities. Review and test the output before using it in production. See [Application card: GitHub Copilot Agents](https://docs.github.com/en/enterprise-cloud@latest/copilot/responsible-use/agents).\n\nFor information about built-in security protections, see [Risks and mitigations for GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/risks-and-mitigations).\n\n### Agentic work\n\nCopilot cloud agent has the following workflow limitations:\n\n- **Repository scope**: Copilot can only make changes in the repository specified when you start a task. It cannot make changes across multiple repositories in one run.\n- **Context access**: By default, the GitHub MCP server only provides access to context in the repository where the agent is working, such as issues and previous pull requests. You can configure broader access through repository MCP settings. See [Configure MCP servers for your repository](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers).\n- **Branches and pull requests**: Copilot can only work on one branch at a time and can open one pull request per task.\n- **Session duration**: Each Copilot cloud agent session has a maximum execution time of 59 minutes. This limit cannot be extended or bypassed. If a task exceeds the limit, the session times out and stops.\nBreak complex tasks into smaller, focused tasks. You can configure a shorter timeout using the `timeout-minutes` setting in your `copilot-setup-steps.yml` file. See [Configure the development environment](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment).\n\n### Repository compatibility\n\n- **Repository rules**: If a ruleset or branch protection rule is incompatible with Copilot cloud agent, access to the agent is blocked. For example, a rule that only allows specific commit authors can prevent Copilot from creating or updating pull requests. If the rule is configured using rulesets, repository administrators can add Copilot as a bypass actor to enable access. See [Creating rulesets for a repository](https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-branch-or-tag-ruleset).\n- **Repository hosting**: Copilot cloud agent only works with repositories hosted on GitHub. It cannot work on repositories stored on other code hosting platforms.\n\n## Further reading\n\n- [GitHub Copilot on GitHub](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github)\n- [GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/cloud-agent) how-to guides\n- [GitHub Copilot Cookbook](https://docs.github.com/en/enterprise-cloud@latest/copilot/tutorials/copilot-cookbook)\n- For delegating work from tools such as Microsoft Teams and Slack, see [About Copilot integrations](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/tools/about-copilot-integrations).\n- For organization and enterprise metrics on pull request creation, merges, and time to merge, see [GitHub Copilot usage metrics](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics).",
      "content_chars": 14722,
      "published_date": "2026-10-06"
    },
    {
      "rank": 8,
      "url": "https://docs.github.com/en/copilot/github-copilot-chat/about-github-copilot-chat",
      "title": "Application card: GitHub Copilot Chat - GitHub Docs",
      "content": "In this article\n\n# Application card: GitHub Copilot Chat\n\nCopy markdown\n\n## In this article\n\n## What is an Application Card?\n\nGitHub\u2019s application and platform cards are intended to help you understand how our AI technology works, the choices application owners can make that influence application performance and behavior, and the importance of considering the whole application, including the technology, the people, and the environment. Application cards are created for AI applications and platform cards are created for AI platform services. These resources can support the development or deployment of your own applications and can be shared with users or stakeholders impacted by them.\n\nAs part of its commitment to responsible AI, GitHub adheres to Microsoft's [six core principles](https://www.microsoft.com/en-us/ai/principles-and-approach/?msockid=3da790040c776d6f2b5485e40de56c06#ai-principles): fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability. These principles are embedded in the [Responsible AI Standard](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/final/en-us/microsoft-brand/documents/Microsoft-Responsible-AI-Standard-General-Requirements.pdf?culture=en-us&country=us), which guides teams in designing, building, and testing AI applications. Application and Platform Cards play a key role in operationalizing these principles by offering transparency around capabilities, intended uses, and limitations. For further insight, readers are encouraged to explore Microsoft\u2019s [Responsible AI Transparency Report](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/msc/documents/presentations/CSR/Responsible-AI-Transparency-Report-2025-vertical.pdf) and [GitHub Terms](https://docs.github.com/en/site-policy/github-terms).\n\n## 1. Overview\n\nGitHub Copilot Chat is a chat interface that lets you interact with GitHub Copilot to ask and receive answers to coding-related questions. GitHub Copilot Chat is available on GitHub.com, in supported IDEs (VS Code, Visual Studio, JetBrains, and Eclipse), on GitHub Mobile, and in Windows Terminal. On GitHub.com and in GitHub Desktop, Copilot can also generate pull request summaries and commit messages\u2014AI-powered overviews of changes made in a pull request or commit.\n\nGitHub Copilot Chat can answer a wide range of coding-related questions on topics including syntax, programming concepts, test cases, debugging, and more. GitHub Copilot Chat is not designed to answer non-coding questions or provide general information on topics outside of coding.\n\nThe primary supported language for GitHub Copilot Chat is English.\n\n## 2. Key terms\n\nThe following list provides a glossary of key terms related to GitHub Copilot Chat:\n\n- **Content filtering**: A safety system that scans prompts and responses to detect and block harmful content before it is shown to the user.\n- **Hallucination**: A phenomenon where a language model generates output that sounds plausible but is factually incorrect, unsupported by the provided context, or entirely fabricated. Hallucinations are a known risk of large language models and are reason that human review of AI-generated output is important.\n- **Large language model (LLM)**: A type of neural network trained on a large body of text data that can generate, analyze, and transform natural language and code. GitHub Copilot Chat uses one or more LLMs to process prompts and produce responses.\n- **Prompt**: The input that is provided to GitHub Copilot Chat. The system combines the prompt with additional context (for example, open files or repository data) before sending it to the language model.\n- **Public code matching**: A feature that checks whether Copilot's suggestions match publicly available code. Depending on your settings, matching suggestions may be turned off or on; if turned on, it can either block or annotate with a reference to the source repository and any license information.\n- **Pull request summary**: An AI-generated overview of the changes in a pull request, consisting of a prose paragraph and a bulleted list of key changes linked to the affected files. Summaries are generated on demand on GitHub.com.\n- **Red teaming**: A structured testing practice in which testers deliberately attempt to provoke unsafe, harmful, or unintended behavior from an AI system. Red teaming helps identify vulnerabilities and improve safety mitigations before and after release.\n- **Training data**: The large body of publicly available text and code that was used to train the foundation models behind GitHub Copilot Chat. The composition of the training data influences the quality and coverage of the model's suggestions across different programming languages, frameworks, and topics.\n\n## 3. Key features or capabilities\n\nThe key features and capabilities outlined here describe what GitHub Copilot Chat is designed to do and how it performs across supported tasks.\n\n- **Conversational coding assistance**: GitHub Copilot Chat provides a natural language interface for asking coding-related questions and receiving answers in the form of code, explanations, or step-by-step guidance. Users can ask follow-up questions to refine responses, and the conversation history is maintained within a session.\n- **Context-aware responses**: GitHub Copilot Chat uses contextual information\u2014such as open files, the active repository, chat history, and (when enabled) web search results\u2014to generate responses that are relevant to the user's current work. The specific context available depends on the platform (GitHub.com, IDE, Mobile, Windows Terminal, or GitHub Desktop).\n- **Multi-platform availability**: GitHub Copilot Chat is available across multiple surfaces, including GitHub.com, supported IDEs (VS Code, Visual Studio, JetBrains, and Eclipse), GitHub Mobile, Windows Terminal, and GitHub Desktop. Each platform offers a tailored experience optimized for its environment.\n- **Agent mode**: In supported IDEs, GitHub Copilot Chat can operate in agent mode, where the model autonomously plans multi-step tasks, invokes tools (such as running terminal commands or editing files), and iterates on results. This extends the chat experience beyond single-turn question-and-answer interactions.\n- **Copilot Spaces**: Spaces let users organize repositories, files, issues, and other materials into a curated collection of context. When a question is asked inside a space, Copilot uses the included context to produce more targeted and relevant responses. Spaces can also be accessed from the IDE via the remote GitHub MCP server.\n- **Pull request summaries**: On GitHub.com, Copilot can generate an AI-powered summary of the changes in a pull request. The output consists of a prose overview followed by a bulleted list of key changes linked to the affected files. Summaries are generated on demand and are intended to help reviewers quickly understand what changed.\n- **Commit message generation**: On GitHub.com and in GitHub Desktop, Copilot can generate a suggested commit summary (title) and description based on the code changes you have selected. In GitHub Desktop, users can select specific lines of code or files to improve context and accuracy. Generated messages can be reviewed and edited before committing.\n- **Bring Your Own Key (BYOK)**: Organizations can connect GitHub Copilot Chat to large language models from supported third-party providers by supplying their own API key, rather than using the default GitHub-hosted model.\n- **Content filtering**: At times, GitHub Copilot Chat may include a content filtering system that scans prompts and responses to detect and block harmful content. A public code matching feature checks whether suggestions match publicly available code and, depending on settings, blocks or annotates those matches with source and license information.\n\n## 4. Intended uses\n\nGitHub Copilot Chat can be used in multiple scenarios across a variety of industries. Some examples of use cases include:\n\n- **Answering coding questions**: Ask GitHub Copilot Chat for help or clarification on specific coding problems and receive responses in natural language or code snippet format. The response may draw on the model's training data, repository context, and web search results (when enabled).\n- **Explaining code and suggesting improvements**: Generate natural language descriptions of a function's purpose, inputs, outputs, and dependencies. GitHub Copilot Chat can also suggest improvements such as better error handling or more readable control flow. Note that generated explanations may not always be accurate or complete and should be reviewed.\n- **Generating unit test cases**: GitHub Copilot Chat can help write unit test cases by generating code snippets based on the code open in the editor or a highlighted code snippet. It can suggest possible input parameters, expected output values, and assertions based on the function's signature and body. GitHub Copilot Chat can also suggest test cases for edge cases and boundary conditions\u2014such as error handling, null values, or unexpected input types\u2014that might be difficult to identify manually. Generated test cases may not cover all possible scenarios; manual testing and code review are still necessary.\n- **Proposing code fixes**: Get suggested fixes for bugs based on the error message, code syntax, and surrounding context. GitHub Copilot Chat can suggest changes to variables, control structures, or function calls that might resolve the issue. Note that suggested fixes may not always be optimal or complete.\n- **Planning coding tasks**: Read and summarize GitHub issues, answer questions about them, or propose next steps.\n- **Learning about releases, discussions, and commits**: Summarize what changed in a release, the gist of a discussion, or the changes in a specific commit.\n- **Summarizing pull request changes (GitHub.com)**: Generate an AI-powered summary of the changes in a pull request\u2014including a prose overview and a bulleted list of key changes linked to the affected files\u2014to help reviewers quickly understand what changed and where to focus their review.\n- **Generating commit messages (GitHub.com and GitHub Desktop)**: Generate a commit message summary (title) and description based on the code changes you've selected to commit, helping you save time and maintain clear commit histories. In GitHub Desktop, you can select specific lines of code or files for better context understanding to increase accuracy. You can review and edit the suggested title and description before committing.\n- **Finding the right command (Windows Terminal)**: Ask Copilot to suggest commands that help you perform tasks in the command line. You can revise your question until the returned command meets your expectations, then insert it into your command line to run it.\n- **Explaining an unfamiliar command (Windows Terminal)**: Ask Copilot to generate a natural language description of a command's functionality, including its input and output parameters and usage examples. Note that generated explanations may not always be accurate or complete.\n- **Developing a new feature (Spaces)**: Bundle relevant code, product specs, and design notes in a space so Copilot can explain the current implementation, highlight gaps, and draft new code or next steps.\n- **Defining logic for repeated tasks (Spaces)**: Document a process once\u2014with flowcharts, examples, or schemas\u2014and reuse it across your team for consistent patterns and reusable templates.\n- **Sharing knowledge with teammates (Spaces)**: Collect the latest code and documentation in one place so Copilot can explain systems, answer questions, and onboard teammates.\n\n## 5. Models and training data\n\nGitHub Copilot Chat leverages a variety of AI models to power the experience that users see. For a comparison of the models available for Copilot, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison). For the full list of supported models, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models). For information on where models are hosted, see [Hosting of models for GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/model-hosting). To learn more about the data used to train the foundation models behind GitHub Copilot Chat, refer to the linked AI model comparison above and [What data has GitHub Copilot been trained on?](https://github.com/features/copilot#faq) in the GitHub Copilot FAQ.\n\n### Using Bring Your Own Key (BYOK)\n\nWhen you use Bring Your Own Key with GitHub Copilot Chat, you can connect the chat experience to large language models from supported providers beyond the default Copilot model. Examples of supported providers include Anthropic, AWS Bedrock, Google AI Studio, Microsoft Foundry, OpenAI, OpenAI-compatible providers, and xAI. You add your API key for the chosen provider directly in your Copilot settings.\n\nWhen BYOK is active:\n\n- **Feature scope**: Your chosen model is used within GitHub Copilot Chat. In Agent mode, BYOK powers the main conversation, but certain actions such as code application or other tool calls may still use Copilot-integrated models optimized for those tasks. These built-in models do not run through your BYOK provider.\n- **Content filtering**: Regardless of which provider is active, responses still pass through GitHub's API and may have content filtering before results are shown to you.\n- **Quality considerations**: Suggestions may vary depending on the strengths and training coverage of your chosen provider.\n- **Data handling**: When using BYOK, your prompts and responses are transmitted to your selected provider and may be subject to that provider's data retention and privacy policies.\n- **Your responsibilities**: You are responsible for the following:\n - Provider API key security\n- Usage costs or quotas\n- Output validation\n- Evaluating whether your chosen model meets your safety and quality requirements\n- Compliance with your selected provider's terms\n- Determining whether your chosen model complies with applicable laws\n- Ensuring that a human reviews any output before using it to make decisions that affect people\n- **Export restrictions**: Certain AI models may be subject to export controls. Verify your selected provider and model are authorized for use in your jurisdiction.\n\nBYOK empowers your organization to choose the language model that best fits your needs. Note that model performance and safety characteristics are provider-dependent.\n\n## 6. Performance\n\nGitHub Copilot Chat works by using a combination of natural language processing and machine learning to understand your question and provide you with an answer. This process involves:\n\n1. **Input processing**: The user's prompt is pre-processed by the system, combined with contextual information (for example, the current repository, open files, or chat history), and sent to a large language model. User input can take the form of code snippets or plain language.\n2. **Language model analysis**: The prompt is passed through the language model, which is a neural network trained on a large body of text data. The language model analyzes the input prompt.\n3. **Response generation**: The model generates a response based on its analysis of the input prompt and the context provided to it. This response can take the form of generated code, code suggestions, or explanations of existing code.\n4. **Output formatting**: The response is formatted with syntax highlighting, indentation, and other features to add clarity. Depending on the type of question, links to context that the model used\u2014such as source code files, issues, or documentation\u2014may also be provided.\n\n### Differences by experience\n\n- **On GitHub.com**: The model can gather additional context from repository data stored on GitHub and web search results (when enabled by your administrator). Responses may include links to source code files, issues, or documentation.\n- **Pull request summaries (GitHub.com)**: When a user requests a summary, a workflow uses the code diffs from files to build a prompt and requests Copilot to generate an overall summary. The output consists of a prose paragraph giving an overview of the changes, followed by a bulleted list of key changes linked to the respective lines of code. You can generate a summary in the description of a new or existing pull request, or in a comment on the pull request timeline. Larger pull requests may take up to a couple of minutes to process. The only supported language for pull request summaries is English.\n- **Commit message generation (GitHub.com)**: When you click the **Commit changes** button on GitHub.com, Copilot generates a suggested summary (title) and description based on the code changes in the selected files. The text is inserted into the summary and description fields for you to review and edit before committing. The only supported language for commit message generation is English.\n- **Commit message generation (GitHub Desktop)**: When you click the Copilot button in GitHub Desktop, Copilot generates a suggested summary (title) and description based on the code changes you've selected. You can select specific lines of code or files to improve context and accuracy, and you can regenerate suggestions before finalizing. The only supported language is English.\n- **In your IDE**: The system combines user input with contextual information such as the name of the repository and the files the user has open. In VS Code and Visual Studio, additional context can be provided automatically from an optional `.github/copilot-instructions.md` file (the user can disable this in settings). When using the `@github` chat participant in VS Code or Visual Studio, GitHub Copilot Chat can also gather context from code stored on GitHub and from Bing search results (if enabled by your administrator).\n- **On GitHub Mobile**: The input prompt is pre-processed and sent to the language model. The system is only intended to respond to coding-related questions. The options available vary by Copilot plan: users with a Copilot Enterprise subscription can have conversations using data from private indexed repositories and, if the web search integration is enabled, receive responses informed by web search results. Users with a Copilot Pro subscription can discuss top popular public repositories.\n- **In Windows Terminal**: The user's prompt is combined with contextual information (the name of the active shell and the chat history) and sent to the language model. Responses take the form of a suggested command or an explanation of a command. Suggested commands are not run automatically\u2014you must click on a command to insert it into your command line and then manually run it.\n- **In Copilot Spaces**: Spaces let you organize the context that GitHub Copilot Chat uses to answer your questions. A space can include repositories, code, pull requests, issues, free-text content like transcripts or notes, images, and file uploads. When you submit a question in a space, Copilot augments your request with relevant context from that space. Spaces can also be accessed from the IDE via the remote GitHub MCP server. Not all content in a space is used in every response\u2014Copilot processes a portion of the included content, so being selective about what you add helps ensure relevance.\n\nGitHub Copilot Chat is intended to provide you with the most relevant answer to your question. However, it may not always provide the answer you are looking for. Users of GitHub Copilot Chat are responsible for reviewing and validating responses generated by the system to ensure they are accurate and appropriate.\n\n## 7. Limitations\n\nUnderstanding GitHub Copilot Chat's limitations is crucial to determine if it is used within safe and effective boundaries. While we encourage customers to leverage GitHub Copilot Chat in their innovative solutions or applications, it's important to note that GitHub Copilot Chat was not designed for every possible scenario. We encourage users to refer to [GitHub Terms](https://docs.github.com/en/site-policy/github-terms) as well as the following considerations when choosing a use case:\n\n- **Limited scope**: GitHub Copilot Chat has been trained on a large body of code but may not be able to handle more complex code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data. For example, JavaScript is well-represented and well-supported, while less common languages may yield lower-quality results.\n- **Potential biases**: Training data drawn from existing code repositories may contain biases and errors that can be perpetuated by the tool. GitHub Copilot Chat may also be biased towards certain programming languages or coding styles, which can lead to suboptimal or incomplete code suggestions.\n- **Security risks**: Generated code can potentially expose sensitive information or vulnerabilities if not reviewed carefully. Always review and test generated code thoroughly, especially for security-sensitive applications.\n- **Matches with public code**: While the probability is low, GitHub Copilot Chat may produce code that matches code in the training set. You should take the same precautions as you would with any code that uses material you did not independently originate including rigorous testing, IP scanning, and checking for security vulnerabilities. For more information, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/copilot-for-common-tasks/find-matching-code).\n- **Inaccurate code**: GitHub Copilot Chat may generate code that appears valid but is not semantically or syntactically correct, or does not accurately reflect the intent of the developer. Carefully review and test generated code, particularly for critical or sensitive applications.\n- **Inaccurate responses to non-coding topics**: GitHub Copilot Chat is not designed to answer non-coding questions, and its responses in those contexts may be irrelevant or nonsensical.\n- **Risk of destructive commands (Windows Terminal)**: Copilot may suggest commands that could be destructive\u2014such as deleting content or formatting a hard drive\u2014that may be necessary in certain scenarios but can cause problems if used incorrectly. You are ultimately responsible for any commands you choose to execute. Despite the presence of fail-safes and safety mechanisms, executing commands carries inherent risks.\n- **Lines changed limits for PR summaries (GitHub.com)**: Files with more than 400 combined additions and deletions are excluded from summarization.\n- **PR summaries are not auto-updated (GitHub.com)**: Pull request summaries are only created when users request them manually. When updates or changes are made to the pull request, the summary is not automatically refreshed. Users can request a new summary, but should carefully review the updated output\u2014it carries the same risks of inaccuracy as the original.\n- **Replication of PR content (GitHub.com)**: Because a summary outlines the changes in a pull request, if harmful or offensive terms appear in the pull request content, there is potential for the summary to replicate those terms. Users should expect terms used in their PR to appear in the AI-generated summary.\n- **Limited scope for commit messages (GitHub.com and GitHub Desktop)**: Commit message generation may struggle with intricate code changes, short diff windows, or recently developed programming languages. The quality of suggestions depends on the availability and diversity of training data for the languages involved.\n- **Replication of commit content (GitHub.com and GitHub Desktop)**: Because a commit message summarizes the changes in a commit, if harmful or offensive terms appear in the code changes, there is potential for the generated message to include those terms.\n- **Commit messages are not auto-updated (GitHub.com and GitHub Desktop)**: Commit messages are only generated when you request them. When you make additional changes, the commit message is not automatically refreshed. You can regenerate a new suggestion, but should carefully review the updated output\u2014it carries the same risks of inaccuracy as the original.\n- **Interpretation of user intent (Spaces)**: Spaces help ground GitHub Copilot Chat's responses in curated context, but the system may still misunderstand your intent. Always review output to confirm it reflects your goals.\n- **Context limits (Spaces)**: Spaces have defined size limits, and GitHub Copilot Chat only processes a portion of the content you include. Not every file, document, or note in a space will be used in a response. Being selective about what you add helps ensure the most relevant context is used.",
      "content_chars": 24921,
      "published_date": "2021-11-02"
    },
    {
      "rank": 9,
      "url": "https://docs.github.com/en/copilot/concepts/enterprise/learning-about-new-features-and-models",
      "title": "Learning about new features and models - GitHub Docs",
      "content": "In this article\n\n# Learning about new features and models\n\nCopy markdown\n\n## In this article\n\n## Up next\n\n[Pilot a new Copilot feature or model in your enterprise](https://docs.github.com/en/copilot/tutorials/roll-out-at-scale/govern-at-scale/pilot-a-feature-or-model)\n\nGitHub Copilot is evolving rapidly, with new features and models released regularly. If you're an enterprise administrator, staying informed helps you make confident decisions about which capabilities to enable, when to adopt them, and how to manage risk across your organizations.\n\nThis article provides guidance on navigating the Copilot landscape, understanding different types of features and models, and preparing for upcoming changes.\n\n## Keeping up to date with Copilot changes\n\nYou can use GitHub Docs and the GitHub Blog to keep track of new releases.\n\n### Learning about new Copilot features\n\nTo learn about new Copilot features, we recommend monitoring these two locations:\n\n- **Copilot blog updates**: For broader news and updates about Copilot, see the [Copilot blog](https://github.blog/ai-and-ml/github-copilot/).\n- **Changelog**: For announcements about newly released and updated features, follow the [Copilot changelog](https://github.blog/changelog/?label=copilot).\n\nCopilot's capabilities and supporting features fall into four categories:\n\n| Type | Description | Examples | Considerations |\n| --- | --- | --- | --- |\n| Assistive | Respond to prompts and provide suggestions, but require human review before changes are made. | Inline suggestions, Copilot Chat, Copilot pull request summaries. | All changes require user approval. |\n| Agentic | Autonomously research, plan, and make changes on behalf of users. | Copilot cloud agent, third-party agents. | Can work autonomously, but with built-in protections. |\n| Customizations | Add context, instructions, tools, skills, and agents to tailor how Copilot responds and works. | Custom instructions, prompt files, Copilot Spaces, MCP servers, agent skills, custom agents. | Support and configuration vary by feature and surface. Organization and enterprise policies can control access to some customizations. |\n| External AI agents, models, and tools | External coding agents, models, and tools, including MCP servers from other providers, that work alongside Copilot cloud agent to complete tasks asynchronously. | Anthropic Claude, OpenAI Codex. | Same as agentic. Review provider documentation and enable via policies. See [About third-party coding agents](https://docs.github.com/en/copilot/concepts/agents/about-third-party-coding-agents). |\n\nEach feature has its own enablement requirements and policy settings. When a new feature is released:\n\n1. Review the feature documentation to understand its capabilities.\n2. Check the policy settings available at the enterprise and organization level. See [GitHub Copilot policies for enterprises and organizations](https://docs.github.com/en/copilot/concepts/enterprise/policies).\n3. Consider running a pilot with a subset of users before broader rollout.\n\n### Learning about new Copilot models\n\nGitHub Copilot uses multiple AI models from different providers to power its features. Different models have different strengths: some prioritize speed and cost-efficiency, while others are optimized for accuracy, reasoning, or working with multimodal inputs (like images and code together).\n\nUsers will have access to different models depending on the feature they're using and your enterprise's Copilot plan and policies.\n\nYou can find information about the models available and upcoming models in the following locations:\n\n- **Supported models**: For a complete list of available models and their capabilities, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models).\n- **Model comparison**: To compare model capabilities side by side, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison).\n- **Changelog**: Model updates are announced in the [Copilot changelog](https://github.blog/changelog/label/copilot/).\n\n#### Special categories\n\nGitHub categorizes certain types of model, allowing you to plan for model transitions and set user expectations.\n\n| Model type | Description | Why it matters |\n| --- | --- | --- |\n| Utility model | A small set of models that power background GitHub features across surfaces. | Your enterprise cannot disable these models. Monitor these to ensure they are compliant. |\n| Base model | The default model when no other models are enabled. | Automatically enabled within 60 days of designation. |\n| LTS model | A model supported for one year from designation. | Allows enterprises to build workflows around a stable model. |\n\nFor more information, see [Utility models](https://docs.github.com/en/copilot/concepts/models/utility-models) and [Base and long-term support (LTS) models](https://docs.github.com/en/copilot/concepts/models/fallback-and-lts-models).\n\n### Default enablement\n\nFor enterprises with Copilot Business or Copilot Enterprise plans, two separate policies control whether unconfigured generally available (GA) features and models default to enabled or disabled. If these policies are enabled, users benefit from the latest features and models without the need for administrator intervention.\n\nThe models policy is already active. The feature policy will become active soon.\n\nFor more information, see [About default availability of Copilot features and models](https://docs.github.com/en/copilot/concepts/enterprise/default-availability).\n\n## Considering different release stages\n\nCopilot features and models progress through different release stages. Understanding release stages helps you decide when to enable features for your organization. Each stage has different expectations for stability and support.\n\n| Stage | Availability | Stability |\n| --- | --- | --- |\n| Private preview | Limited set of customers by invitation. | May change significantly based on feedback. |\n| Public preview | All eligible customers who opt in. | Functional but may have limitations or change. |\n| Generally available (GA) | All customers. | Fully supported and recommended for production. |\n\nMany preview features are covered by the [GitHub Data Protection Agreement](https://gh.io/dpa), meaning you can test them without breaching compliance requirements. See [GitHub DPA-Covered Previews](https://gh.io/dpa-previews) for a list.\n\nPreview features are controlled by policy settings at the organization and enterprise level. The **Opt in to preview features** policy allows administrators to enable or disable preview features on the GitHub website specifically. See [Managing policies and features for GitHub Copilot in your enterprise](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies) and [Managing policies and features for GitHub Copilot in your organization](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies).\n\n## Reviewing information about Responsible AI\n\nGitHub is committed to responsible AI development and provides transparency documentation for each Copilot feature.\n\nEach Copilot feature has a dedicated **responsible use** article describing its purpose, capabilities, and limitations. See [Responsible use of GitHub Copilot features](https://docs.github.com/en/copilot/responsible-use).",
      "content_chars": 7444,
      "published_date": "2026-10-06"
    },
    {
      "rank": 10,
      "url": "https://docs.github.com/en/copilot/responsible-use/agents",
      "title": "Application card: GitHub Copilot Agents - GitHub Docs",
      "content": "In this article\n\n# Application card: GitHub Copilot Agents\n\nCopy markdown\n\n## In this article\n\n## What is an Application Card?\n\nGitHub\u2019s application and platform cards are intended to help you understand how our AI technology works, the choices application owners can make that influence application performance and behavior, and the importance of considering the whole application, including the technology, the people, and the environment. Application cards are created for AI applications and platform cards are created for AI platform services. These resources can support the development or deployment of your own applications and can be shared with users or stakeholders impacted by them.\n\nAs part of its commitment to responsible AI, GitHub adheres to Microsoft's [six core principles](https://www.microsoft.com/en-us/ai/principles-and-approach/?msockid=3da790040c776d6f2b5485e40de56c06#ai-principles): fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability. These principles are embedded in the [Responsible AI Standard](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/final/en-us/microsoft-brand/documents/Microsoft-Responsible-AI-Standard-General-Requirements.pdf?culture=en-us&country=us), which guides teams in designing, building, and testing AI applications. Application and Platform Cards play a key role in operationalizing these principles by offering transparency around capabilities, intended uses, and limitations. For further insight, readers are encouraged to explore Microsoft\u2019s [Responsible AI Transparency Report](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/msc/documents/presentations/CSR/Responsible-AI-Transparency-Report-2025-vertical.pdf) and [GitHub Terms](https://docs.github.com/en/site-policy/github-terms).\n\n## 1. Overview\n\nGitHub Copilot includes several agentic features that go beyond suggestion and conversation\u2014they can review code, take action on your behalf, and build applications. This card covers the following experiences:\n\n- **Copilot code review**: Reviews pull request diffs and metadata on GitHub.com, producing feedback comments and suggested changes.\n- **Copilot cloud agent**: An asynchronous agent on GitHub.com that can create branches, write code, and open pull requests in response to assigned issues. The cloud agent runs in an ephemeral, firewalled environment with automated security scanning.\n- **Copilot CLI**: A command-line tool that can create and modify files, execute commands, and perform multi-step tasks. By default, filesystem access is scoped to the directory where the CLI was started. Permission prompts depend on the active permission mode. When computer use is enabled, Copilot CLI can also interact with desktop applications outside that directory scope.\n- **Copilot SDK**: A programmatic library that allows developers to build custom AI-powered applications using Copilot. The SDK communicates with Copilot CLI over JSON-RPC and supports custom agents, MCP server integrations, lifecycle hooks, and session management.\n- **GitHub Copilot app**: A desktop application for directing agent sessions across local repositories, git worktrees, and cloud sandboxes. The app uses GitHub Copilot CLI and GitHub Copilot SDK as its foundation and adds a user interface for parallel sessions, quick chats, GitHub issue and pull request workflows, automations, and canvases. When computer use is enabled, the app can also interact with desktop applications.\n\nThese features share common principles\u2014human oversight, review of outputs, and responsible use\u2014but differ in their execution environments, permissions, and data flows. The sections below describe each in context.\n\n## 2. Key terms\n\nThe following list provides a glossary of key terms related to GitHub Copilot Agents:\n\n- **Code suggestion**: A specific code change proposed by Copilot code review as part of its feedback on a pull request. Code suggestions are presented as suggested changes that can be applied with a couple of clicks.\n- **Content filtering**: A safety system that scans prompts and responses to detect and block harmful, offensive, or insecure content before it is shown to the user.\n- **Computer use**: An optional capability in GitHub Copilot CLI and GitHub Copilot app that allows an agent to interact with desktop applications. Its tools can read accessible application content and visual context through the operating system's accessibility tree or screenshots when visual context is needed, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across applications.\n- **Custom instructions**: Natural language descriptions of coding style and best practices that a repository maintainer can configure to guide Copilot code review's feedback. Custom instructions help Copilot understand the conventions and standards of a specific codebase.\n- **Hallucination**: A phenomenon where a language model generates output that sounds plausible but is factually incorrect, unsupported by the provided context, or entirely fabricated. In code review, hallucination can manifest as feedback that highlights problems that do not exist or are based on misunderstandings of the code.\n- **Large language model (LLM)**: A type of neural network trained on a large body of text data that can generate, analyze, and transform natural language and code. Copilot Agents use one or more LLMs to process context and produce responses.\n- **Ephemeral development environment**: A temporary, isolated compute environment created for each cloud agent session. The environment is destroyed after the session ends, ensuring that no state persists between runs.\n- **Firewall**: A network-level control enabled by default for the cloud agent that prevents outbound connections to unauthorized hosts, protecting against accidental or malicious exfiltration of code or data.\n- **AI credit**: A unit of consumption for Copilot features. Each use of Copilot code review consumes AI credits.\n- **Permission prompt**: An interactive confirmation step in Copilot CLI that asks the user to approve an action\u2014such as modifying a file, executing a command, or accessing files outside the current directory\u2014before the agent proceeds. Permission prompts are a key safety mechanism for local agentic execution.\n- **Copilot SDK**: A programmatic library (`@github/copilot-sdk`) that lets developers build custom AI-powered applications by creating sessions, sending prompts, and receiving streaming responses from Copilot. The SDK communicates with Copilot CLI over JSON-RPC.\n- **JSON-RPC**: The communication protocol used between the Copilot SDK and Copilot CLI. The SDK sends structured requests to the CLI process, which handles model interaction and tool execution.\n- **Custom agent (SDK)**: A named agent configuration within the SDK that has its own system prompt, scoped tools, and optional MCP servers. The SDK runtime can automatically delegate to sub-agents based on user intent.\n- **Hooks (SDK)**: Lifecycle callbacks in the Copilot SDK that let developers inject custom logic at specific points during a session, such as before or after tool use, on session start or end, and on error.\n\n## 3. Key features or capabilities\n\nThe key features and capabilities outlined here describe what GitHub Copilot Agents are designed to do and how they perform across supported tasks.\n\n- **Automated code review feedback**: When a user requests a review from Copilot, it scans the code changes plus additional relevant context and provides feedback on the code. Feedback may include natural language comments and specific code suggestions linked to particular lines and files.\n- **Customizable review guidance**: Copilot code review can be customized with custom instructions\u2014natural language descriptions of coding style and best practices\u2014so that feedback reflects a repository's conventions and standards.\n- **Autonomous pull request creation**: The Copilot cloud agent can pick up a task from an issue, a pull request comment, or Copilot Chat, create a branch, generate tailored code changes, and open a pull request. After the initial pull request is created, the agent can iterate based on your feedback and reviews.\n- **Ephemeral, firewalled execution**: While working on a task, the cloud agent has access to its own ephemeral development environment where it can make changes to code, execute automated tests, and run linters. A firewall is enabled by default to prevent data exfiltration.\n- **Automated security scanning**: During code generation, the cloud agent automatically analyzes newly generated code for security vulnerabilities using CodeQL, secret scanning, and dependency analysis, and attempts to resolve any issues before they are introduced.\n- **External integrations**: The cloud agent can receive information and context from MCP like workIQ and Microsoft 365, and external applications like Microsoft Teams, Linear, Slack, and Jira, enabling teams to assign tasks and track progress directly within their existing workflows.\n- **Local agentic execution (Copilot CLI)**: Copilot CLI provides a chat-like interface in the terminal that can autonomously create and modify files, execute commands, and perform multi-step tasks. By default, filesystem access is scoped to the directory where the CLI was started. The active permission mode determines whether the CLI prompts before modifying files or running commands.\n- **Desktop application interaction (computer use)**: In local Copilot CLI and Copilot app sessions, computer use can read accessible application content and visual context through the operating system's accessibility tree or screenshots when visual context is needed, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across applications.\n\n## 4. Intended uses\n\nGitHub Copilot Agents can be used in multiple scenarios across a variety of industries. Some examples of use cases include:\n\n- **Supplementing human code review**: Copilot code review is intended to quickly provide feedback on a developer's code, enabling developers to get code ready to merge more quickly and increasing overall code quality.\n- **Codebase maintenance**: The cloud agent can tackle security-related fixes, dependency upgrades, and targeted refactoring.\n- **Feature development**: The cloud agent can implement incremental feature requests, develop additional test suites, and create or update documentation.\n- **Prototyping new projects**: The cloud agent and Copilot CLI can greenfield new concepts, helping developers explore ideas quickly.\n- **Setting up your environment (CLI)**: Copilot CLI can run commands in your terminal to set up your local environment to work on existing projects.\n- **Finding the right command (CLI)**: Copilot CLI can suggest commands to perform tasks you're trying to complete, and explain unfamiliar commands in natural language.\n- **Working with legacy and GUI-only applications (computer use)**: Computer use can help with workflows in local desktop applications that do not provide an API, command-line interface, or MCP integration. Users should describe the outcome, applications, and important constraints, then review the actions and result.\n- **Building custom AI applications (SDK)**: The Copilot SDK enables developers to build applications that leverage Copilot for code generation, natural language interaction, and task automation in their own products and workflows.\n- **Multi-agent orchestration (SDK)**: Using custom agents and sub-agents, developers can build sophisticated workflows where multiple specialized agents collaborate on complex tasks, with automatic delegation based on user intent.\n- **Extending applications with external tools (SDK)**: The SDK's MCP server support allows developers to connect their applications to external data sources and services, expanding the range of tasks their agents can perform.\n\n## 5. Models and training data\n\nGitHub Copilot Agents leverage a variety of AI models to power the experience that users see. For a comparison of the models available for Copilot, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison). For the full list of supported models, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models). For information on where models are hosted, see [Hosting of models for GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/model-hosting). To learn more about the data used to train the foundation models behind GitHub Copilot Agents, refer to the linked AI model comparison above and [What data has GitHub Copilot been trained on?](https://github.com/features/copilot#faq) in the GitHub Copilot FAQ.\n\nCopilot code review is a purpose-built product that uses a carefully tuned mix of models, prompts, and system behaviors to deliver consistent, high-quality feedback across a wide range of codebases. Model switching is not supported, as changing the model is likely to compromise reliability, user experience, and the quality of review comments. Copilot code review may use models that are not enabled on your organization's \"Models\" settings page.\n\nThe Copilot cloud agent uses a large language model to reason about tasks, generate code, and leverage tools within its ephemeral development environment. The agent has been evaluated across a variety of programming languages. English is the primary supported language for prompts and responses.\n\nCopilot CLI uses a large language model to reason about tasks, generate code, modify files, and execute commands in your local terminal environment. The agent has been evaluated across a variety of programming languages. English is the primary supported language for prompts and responses.\n\nThe Copilot SDK communicates with Copilot CLI over JSON-RPC, using the same underlying models and capabilities. Applications built with the SDK use the same models available to the authenticated Copilot user or organization. Developers can also bring their own API keys (BYOK) to use custom model providers.\n\n## 6. Performance\n\n### Differences by experience\n\n#### Copilot cloud agent\n\nThe Copilot cloud agent works by using a combination of natural language processing and machine learning to understand your task and make changes in a codebase. This process can be broken down into a number of steps:\n\n1. **Prompt processing**: The task provided through an issue, pull request comment, or Copilot Chat message is combined with other relevant, contextual information to form a prompt. That prompt is sent to a large language model for processing. Inputs can take the form of plain natural language, code snippets, or images.\n2. **Language model analysis**: The prompt is passed through a large language model, which is a neural network that has been trained on a large body of data. The language model analyzes the input prompt to help the agent reason about the task and leverage necessary tools.\n3. **Response generation**: The language model generates a response based on its analysis of the prompt. This response can take the form of natural language suggestions and code suggestions.\n4. **Output formatting**: Once the agent completes its first run, it updates the pull request description with the changes it made. The agent may include supplemental information about resources it could not access and provide suggestions on steps to resolve. You may provide feedback by commenting within the pull request or explicitly mentioning the agent (`@copilot`). The agent will then resubmit that feedback for further analysis and respond with updated changes.\n\nCopilot cloud agent is intended to provide the most relevant solution for task resolution. However, it may not always provide the answer you are looking for. You are responsible for reviewing and validating responses generated by Copilot cloud agent to ensure they are accurate and appropriate.\n\n#### Copilot code review\n\nCopilot code review inspects your code and provides feedback using a combination of natural language processing and machine learning. This process can be broken down into a number of steps:\n\n1. **Input processing**: The code changes are combined with other relevant, contextual information (for example, the pull request's title and body), and any custom instructions that have been defined, to form a prompt. That prompt is sent to a large language model.\n2. **Language model analysis**: The prompt is passed through the Copilot language model, which is a neural network that has been trained on a large body of text data. The language model analyzes the input prompt.\n3. **Response generation**: The language model generates a response based on its analysis of the input prompt. This response can take the form of natural language suggestions and code suggestions.\n4. **Output formatting**: The response is presented to the user either directly in a supported editor or as a pull request review on GitHub.com, providing code feedback linked to specific lines of specific files. Where Copilot has provided a code suggestion, the suggestion is presented as a suggested change, which can be applied with a couple of clicks.\n\n#### Copilot CLI\n\nCopilot CLI works by using a combination of natural language processing and machine learning to understand your task and make changes in a codebase. This process can be broken down into a number of steps:\n\n1. **Input processing**: Your input is combined with relevant contextual information to form a prompt. That prompt is sent to a large language model for processing. Inputs can take the form of plain natural language, code snippets, or references to files in your terminal.\n2. **Language model analysis**: The prompt is passed through a large language model, which is a neural network that has been trained on a large body of data. The language model analyzes the input prompt to help the agent reason about the task and use the necessary tools.\n3. **Response generation**: The language model generates a response based on its analysis of the prompt. This response can take the form of natural language suggestions, code suggestions, file modifications, and command executions.\n4. **Output formatting**: The response is formatted and presented using syntax highlighting, indentation, and other formatting features. The agent may also execute commands in your local environment and create, edit, or delete files in your file system in order to complete the task. All such actions require explicit permission prompts.\n\nYou may provide feedback to the agent after it returns a response in the interactive chat window. The agent will resubmit that feedback to the language model for further analysis and return an additional response.\n\n#### Copilot SDK\n\nThe Copilot SDK provides a programmatic interface to Copilot's agentic capabilities. Applications built with the SDK follow this process:\n\n1. **Session creation**: The application creates a session with the SDK, specifying the model, system prompt, available tools, custom agents, MCP servers, and hooks. The SDK establishes a JSON-RPC connection to Copilot CLI.\n2. **Prompt submission**: User input is submitted to the session. The SDK routes the prompt (along with session context) to the CLI, which forwards it to the language model.\n3. **Agent execution**: The language model reasons about the task and may invoke tools, delegate to sub-agents, or connect to MCP servers. Lifecycle hooks fire at each stage, allowing the application to inject custom logic.\n4. **Response streaming**: Responses are streamed back to the application, which can present them in any format appropriate for its interface. The SDK provides structured events for text, tool calls, errors, and completion signals.\n\n## 7. Limitations\n\nUnderstanding GitHub Copilot agentic features' limitations is crucial to determine they are used within safe and effective boundaries. While we encourage customers to leverage these features in their innovative solutions or applications, it's important to note that they were not designed for every possible scenario. We encourage users to refer to [GitHub Terms](https://docs.github.com/en/site-policy/github-terms) as well as the following considerations when choosing a use case:\n\n- **Missed code quality problems**: Copilot may not identify all of the problems that are present in code, especially where changes are large or complex. To ensure that all relevant problems are identified and corrected, Copilot code review should be supplemented with careful human code review.\n- **False positives**: Copilot code review has a risk of hallucination\u2014it may highlight problems in reviewed code that do not exist or are based on misunderstandings of the code. Comments generated by Copilot code review should be carefully reviewed and considered before taking action and making changes.\n- **Inaccurate or insecure code suggestions**: As part of its comments, Copilot code review may provide specific code suggestions. The code generated may appear to be valid but may not actually be semantically or syntactically correct, or may not correctly resolve the problem identified in the comment. In addition, code generated by Copilot may contain security vulnerabilities or other issues. You should always carefully review and test code generated by Copilot.\n- **Potential biases**: Copilot's training data is drawn from existing code repositories, which may contain biases and errors that can be perpetuated by the tool. Additionally, Copilot code review may be biased toward certain programming languages or coding styles, which can lead to suboptimal or incomplete feedback.\n- **Limited scope (cloud agent)**: The language model used by the cloud agent has been trained on a large body of code but still has a limited scope and may not be able to handle certain code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data for that language.\n- **Inaccurate code (cloud agent)**: The cloud agent may generate code that appears to be valid but may not actually be semantically or syntactically correct, or may not accurately reflect the intent of the developer. You should carefully review and test generated code, particularly when dealing with critical or sensitive applications.\n- **Security risks (cloud agent)**: The cloud agent generates code and natural language based on the context of an issue or comment within a repository, which can potentially expose sensitive information or vulnerabilities if not used carefully. You should review all outputs generated by the agent thoroughly prior to merging.\n- **Public code matches (cloud agent)**: The cloud agent may generate code that is a match or near match of publicly available code, even if the \"Suggestions matching public code\" policy is set to \"Block.\" If this happens, Copilot will show matches in the agent session logs with a link to display details of the matched code.\n- **Limited scope (CLI)**: The language model used by Copilot CLI has been trained on a large body of code but still has a limited scope and may not be able to handle certain code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data for that language.\n- **Inaccurate code (CLI)**: Copilot CLI may generate code that appears to be valid but may not actually be semantically or syntactically correct, or may not accurately reflect the intent of the developer. You should carefully review and test generated code, particularly when dealing with critical or sensitive applications.\n- **Security risks (CLI)**: Copilot CLI generates code and natural language based on the context of your local environment, which can potentially expose sensitive information or vulnerabilities if not used carefully. You should review all outputs generated by the agent thoroughly.\n- **Public code matches (CLI)**: Copilot CLI may generate code that is a match or near match of publicly available code, even if the \"Suggestions matching public code\" policy is set to \"Block.\"\n- **Command execution risks (CLI)**: Additional caution is required when asking or allowing Copilot CLI to execute a command, particularly regarding the potential destructiveness of some suggested commands. You may encounter commands for file deletion or hard drive formatting, which can cause problems if used incorrectly. You are ultimately responsible for the commands executed by Copilot CLI.\n- **Interface interpretation (computer use)**: Computer use may select the wrong control, enter text in the wrong location, or have difficulty with non-standard or dynamic controls and complex workflows. Changes in timing or window state can produce different results, cause computer use to repeat an action, or prevent it from continuing.",
      "content_chars": 24954,
      "published_date": "2026-10-06"
    }
  ],
  "answer_text": null,
  "citations": [],
  "raw_response": {
    "success": true,
    "error": "",
    "tx_id": "tx_5d6428ba-d0a6-407f-b614-2a5b7faca881",
    "query": "In what year did GitHub first launch a technical preview of GitHub Copilot?",
    "results": [
      {
        "title": "About GitHub Copilot - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/get-started/github-copilot-features",
        "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
        "description": "Understand how GitHub Copilot helps you ship software faster, how it works, and how to get access.",
        "source": "web",
        "price": 0.0015,
        "length": 6665,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/get-started/github-copilot-features",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6242638386497864
      },
      {
        "title": "About GitHub Copilot - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/overview-of-github-copilot/about-github-copilot",
        "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
        "description": "Understand how GitHub Copilot helps you ship software faster, how it works, and how to get access.",
        "source": "web",
        "price": 0.0015,
        "length": 6665,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2022-06-21",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/overview-of-github-copilot/about-github-copilot",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6242638386497864
      },
      {
        "title": "About GitHub Copilot - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/get-started/about-github-copilot",
        "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
        "description": "Understand how GitHub Copilot helps you ship software faster, how it works, and how to get access.",
        "source": "web",
        "price": 0.0015,
        "length": 6665,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/get-started/about-github-copilot",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6242638386497864
      },
      {
        "title": "About GitHub Copilot - GitHub Enterprise Cloud Docs",
        "url": "https://docs.github.com/en/enterprise-cloud@latest/copilot/about-github-copilot/github-copilot-features",
        "content": "In this article\n\n# About GitHub Copilot\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot is an AI assistant that helps you write, understand, and ship software. It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.\n\nBecause Copilot is built into GitHub, it works within the development workflow you already use:\n\n- Your code and its history.\n- The issues and pull requests you already use to track work.\n- The automations you run in your repository.\n\nA change can start as an issue, be picked up by an agent, return as a pull request, get reviewed for quality and security, and be merged.\n\nYou and Copilot work on it in the same place, with the same context, instead of moving code into separate tools and back again.\n\n## How Copilot works\n\nCopilot's capabilities and supporting features fall into four categories:\n\n**Assistive.** Copilot responds while you work, suggesting code, answering questions, or explaining code. You review and apply each suggestion.\n\n**Agentic.** You describe a goal, and Copilot can work through multiple steps. It researches a repository, proposes a plan, edits files, reviews pull requests, runs tools, and prepares tasks for your review. You remain responsible for reviewing and approving.\n\n**Customizations.** You customize Copilot's responses with instructions, reusable prompts, repository context, external tools, agent skills, and custom agents. When Copilot understands your project's structure, conventions, and tooling, it gives you better responses.\n\n**External AI agents, models, and tools.** Coding agents, models, and tools, including MCP servers from other providers, work alongside Copilot. Third-party coding agents work asynchronously on development tasks and can make changes and open or update pull requests for your review. They are subject to the same security protections, mitigations, and limitations as Copilot.\n\n## What you can do with Copilot\n\nCopilot helps you throughout the software development lifecycle. For example:\n\n- **Understand code** by asking questions about files, repositories, and development concepts.\n- **Plan and implement tasks** with an agent that can research a repository, make changes, and prepare a pull request for your review.\n- **Customize responses** with instructions, reusable prompts, repository context, tools, and specialized agents.\n- **Write code** with inline suggestions and natural-language prompts.\n- **Build applications** from natural-language descriptions.\n- **Change code** by asking Copilot to edit, refactor, or fix code.\n- **Review code** and pull requests, including summaries and suggestions for potential improvements.\n\nThe capabilities available to you depend on your Copilot plan, the client you use, and your organization's policies.\n\n## Get access\n\nYou can start using Copilot in several ways, depending on your role and needs.\n\n### Individuals\n\n- **Try Copilot for free.** Use [Copilot Free](https://github.com/copilot?ref_product=copilot&ref_plan=free&ref_style=text&ref_type=engagement) to explore core features with no paid plan required.\n- **Subscribe to a paid plan.** Upgrade to a paid plan for access to premium features, increased access to models, and a higher monthly allowance of AI credits. See [Getting started with a GitHub Copilot plan](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/manage-your-account/get-started-with-a-copilot-plan) for more information.\n- **Get free access if you're eligible.** Students, teachers, and open source maintainers may qualify for access to premium features at no cost. See [Access GitHub Copilot for free as a student](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-students) and [Access Copilot Pro for free as a teacher or open source maintainer](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-teachers-and-os-maintainers).\n\n### Members of an organization\n\n- **Request access from your organization.** If your organization or enterprise has a GitHub Copilot plan, go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n### Organization and enterprise owners\n\nOwners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).\n\nIf your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to [https://github.com/settings/copilot](https://github.com/settings/copilot) and request access under \"Get Copilot from an organization.\"\n\n**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.\n\n- If you want to pay by credit card or PayPal, [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).\nIf you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.\n- For other payment methods, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).\n\nIf you are on **GitHub Enterprise Server**, see [About GitHub Copilot on GitHub Enterprise Server](https://docs.github.com/en/enterprise-server@3.22/copilot/copilot-on-ghes/about-copilot-on-ghes).\n\n## Control for organizations and enterprises\n\nIf you use Copilot through an organization or enterprise, administrators decide how it can be used. They control which members have access, set policies for which features are available, exclude files that Copilot shouldn't see, and review usage data and audit logs to understand how it's being used.\n\nThese settings help administrators manage Copilot across the environments and features available to their organization or enterprise. Some settings and controls depend on the Copilot plan and the client where Copilot is used. See [Administer GitHub Copilot for your team](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot).\n\n## Next steps\n\n- Start using Copilot. See [Where to use GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/where-to-use-github-copilot).\n- View the Copilot features available to you by navigating to your Copilot settings at [https://github.com/settings/copilot/features](https://github.com/settings/copilot/features?ref_product=copilot&ref_type=engagement&ref_style=text).",
        "description": "Understand how GitHub Copilot helps you ship software faster, how it works, and how to get access.",
        "source": "web",
        "price": 0.0015,
        "length": 6785,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/enterprise-cloud@latest/copilot/about-github-copilot/github-copilot-features",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6221456992893811
      },
      {
        "title": "Exploring early access releases with feature preview - GitHub Docs",
        "url": "https://docs.github.com/en/get-started/using-github/exploring-early-access-releases-with-feature-preview",
        "content": "In this article\n\n# Exploring early access releases with feature preview\n\nCopy markdown\n\n## In this article\n\n## GitHub's release cycle\n\nGitHub's products and features can go through multiple release phases.\n\n| Phase | Description |\n| --- | --- |\n| Private preview | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. Private preview releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. **Note:** A product or feature released as a \"Technology Preview\" is considered to be in the private preview release stage. Technology Preview releases share the same characteristics of private preview releases as described above. |\n| Public preview | The product or feature is ready for broader distribution. Public preview releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |\n| General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. |\n\n## Exploring public preview releases with feature preview\n\nYou can see a list of features that are available in public preview and a brief description for each feature. Each feature includes a link to give feedback.\n\n1. In the upper-right corner of any page, click your profile picture, then click **Feature preview**.\n2. To view details for a feature, in the left sidebar, click the feature's name.\n3. Optionally, to the right of a feature's name, click **Enable** or **Disable**.",
        "description": "You can use feature preview to see products or features that are available in public preview and to enable or disable each feature for your personal account.",
        "source": "web",
        "price": 0.0015,
        "length": 1734,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2022-11-09",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/get-started/using-github/exploring-early-access-releases-with-feature-preview",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/get-started.png"
        },
        "relevance_score": 0.6177300618192776
      },
      {
        "title": "GitHub Copilot on GitHub.com - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent",
        "content": "In this article\n\n# GitHub Copilot on GitHub.com\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot on GitHub.com can answer questions about your repositories, plan and make changes, review pull requests, and automate repository tasks. You can ask questions and delegate work from the same prompt box, or use Copilot directly in your issue and pull request workflows.\n\nTo compare where you can use Copilot, see [Where to use GitHub Copilot](https://docs.github.com/en/copilot/get-started/where-to-use-github-copilot).\n\n## How Copilot helps on GitHub.com\n\nYou can work with Copilot in several ways:\n\n- **Chat** lets you ask questions about your repositories, understand code, and explore possible solutions.\n- **Agentic experiences** can research a repository, plan changes, and complete multi-step tasks by reading files, editing code, and running tests in a cloud development environment.\n- **Code review** provides feedback on pull requests and suggests fixes.\n- **Automations** run repository tasks on a schedule or in response to events, rather than requiring a new prompt each time.\n\nFor example, you might use chat to understand how a repository handles authentication, then ask an agent to plan and add missing tests. Once the changes are in a pull request, you can request a review from Copilot. To maintain test coverage over time, you could set up an automation to check for missing tests each week and propose additions for you to review.\n\n## Chat and agentic experiences\n\nOn GitHub.com, you can move from asking questions to delegating work in the same conversation.\n\n### Asking questions\n\nChat can explain unfamiliar code, suggest fixes, generate tests, or compare approaches. Follow-up questions let you refine your request without starting a new conversation.\n\nChat is preconfigured with tools for tasks such as creating branches, updating files, and creating or updating issues. It also supports semantic code search.\n\n### Delegating work\n\nCopilot cloud agent can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in an ephemeral cloud development environment, rather than your local IDE. See [GitHub Copilot in IDEs](https://docs.github.com/en/copilot/concepts/copilot-surfaces/copilot-in-ides).\n\nYou can start work from the agents panel, a conversation, or an issue or pull request on GitHub.com.\n\nFrom security campaigns, you can assign code scanning alerts to Copilot for fixes. See [Fixing alerts in a security campaign](https://docs.github.com/en/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/fixing-alerts-in-security-campaign#assigning-alerts-to-copilot-cloud-agent).\n\nWhen implementing changes, Copilot handles branch creation, commit messages, and pushing changes. You can review changes and request refinements before creating a pull request, or request a pull request in your initial prompt. You can also continue the work yourself. See [Research, plan, and iterate on code changes with Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/research-plan-iterate).\n\n### Session context\n\nOn GitHub.com, Copilot Chat and Copilot cloud agent can share context. When you start an agent session from a chat, the session incorporates the context of your conversation. While the session runs, you can continue chatting with Copilot about its progress and steer the work.\n\nCopilot Chat can also answer questions about pull requests created by Copilot by pulling in the relevant agent session logs. You can ask what changed, what was validated, and why, without leaving the conversation.\n\nThis context passing is scoped to the Copilot Chat and cloud agent sessions you are actively working with. It is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see [About GitHub Copilot Memory](https://docs.github.com/en/copilot/concepts/agents/copilot-memory).\n\nOn GitHub.com, session logs show the work and tools used. Shared sessions and pull requests let teammates with repository access follow the work and review changes. Logs do not replace your own review and testing. See [Managing agent sessions](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).\n\n### Sessions across surfaces\n\nWith remote control enabled, you can monitor and steer a GitHub Copilot CLI session from GitHub.com. It continues running on your original machine, which must stay online. See [About remote control of GitHub Copilot CLI sessions](https://docs.github.com/en/copilot/concepts/agents/copilot-cli/about-remote-control).\n\nOn GitHub.com, you can ask about your synced session history across Copilot surfaces. This includes Copilot cloud agent and Copilot code review sessions, and sessions from GitHub Copilot CLI, VS Code, JetBrains IDEs, and the GitHub Copilot app.\n\nYou can only query sessions you started. Syncing must be enabled and permitted by your organization's policies. See [Query past sessions](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents#query-past-sessions).\n\n## Code review\n\nOn GitHub.com, Copilot code review reviews pull request changes, identifies potential issues, and suggests fixes. It uses agentic capabilities to gather context from your repository. You can request a review or configure automatic reviews, then review and apply the suggested changes. See [About GitHub Copilot code review](https://docs.github.com/en/copilot/concepts/agents/code-review).\n\nCopilot can also generate a summary of your changes directly in a pull request description or comment. This helps reviewers understand the changes, but is separate from reviewing the code. See [Creating a pull request summary with GitHub Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/copilot-for-github-tasks/create-a-pr-summary).\n\n## Automations and agentic workflows\n\nAutomations let you define a task once and have Copilot cloud agent run it on a schedule or in response to repository events. For example, an automation can triage incoming issues or prepare weekly release notes. You create and manage automations from the **Agents** tab in a repository on GitHub.com. Automations are available in eligible private and internal repositories. See [About Copilot automations](https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-automations).\n\nGitHub Agentic Workflows provide another way to automate tasks in your repositories on GitHub.com. You define tasks in natural language in Markdown files, and they run as GitHub Actions workflows. These workflows can use Copilot or another supported coding agent. See [About GitHub Agentic Workflows](https://docs.github.com/en/copilot/concepts/agents/about-github-agentic-workflows).\n\n## Customizations\n\nOn GitHub.com, custom instructions let you save personal preferences for chat, repository conventions, and organization guidance. Copilot Spaces organize shared context for questions. For delegated work, custom agents and agent skills provide task-specific instructions and resources. Model Context Protocol (MCP) servers connect agents to additional tools and data. Hooks can run commands during agent work for validation or logging. For setup guidance, see [Customize Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot).\n\n## AI models\n\nYou can change the model Copilot uses to generate responses. You may find that different models perform better, or provide more useful responses, depending on the type of questions you ask. Options include premium models with advanced capabilities. To change the model in your IDE, see [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/chat-with-copilot/change-the-chat-model). To change or compare models on GitHub, see [Asking GitHub Copilot questions in GitHub](https://docs.github.com/en/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github#changing-and-comparing-ai-models).\n\nOn GitHub.com, available models depend on your plan and account policies. See [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models).\n\nFor Copilot cloud agent, the ability to select a model also depends on how you start the task. See [Changing the AI model for GitHub Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).\n\n## References to matching public code\n\nIn chat responses and agent sessions on GitHub.com, Copilot can generate code that matches code in public repositories. Code references help you review the matching code and its licensing information so you can decide whether to use it, provide attribution, or remove it.\n\nMatches appear in the context where you are reviewing the output:\n\n- **Chat responses**: If you or your organization allow suggestions matching public code, matching code in a response includes a reference beneath the suggestion. The reference identifies public repositories containing matching code and licensing information, if found.\n- **Agent session logs**: When Copilot generates matching code during a delegated task, the session logs include a link to details of the matched code.\n\nMatches occur infrequently, so most responses do not contain code references. The search covers an index of public repositories on GitHub.com, not private repositories or code hosted elsewhere. The index is refreshed periodically, so it may omit recently added code or refer to code that has since moved or been deleted.\n\nFor instructions on viewing references, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/copilot/how-tos/get-code-suggestions/find-matching-code?tool=webui).\n\n## Access and availability\n\nAvailable features depend on your plan and organization policies. For setup guidance, see [Set up Copilot](https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot). For usage allowances and costs, see [GitHub Copilot billing and usage](https://docs.github.com/en/copilot/concepts/billing-and-usage).\n\nRepository owners and administrators can disable Copilot cloud agent for particular repositories, even when your plan and policies otherwise allow you to use it. See [Managing access to GitHub Copilot cloud agent](https://docs.github.com/en/copilot/concepts/enterprise/cloud-agent-access).\n\n## Limitations and compatibility\n\nBoth chat and agentic experiences on GitHub.com can produce incorrect or suboptimal code, including code that contains security vulnerabilities. Review and test the output before using it in production. See [Application card: GitHub Copilot Agents](https://docs.github.com/en/copilot/responsible-use/agents).\n\nFor information about built-in security protections, see [Risks and mitigations for GitHub Copilot cloud agent](https://docs.github.com/en/copilot/concepts/agents/cloud-agent/risks-and-mitigations).\n\n### Agentic work\n\nCopilot cloud agent has the following workflow limitations:\n\n- **Repository scope**: Copilot can only make changes in the repository specified when you start a task. It cannot make changes across multiple repositories in one run.\n- **Context access**: By default, the GitHub MCP server only provides access to context in the repository where the agent is working, such as issues and previous pull requests. You can configure broader access through repository MCP settings. See [Configure MCP servers for your repository](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers).\n- **Branches and pull requests**: Copilot can only work on one branch at a time and can open one pull request per task.\n- **Session duration**: Each Copilot cloud agent session has a maximum execution time of 59 minutes. This limit cannot be extended or bypassed. If a task exceeds the limit, the session times out and stops.\nBreak complex tasks into smaller, focused tasks. You can configure a shorter timeout using the `timeout-minutes` setting in your `copilot-setup-steps.yml` file. See [Configure the development environment](https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment).\n\n### Repository compatibility\n\n- **Repository rules**: If a ruleset or branch protection rule is incompatible with Copilot cloud agent, access to the agent is blocked. For example, a rule that only allows specific commit authors can prevent Copilot from creating or updating pull requests. If the rule is configured using rulesets, repository administrators can add Copilot as a bypass actor to enable access. See [Creating rulesets for a repository](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-branch-or-tag-ruleset).\n- **Repository hosting**: Copilot cloud agent only works with repositories hosted on GitHub. It cannot work on repositories stored on other code hosting platforms.\n\n## Further reading\n\n- [GitHub Copilot on GitHub](https://docs.github.com/en/copilot/how-tos/copilot-on-github)\n- [GitHub Copilot cloud agent](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent) how-to guides\n- [GitHub Copilot Cookbook](https://docs.github.com/en/copilot/tutorials/copilot-cookbook)\n- For delegating work from tools such as Microsoft Teams and Slack, see [About Copilot integrations](https://docs.github.com/en/copilot/concepts/tools/about-copilot-integrations).\n- For organization and enterprise metrics on pull request creation, merges, and time to merge, see [GitHub Copilot usage metrics](https://docs.github.com/en/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics).",
        "description": "Explore your repositories, plan changes, and delegate coding tasks to GitHub Copilot without leaving GitHub.com.",
        "source": "web",
        "price": 0.0015,
        "length": 13978,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6154346832138401
      },
      {
        "title": "GitHub Copilot on GitHub.com - GitHub Enterprise Cloud Docs",
        "url": "https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/about-cloud-agent",
        "content": "In this article\n\n# GitHub Copilot on GitHub.com\n\nCopy markdown\n\n## In this article\n\nGitHub Copilot on GitHub.com can answer questions about your repositories, plan and make changes, review pull requests, and automate repository tasks. You can ask questions and delegate work from the same prompt box, or use Copilot directly in your issue and pull request workflows.\n\nTo compare where you can use Copilot, see [Where to use GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/where-to-use-github-copilot).\n\n## How Copilot helps on GitHub.com\n\nYou can work with Copilot in several ways:\n\n- **Chat** lets you ask questions about your repositories, understand code, and explore possible solutions.\n- **Agentic experiences** can research a repository, plan changes, and complete multi-step tasks by reading files, editing code, and running tests in a cloud development environment.\n- **Code review** provides feedback on pull requests and suggests fixes.\n- **Automations** run repository tasks on a schedule or in response to events, rather than requiring a new prompt each time.\n\nFor example, you might use chat to understand how a repository handles authentication, then ask an agent to plan and add missing tests. Once the changes are in a pull request, you can request a review from Copilot. To maintain test coverage over time, you could set up an automation to check for missing tests each week and propose additions for you to review.\n\n## Chat and agentic experiences\n\nOn GitHub.com, you can move from asking questions to delegating work in the same conversation.\n\n### Asking questions\n\nChat can explain unfamiliar code, suggest fixes, generate tests, or compare approaches. Follow-up questions let you refine your request without starting a new conversation.\n\nChat is preconfigured with tools for tasks such as creating branches, updating files, and creating or updating issues. It also supports semantic code search.\n\n### Delegating work\n\nCopilot cloud agent can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in an ephemeral cloud development environment, rather than your local IDE. See [GitHub Copilot in IDEs](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/copilot-surfaces/copilot-in-ides).\n\nYou can start work from the agents panel, a conversation, or an issue or pull request on GitHub.com.\n\nFrom security campaigns, you can assign code scanning alerts to Copilot for fixes. See [Fixing alerts in a security campaign](https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/fixing-alerts-in-security-campaign#assigning-alerts-to-copilot-cloud-agent).\n\nWhen implementing changes, Copilot handles branch creation, commit messages, and pushing changes. You can review changes and request refinements before creating a pull request, or request a pull request in your initial prompt. You can also continue the work yourself. See [Research, plan, and iterate on code changes with Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/research-plan-iterate).\n\n### Session context\n\nOn GitHub.com, Copilot Chat and Copilot cloud agent can share context. When you start an agent session from a chat, the session incorporates the context of your conversation. While the session runs, you can continue chatting with Copilot about its progress and steer the work.\n\nCopilot Chat can also answer questions about pull requests created by Copilot by pulling in the relevant agent session logs. You can ask what changed, what was validated, and why, without leaving the conversation.\n\nThis context passing is scoped to the Copilot Chat and cloud agent sessions you are actively working with. It is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see [About GitHub Copilot Memory](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/copilot-memory).\n\nOn GitHub.com, session logs show the work and tools used. Shared sessions and pull requests let teammates with repository access follow the work and review changes. Logs do not replace your own review and testing. See [Managing agent sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).\n\n### Sessions across surfaces\n\nWith remote control enabled, you can monitor and steer a GitHub Copilot CLI session from GitHub.com. It continues running on your original machine, which must stay online. See [About remote control of GitHub Copilot CLI sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/copilot-cli/about-remote-control).\n\nOn GitHub.com, you can ask about your synced session history across Copilot surfaces. This includes Copilot cloud agent and Copilot code review sessions, and sessions from GitHub Copilot CLI, VS Code, JetBrains IDEs, and the GitHub Copilot app.\n\nYou can only query sessions you started. Syncing must be enabled and permitted by your organization's policies. See [Query past sessions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents#query-past-sessions).\n\n## Code review\n\nOn GitHub.com, Copilot code review reviews pull request changes, identifies potential issues, and suggests fixes. It uses agentic capabilities to gather context from your repository. You can request a review or configure automatic reviews, then review and apply the suggested changes. See [About GitHub Copilot code review](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/code-review).\n\nCopilot can also generate a summary of your changes directly in a pull request description or comment. This helps reviewers understand the changes, but is separate from reviewing the code. See [Creating a pull request summary with GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/copilot-for-github-tasks/create-a-pr-summary).\n\n## Automations and agentic workflows\n\nAutomations let you define a task once and have Copilot cloud agent run it on a schedule or in response to repository events. For example, an automation can triage incoming issues or prepare weekly release notes. You create and manage automations from the **Agents** tab in a repository on GitHub.com. Automations are available in eligible private and internal repositories. See [About Copilot automations](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/about-automations).\n\nGitHub Agentic Workflows provide another way to automate tasks in your repositories on GitHub.com. You define tasks in natural language in Markdown files, and they run as GitHub Actions workflows. These workflows can use Copilot or another supported coding agent. See [About GitHub Agentic Workflows](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/about-github-agentic-workflows).\n\n## Customizations\n\nOn GitHub.com, custom instructions let you save personal preferences for chat, repository conventions, and organization guidance. Copilot Spaces organize shared context for questions. For delegated work, custom agents and agent skills provide task-specific instructions and resources. Model Context Protocol (MCP) servers connect agents to additional tools and data. Hooks can run commands during agent work for validation or logging. For setup guidance, see [Customize Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot).\n\n## AI models\n\nYou can change the model Copilot uses to generate responses. You may find that different models perform better, or provide more useful responses, depending on the type of questions you ask. Options include premium models with advanced capabilities. To change the model in your IDE, see [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-in-your-ide/chat-with-copilot/change-the-chat-model). To change or compare models on GitHub, see [Asking GitHub Copilot questions in GitHub](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-github#changing-and-comparing-ai-models).\n\nOn GitHub.com, available models depend on your plan and account policies. See [Supported AI models in GitHub Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/reference/ai-models/supported-models).\n\nFor Copilot cloud agent, the ability to select a model also depends on how you start the task. See [Changing the AI model for GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).\n\n## References to matching public code\n\nIn chat responses and agent sessions on GitHub.com, Copilot can generate code that matches code in public repositories. Code references help you review the matching code and its licensing information so you can decide whether to use it, provide attribution, or remove it.\n\nMatches appear in the context where you are reviewing the output:\n\n- **Chat responses**: If you or your organization allow suggestions matching public code, matching code in a response includes a reference beneath the suggestion. The reference identifies public repositories containing matching code and licensing information, if found.\n- **Agent session logs**: When Copilot generates matching code during a delegated task, the session logs include a link to details of the matched code.\n\nMatches occur infrequently, so most responses do not contain code references. The search covers an index of public repositories on GitHub.com, not private repositories or code hosted elsewhere. The index is refreshed periodically, so it may omit recently added code or refer to code that has since moved or been deleted.\n\nFor instructions on viewing references, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/get-code-suggestions/find-matching-code?tool=webui).\n\n## Access and availability\n\nAvailable features depend on your plan and organization policies. For setup guidance, see [Set up Copilot](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/set-up-copilot). For usage allowances and costs, see [GitHub Copilot billing and usage](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing-and-usage).\n\nRepository owners and administrators can disable Copilot cloud agent for particular repositories, even when your plan and policies otherwise allow you to use it. See [Managing access to GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/enterprise/cloud-agent-access).\n\n## Limitations and compatibility\n\nBoth chat and agentic experiences on GitHub.com can produce incorrect or suboptimal code, including code that contains security vulnerabilities. Review and test the output before using it in production. See [Application card: GitHub Copilot Agents](https://docs.github.com/en/enterprise-cloud@latest/copilot/responsible-use/agents).\n\nFor information about built-in security protections, see [Risks and mitigations for GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/risks-and-mitigations).\n\n### Agentic work\n\nCopilot cloud agent has the following workflow limitations:\n\n- **Repository scope**: Copilot can only make changes in the repository specified when you start a task. It cannot make changes across multiple repositories in one run.\n- **Context access**: By default, the GitHub MCP server only provides access to context in the repository where the agent is working, such as issues and previous pull requests. You can configure broader access through repository MCP settings. See [Configure MCP servers for your repository](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers).\n- **Branches and pull requests**: Copilot can only work on one branch at a time and can open one pull request per task.\n- **Session duration**: Each Copilot cloud agent session has a maximum execution time of 59 minutes. This limit cannot be extended or bypassed. If a task exceeds the limit, the session times out and stops.\nBreak complex tasks into smaller, focused tasks. You can configure a shorter timeout using the `timeout-minutes` setting in your `copilot-setup-steps.yml` file. See [Configure the development environment](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment).\n\n### Repository compatibility\n\n- **Repository rules**: If a ruleset or branch protection rule is incompatible with Copilot cloud agent, access to the agent is blocked. For example, a rule that only allows specific commit authors can prevent Copilot from creating or updating pull requests. If the rule is configured using rulesets, repository administrators can add Copilot as a bypass actor to enable access. See [Creating rulesets for a repository](https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-branch-or-tag-ruleset).\n- **Repository hosting**: Copilot cloud agent only works with repositories hosted on GitHub. It cannot work on repositories stored on other code hosting platforms.\n\n## Further reading\n\n- [GitHub Copilot on GitHub](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/copilot-on-github)\n- [GitHub Copilot cloud agent](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/cloud-agent) how-to guides\n- [GitHub Copilot Cookbook](https://docs.github.com/en/enterprise-cloud@latest/copilot/tutorials/copilot-cookbook)\n- For delegating work from tools such as Microsoft Teams and Slack, see [About Copilot integrations](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/tools/about-copilot-integrations).\n- For organization and enterprise metrics on pull request creation, merges, and time to merge, see [GitHub Copilot usage metrics](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics).",
        "description": "Explore your repositories, plan changes, and delegate coding tasks to GitHub Copilot without leaving GitHub.com.",
        "source": "web",
        "price": 0.0015,
        "length": 14722,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/agents/cloud-agent/about-cloud-agent",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6129033228420454
      },
      {
        "title": "Application card: GitHub Copilot Chat - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/github-copilot-chat/about-github-copilot-chat",
        "content": "In this article\n\n# Application card: GitHub Copilot Chat\n\nCopy markdown\n\n## In this article\n\n## What is an Application Card?\n\nGitHub\u2019s application and platform cards are intended to help you understand how our AI technology works, the choices application owners can make that influence application performance and behavior, and the importance of considering the whole application, including the technology, the people, and the environment. Application cards are created for AI applications and platform cards are created for AI platform services. These resources can support the development or deployment of your own applications and can be shared with users or stakeholders impacted by them.\n\nAs part of its commitment to responsible AI, GitHub adheres to Microsoft's [six core principles](https://www.microsoft.com/en-us/ai/principles-and-approach/?msockid=3da790040c776d6f2b5485e40de56c06#ai-principles): fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability. These principles are embedded in the [Responsible AI Standard](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/final/en-us/microsoft-brand/documents/Microsoft-Responsible-AI-Standard-General-Requirements.pdf?culture=en-us&country=us), which guides teams in designing, building, and testing AI applications. Application and Platform Cards play a key role in operationalizing these principles by offering transparency around capabilities, intended uses, and limitations. For further insight, readers are encouraged to explore Microsoft\u2019s [Responsible AI Transparency Report](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/msc/documents/presentations/CSR/Responsible-AI-Transparency-Report-2025-vertical.pdf) and [GitHub Terms](https://docs.github.com/en/site-policy/github-terms).\n\n## 1. Overview\n\nGitHub Copilot Chat is a chat interface that lets you interact with GitHub Copilot to ask and receive answers to coding-related questions. GitHub Copilot Chat is available on GitHub.com, in supported IDEs (VS Code, Visual Studio, JetBrains, and Eclipse), on GitHub Mobile, and in Windows Terminal. On GitHub.com and in GitHub Desktop, Copilot can also generate pull request summaries and commit messages\u2014AI-powered overviews of changes made in a pull request or commit.\n\nGitHub Copilot Chat can answer a wide range of coding-related questions on topics including syntax, programming concepts, test cases, debugging, and more. GitHub Copilot Chat is not designed to answer non-coding questions or provide general information on topics outside of coding.\n\nThe primary supported language for GitHub Copilot Chat is English.\n\n## 2. Key terms\n\nThe following list provides a glossary of key terms related to GitHub Copilot Chat:\n\n- **Content filtering**: A safety system that scans prompts and responses to detect and block harmful content before it is shown to the user.\n- **Hallucination**: A phenomenon where a language model generates output that sounds plausible but is factually incorrect, unsupported by the provided context, or entirely fabricated. Hallucinations are a known risk of large language models and are reason that human review of AI-generated output is important.\n- **Large language model (LLM)**: A type of neural network trained on a large body of text data that can generate, analyze, and transform natural language and code. GitHub Copilot Chat uses one or more LLMs to process prompts and produce responses.\n- **Prompt**: The input that is provided to GitHub Copilot Chat. The system combines the prompt with additional context (for example, open files or repository data) before sending it to the language model.\n- **Public code matching**: A feature that checks whether Copilot's suggestions match publicly available code. Depending on your settings, matching suggestions may be turned off or on; if turned on, it can either block or annotate with a reference to the source repository and any license information.\n- **Pull request summary**: An AI-generated overview of the changes in a pull request, consisting of a prose paragraph and a bulleted list of key changes linked to the affected files. Summaries are generated on demand on GitHub.com.\n- **Red teaming**: A structured testing practice in which testers deliberately attempt to provoke unsafe, harmful, or unintended behavior from an AI system. Red teaming helps identify vulnerabilities and improve safety mitigations before and after release.\n- **Training data**: The large body of publicly available text and code that was used to train the foundation models behind GitHub Copilot Chat. The composition of the training data influences the quality and coverage of the model's suggestions across different programming languages, frameworks, and topics.\n\n## 3. Key features or capabilities\n\nThe key features and capabilities outlined here describe what GitHub Copilot Chat is designed to do and how it performs across supported tasks.\n\n- **Conversational coding assistance**: GitHub Copilot Chat provides a natural language interface for asking coding-related questions and receiving answers in the form of code, explanations, or step-by-step guidance. Users can ask follow-up questions to refine responses, and the conversation history is maintained within a session.\n- **Context-aware responses**: GitHub Copilot Chat uses contextual information\u2014such as open files, the active repository, chat history, and (when enabled) web search results\u2014to generate responses that are relevant to the user's current work. The specific context available depends on the platform (GitHub.com, IDE, Mobile, Windows Terminal, or GitHub Desktop).\n- **Multi-platform availability**: GitHub Copilot Chat is available across multiple surfaces, including GitHub.com, supported IDEs (VS Code, Visual Studio, JetBrains, and Eclipse), GitHub Mobile, Windows Terminal, and GitHub Desktop. Each platform offers a tailored experience optimized for its environment.\n- **Agent mode**: In supported IDEs, GitHub Copilot Chat can operate in agent mode, where the model autonomously plans multi-step tasks, invokes tools (such as running terminal commands or editing files), and iterates on results. This extends the chat experience beyond single-turn question-and-answer interactions.\n- **Copilot Spaces**: Spaces let users organize repositories, files, issues, and other materials into a curated collection of context. When a question is asked inside a space, Copilot uses the included context to produce more targeted and relevant responses. Spaces can also be accessed from the IDE via the remote GitHub MCP server.\n- **Pull request summaries**: On GitHub.com, Copilot can generate an AI-powered summary of the changes in a pull request. The output consists of a prose overview followed by a bulleted list of key changes linked to the affected files. Summaries are generated on demand and are intended to help reviewers quickly understand what changed.\n- **Commit message generation**: On GitHub.com and in GitHub Desktop, Copilot can generate a suggested commit summary (title) and description based on the code changes you have selected. In GitHub Desktop, users can select specific lines of code or files to improve context and accuracy. Generated messages can be reviewed and edited before committing.\n- **Bring Your Own Key (BYOK)**: Organizations can connect GitHub Copilot Chat to large language models from supported third-party providers by supplying their own API key, rather than using the default GitHub-hosted model.\n- **Content filtering**: At times, GitHub Copilot Chat may include a content filtering system that scans prompts and responses to detect and block harmful content. A public code matching feature checks whether suggestions match publicly available code and, depending on settings, blocks or annotates those matches with source and license information.\n\n## 4. Intended uses\n\nGitHub Copilot Chat can be used in multiple scenarios across a variety of industries. Some examples of use cases include:\n\n- **Answering coding questions**: Ask GitHub Copilot Chat for help or clarification on specific coding problems and receive responses in natural language or code snippet format. The response may draw on the model's training data, repository context, and web search results (when enabled).\n- **Explaining code and suggesting improvements**: Generate natural language descriptions of a function's purpose, inputs, outputs, and dependencies. GitHub Copilot Chat can also suggest improvements such as better error handling or more readable control flow. Note that generated explanations may not always be accurate or complete and should be reviewed.\n- **Generating unit test cases**: GitHub Copilot Chat can help write unit test cases by generating code snippets based on the code open in the editor or a highlighted code snippet. It can suggest possible input parameters, expected output values, and assertions based on the function's signature and body. GitHub Copilot Chat can also suggest test cases for edge cases and boundary conditions\u2014such as error handling, null values, or unexpected input types\u2014that might be difficult to identify manually. Generated test cases may not cover all possible scenarios; manual testing and code review are still necessary.\n- **Proposing code fixes**: Get suggested fixes for bugs based on the error message, code syntax, and surrounding context. GitHub Copilot Chat can suggest changes to variables, control structures, or function calls that might resolve the issue. Note that suggested fixes may not always be optimal or complete.\n- **Planning coding tasks**: Read and summarize GitHub issues, answer questions about them, or propose next steps.\n- **Learning about releases, discussions, and commits**: Summarize what changed in a release, the gist of a discussion, or the changes in a specific commit.\n- **Summarizing pull request changes (GitHub.com)**: Generate an AI-powered summary of the changes in a pull request\u2014including a prose overview and a bulleted list of key changes linked to the affected files\u2014to help reviewers quickly understand what changed and where to focus their review.\n- **Generating commit messages (GitHub.com and GitHub Desktop)**: Generate a commit message summary (title) and description based on the code changes you've selected to commit, helping you save time and maintain clear commit histories. In GitHub Desktop, you can select specific lines of code or files for better context understanding to increase accuracy. You can review and edit the suggested title and description before committing.\n- **Finding the right command (Windows Terminal)**: Ask Copilot to suggest commands that help you perform tasks in the command line. You can revise your question until the returned command meets your expectations, then insert it into your command line to run it.\n- **Explaining an unfamiliar command (Windows Terminal)**: Ask Copilot to generate a natural language description of a command's functionality, including its input and output parameters and usage examples. Note that generated explanations may not always be accurate or complete.\n- **Developing a new feature (Spaces)**: Bundle relevant code, product specs, and design notes in a space so Copilot can explain the current implementation, highlight gaps, and draft new code or next steps.\n- **Defining logic for repeated tasks (Spaces)**: Document a process once\u2014with flowcharts, examples, or schemas\u2014and reuse it across your team for consistent patterns and reusable templates.\n- **Sharing knowledge with teammates (Spaces)**: Collect the latest code and documentation in one place so Copilot can explain systems, answer questions, and onboard teammates.\n\n## 5. Models and training data\n\nGitHub Copilot Chat leverages a variety of AI models to power the experience that users see. For a comparison of the models available for Copilot, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison). For the full list of supported models, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models). For information on where models are hosted, see [Hosting of models for GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/model-hosting). To learn more about the data used to train the foundation models behind GitHub Copilot Chat, refer to the linked AI model comparison above and [What data has GitHub Copilot been trained on?](https://github.com/features/copilot#faq) in the GitHub Copilot FAQ.\n\n### Using Bring Your Own Key (BYOK)\n\nWhen you use Bring Your Own Key with GitHub Copilot Chat, you can connect the chat experience to large language models from supported providers beyond the default Copilot model. Examples of supported providers include Anthropic, AWS Bedrock, Google AI Studio, Microsoft Foundry, OpenAI, OpenAI-compatible providers, and xAI. You add your API key for the chosen provider directly in your Copilot settings.\n\nWhen BYOK is active:\n\n- **Feature scope**: Your chosen model is used within GitHub Copilot Chat. In Agent mode, BYOK powers the main conversation, but certain actions such as code application or other tool calls may still use Copilot-integrated models optimized for those tasks. These built-in models do not run through your BYOK provider.\n- **Content filtering**: Regardless of which provider is active, responses still pass through GitHub's API and may have content filtering before results are shown to you.\n- **Quality considerations**: Suggestions may vary depending on the strengths and training coverage of your chosen provider.\n- **Data handling**: When using BYOK, your prompts and responses are transmitted to your selected provider and may be subject to that provider's data retention and privacy policies.\n- **Your responsibilities**: You are responsible for the following:\n - Provider API key security\n- Usage costs or quotas\n- Output validation\n- Evaluating whether your chosen model meets your safety and quality requirements\n- Compliance with your selected provider's terms\n- Determining whether your chosen model complies with applicable laws\n- Ensuring that a human reviews any output before using it to make decisions that affect people\n- **Export restrictions**: Certain AI models may be subject to export controls. Verify your selected provider and model are authorized for use in your jurisdiction.\n\nBYOK empowers your organization to choose the language model that best fits your needs. Note that model performance and safety characteristics are provider-dependent.\n\n## 6. Performance\n\nGitHub Copilot Chat works by using a combination of natural language processing and machine learning to understand your question and provide you with an answer. This process involves:\n\n1. **Input processing**: The user's prompt is pre-processed by the system, combined with contextual information (for example, the current repository, open files, or chat history), and sent to a large language model. User input can take the form of code snippets or plain language.\n2. **Language model analysis**: The prompt is passed through the language model, which is a neural network trained on a large body of text data. The language model analyzes the input prompt.\n3. **Response generation**: The model generates a response based on its analysis of the input prompt and the context provided to it. This response can take the form of generated code, code suggestions, or explanations of existing code.\n4. **Output formatting**: The response is formatted with syntax highlighting, indentation, and other features to add clarity. Depending on the type of question, links to context that the model used\u2014such as source code files, issues, or documentation\u2014may also be provided.\n\n### Differences by experience\n\n- **On GitHub.com**: The model can gather additional context from repository data stored on GitHub and web search results (when enabled by your administrator). Responses may include links to source code files, issues, or documentation.\n- **Pull request summaries (GitHub.com)**: When a user requests a summary, a workflow uses the code diffs from files to build a prompt and requests Copilot to generate an overall summary. The output consists of a prose paragraph giving an overview of the changes, followed by a bulleted list of key changes linked to the respective lines of code. You can generate a summary in the description of a new or existing pull request, or in a comment on the pull request timeline. Larger pull requests may take up to a couple of minutes to process. The only supported language for pull request summaries is English.\n- **Commit message generation (GitHub.com)**: When you click the **Commit changes** button on GitHub.com, Copilot generates a suggested summary (title) and description based on the code changes in the selected files. The text is inserted into the summary and description fields for you to review and edit before committing. The only supported language for commit message generation is English.\n- **Commit message generation (GitHub Desktop)**: When you click the Copilot button in GitHub Desktop, Copilot generates a suggested summary (title) and description based on the code changes you've selected. You can select specific lines of code or files to improve context and accuracy, and you can regenerate suggestions before finalizing. The only supported language is English.\n- **In your IDE**: The system combines user input with contextual information such as the name of the repository and the files the user has open. In VS Code and Visual Studio, additional context can be provided automatically from an optional `.github/copilot-instructions.md` file (the user can disable this in settings). When using the `@github` chat participant in VS Code or Visual Studio, GitHub Copilot Chat can also gather context from code stored on GitHub and from Bing search results (if enabled by your administrator).\n- **On GitHub Mobile**: The input prompt is pre-processed and sent to the language model. The system is only intended to respond to coding-related questions. The options available vary by Copilot plan: users with a Copilot Enterprise subscription can have conversations using data from private indexed repositories and, if the web search integration is enabled, receive responses informed by web search results. Users with a Copilot Pro subscription can discuss top popular public repositories.\n- **In Windows Terminal**: The user's prompt is combined with contextual information (the name of the active shell and the chat history) and sent to the language model. Responses take the form of a suggested command or an explanation of a command. Suggested commands are not run automatically\u2014you must click on a command to insert it into your command line and then manually run it.\n- **In Copilot Spaces**: Spaces let you organize the context that GitHub Copilot Chat uses to answer your questions. A space can include repositories, code, pull requests, issues, free-text content like transcripts or notes, images, and file uploads. When you submit a question in a space, Copilot augments your request with relevant context from that space. Spaces can also be accessed from the IDE via the remote GitHub MCP server. Not all content in a space is used in every response\u2014Copilot processes a portion of the included content, so being selective about what you add helps ensure relevance.\n\nGitHub Copilot Chat is intended to provide you with the most relevant answer to your question. However, it may not always provide the answer you are looking for. Users of GitHub Copilot Chat are responsible for reviewing and validating responses generated by the system to ensure they are accurate and appropriate.\n\n## 7. Limitations\n\nUnderstanding GitHub Copilot Chat's limitations is crucial to determine if it is used within safe and effective boundaries. While we encourage customers to leverage GitHub Copilot Chat in their innovative solutions or applications, it's important to note that GitHub Copilot Chat was not designed for every possible scenario. We encourage users to refer to [GitHub Terms](https://docs.github.com/en/site-policy/github-terms) as well as the following considerations when choosing a use case:\n\n- **Limited scope**: GitHub Copilot Chat has been trained on a large body of code but may not be able to handle more complex code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data. For example, JavaScript is well-represented and well-supported, while less common languages may yield lower-quality results.\n- **Potential biases**: Training data drawn from existing code repositories may contain biases and errors that can be perpetuated by the tool. GitHub Copilot Chat may also be biased towards certain programming languages or coding styles, which can lead to suboptimal or incomplete code suggestions.\n- **Security risks**: Generated code can potentially expose sensitive information or vulnerabilities if not reviewed carefully. Always review and test generated code thoroughly, especially for security-sensitive applications.\n- **Matches with public code**: While the probability is low, GitHub Copilot Chat may produce code that matches code in the training set. You should take the same precautions as you would with any code that uses material you did not independently originate including rigorous testing, IP scanning, and checking for security vulnerabilities. For more information, see [Finding public code that matches GitHub Copilot suggestions](https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/copilot-for-common-tasks/find-matching-code).\n- **Inaccurate code**: GitHub Copilot Chat may generate code that appears valid but is not semantically or syntactically correct, or does not accurately reflect the intent of the developer. Carefully review and test generated code, particularly for critical or sensitive applications.\n- **Inaccurate responses to non-coding topics**: GitHub Copilot Chat is not designed to answer non-coding questions, and its responses in those contexts may be irrelevant or nonsensical.\n- **Risk of destructive commands (Windows Terminal)**: Copilot may suggest commands that could be destructive\u2014such as deleting content or formatting a hard drive\u2014that may be necessary in certain scenarios but can cause problems if used incorrectly. You are ultimately responsible for any commands you choose to execute. Despite the presence of fail-safes and safety mechanisms, executing commands carries inherent risks.\n- **Lines changed limits for PR summaries (GitHub.com)**: Files with more than 400 combined additions and deletions are excluded from summarization.\n- **PR summaries are not auto-updated (GitHub.com)**: Pull request summaries are only created when users request them manually. When updates or changes are made to the pull request, the summary is not automatically refreshed. Users can request a new summary, but should carefully review the updated output\u2014it carries the same risks of inaccuracy as the original.\n- **Replication of PR content (GitHub.com)**: Because a summary outlines the changes in a pull request, if harmful or offensive terms appear in the pull request content, there is potential for the summary to replicate those terms. Users should expect terms used in their PR to appear in the AI-generated summary.\n- **Limited scope for commit messages (GitHub.com and GitHub Desktop)**: Commit message generation may struggle with intricate code changes, short diff windows, or recently developed programming languages. The quality of suggestions depends on the availability and diversity of training data for the languages involved.\n- **Replication of commit content (GitHub.com and GitHub Desktop)**: Because a commit message summarizes the changes in a commit, if harmful or offensive terms appear in the code changes, there is potential for the generated message to include those terms.\n- **Commit messages are not auto-updated (GitHub.com and GitHub Desktop)**: Commit messages are only generated when you request them. When you make additional changes, the commit message is not automatically refreshed. You can regenerate a new suggestion, but should carefully review the updated output\u2014it carries the same risks of inaccuracy as the original.\n- **Interpretation of user intent (Spaces)**: Spaces help ground GitHub Copilot Chat's responses in curated context, but the system may still misunderstand your intent. Always review output to confirm it reflects your goals.\n- **Context limits (Spaces)**: Spaces have defined size limits, and GitHub Copilot Chat only processes a portion of the content you include. Not every file, document, or note in a space will be used in a response. Being selective about what you add helps ensure the most relevant context is used.",
        "description": "Learn how to use GitHub Copilot Chat responsibly by understanding its purposes, capabilities, and limitations.",
        "source": "web",
        "price": 0.0015,
        "length": 24921,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2021-11-02",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/github-copilot-chat/about-github-copilot-chat",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6101556797446378
      },
      {
        "title": "Learning about new features and models - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/concepts/enterprise/learning-about-new-features-and-models",
        "content": "In this article\n\n# Learning about new features and models\n\nCopy markdown\n\n## In this article\n\n## Up next\n\n[Pilot a new Copilot feature or model in your enterprise](https://docs.github.com/en/copilot/tutorials/roll-out-at-scale/govern-at-scale/pilot-a-feature-or-model)\n\nGitHub Copilot is evolving rapidly, with new features and models released regularly. If you're an enterprise administrator, staying informed helps you make confident decisions about which capabilities to enable, when to adopt them, and how to manage risk across your organizations.\n\nThis article provides guidance on navigating the Copilot landscape, understanding different types of features and models, and preparing for upcoming changes.\n\n## Keeping up to date with Copilot changes\n\nYou can use GitHub Docs and the GitHub Blog to keep track of new releases.\n\n### Learning about new Copilot features\n\nTo learn about new Copilot features, we recommend monitoring these two locations:\n\n- **Copilot blog updates**: For broader news and updates about Copilot, see the [Copilot blog](https://github.blog/ai-and-ml/github-copilot/).\n- **Changelog**: For announcements about newly released and updated features, follow the [Copilot changelog](https://github.blog/changelog/?label=copilot).\n\nCopilot's capabilities and supporting features fall into four categories:\n\n| Type | Description | Examples | Considerations |\n| --- | --- | --- | --- |\n| Assistive | Respond to prompts and provide suggestions, but require human review before changes are made. | Inline suggestions, Copilot Chat, Copilot pull request summaries. | All changes require user approval. |\n| Agentic | Autonomously research, plan, and make changes on behalf of users. | Copilot cloud agent, third-party agents. | Can work autonomously, but with built-in protections. |\n| Customizations | Add context, instructions, tools, skills, and agents to tailor how Copilot responds and works. | Custom instructions, prompt files, Copilot Spaces, MCP servers, agent skills, custom agents. | Support and configuration vary by feature and surface. Organization and enterprise policies can control access to some customizations. |\n| External AI agents, models, and tools | External coding agents, models, and tools, including MCP servers from other providers, that work alongside Copilot cloud agent to complete tasks asynchronously. | Anthropic Claude, OpenAI Codex. | Same as agentic. Review provider documentation and enable via policies. See [About third-party coding agents](https://docs.github.com/en/copilot/concepts/agents/about-third-party-coding-agents). |\n\nEach feature has its own enablement requirements and policy settings. When a new feature is released:\n\n1. Review the feature documentation to understand its capabilities.\n2. Check the policy settings available at the enterprise and organization level. See [GitHub Copilot policies for enterprises and organizations](https://docs.github.com/en/copilot/concepts/enterprise/policies).\n3. Consider running a pilot with a subset of users before broader rollout.\n\n### Learning about new Copilot models\n\nGitHub Copilot uses multiple AI models from different providers to power its features. Different models have different strengths: some prioritize speed and cost-efficiency, while others are optimized for accuracy, reasoning, or working with multimodal inputs (like images and code together).\n\nUsers will have access to different models depending on the feature they're using and your enterprise's Copilot plan and policies.\n\nYou can find information about the models available and upcoming models in the following locations:\n\n- **Supported models**: For a complete list of available models and their capabilities, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models).\n- **Model comparison**: To compare model capabilities side by side, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison).\n- **Changelog**: Model updates are announced in the [Copilot changelog](https://github.blog/changelog/label/copilot/).\n\n#### Special categories\n\nGitHub categorizes certain types of model, allowing you to plan for model transitions and set user expectations.\n\n| Model type | Description | Why it matters |\n| --- | --- | --- |\n| Utility model | A small set of models that power background GitHub features across surfaces. | Your enterprise cannot disable these models. Monitor these to ensure they are compliant. |\n| Base model | The default model when no other models are enabled. | Automatically enabled within 60 days of designation. |\n| LTS model | A model supported for one year from designation. | Allows enterprises to build workflows around a stable model. |\n\nFor more information, see [Utility models](https://docs.github.com/en/copilot/concepts/models/utility-models) and [Base and long-term support (LTS) models](https://docs.github.com/en/copilot/concepts/models/fallback-and-lts-models).\n\n### Default enablement\n\nFor enterprises with Copilot Business or Copilot Enterprise plans, two separate policies control whether unconfigured generally available (GA) features and models default to enabled or disabled. If these policies are enabled, users benefit from the latest features and models without the need for administrator intervention.\n\nThe models policy is already active. The feature policy will become active soon.\n\nFor more information, see [About default availability of Copilot features and models](https://docs.github.com/en/copilot/concepts/enterprise/default-availability).\n\n## Considering different release stages\n\nCopilot features and models progress through different release stages. Understanding release stages helps you decide when to enable features for your organization. Each stage has different expectations for stability and support.\n\n| Stage | Availability | Stability |\n| --- | --- | --- |\n| Private preview | Limited set of customers by invitation. | May change significantly based on feedback. |\n| Public preview | All eligible customers who opt in. | Functional but may have limitations or change. |\n| Generally available (GA) | All customers. | Fully supported and recommended for production. |\n\nMany preview features are covered by the [GitHub Data Protection Agreement](https://gh.io/dpa), meaning you can test them without breaching compliance requirements. See [GitHub DPA-Covered Previews](https://gh.io/dpa-previews) for a list.\n\nPreview features are controlled by policy settings at the organization and enterprise level. The **Opt in to preview features** policy allows administrators to enable or disable preview features on the GitHub website specifically. See [Managing policies and features for GitHub Copilot in your enterprise](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies) and [Managing policies and features for GitHub Copilot in your organization](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies).\n\n## Reviewing information about Responsible AI\n\nGitHub is committed to responsible AI development and provides transparency documentation for each Copilot feature.\n\nEach Copilot feature has a dedicated **responsible use** article describing its purpose, capabilities, and limitations. See [Responsible use of GitHub Copilot features](https://docs.github.com/en/copilot/responsible-use).",
        "description": "Stay informed about GitHub Copilot features and models, and make confident decisions about enabling them for your enterprise.",
        "source": "web",
        "price": 0.0015,
        "length": 7444,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/concepts/enterprise/learning-about-new-features-and-models",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6101556797446378
      },
      {
        "title": "Application card: GitHub Copilot Agents - GitHub Docs",
        "url": "https://docs.github.com/en/copilot/responsible-use/agents",
        "content": "In this article\n\n# Application card: GitHub Copilot Agents\n\nCopy markdown\n\n## In this article\n\n## What is an Application Card?\n\nGitHub\u2019s application and platform cards are intended to help you understand how our AI technology works, the choices application owners can make that influence application performance and behavior, and the importance of considering the whole application, including the technology, the people, and the environment. Application cards are created for AI applications and platform cards are created for AI platform services. These resources can support the development or deployment of your own applications and can be shared with users or stakeholders impacted by them.\n\nAs part of its commitment to responsible AI, GitHub adheres to Microsoft's [six core principles](https://www.microsoft.com/en-us/ai/principles-and-approach/?msockid=3da790040c776d6f2b5485e40de56c06#ai-principles): fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability. These principles are embedded in the [Responsible AI Standard](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/final/en-us/microsoft-brand/documents/Microsoft-Responsible-AI-Standard-General-Requirements.pdf?culture=en-us&country=us), which guides teams in designing, building, and testing AI applications. Application and Platform Cards play a key role in operationalizing these principles by offering transparency around capabilities, intended uses, and limitations. For further insight, readers are encouraged to explore Microsoft\u2019s [Responsible AI Transparency Report](https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/msc/documents/presentations/CSR/Responsible-AI-Transparency-Report-2025-vertical.pdf) and [GitHub Terms](https://docs.github.com/en/site-policy/github-terms).\n\n## 1. Overview\n\nGitHub Copilot includes several agentic features that go beyond suggestion and conversation\u2014they can review code, take action on your behalf, and build applications. This card covers the following experiences:\n\n- **Copilot code review**: Reviews pull request diffs and metadata on GitHub.com, producing feedback comments and suggested changes.\n- **Copilot cloud agent**: An asynchronous agent on GitHub.com that can create branches, write code, and open pull requests in response to assigned issues. The cloud agent runs in an ephemeral, firewalled environment with automated security scanning.\n- **Copilot CLI**: A command-line tool that can create and modify files, execute commands, and perform multi-step tasks. By default, filesystem access is scoped to the directory where the CLI was started. Permission prompts depend on the active permission mode. When computer use is enabled, Copilot CLI can also interact with desktop applications outside that directory scope.\n- **Copilot SDK**: A programmatic library that allows developers to build custom AI-powered applications using Copilot. The SDK communicates with Copilot CLI over JSON-RPC and supports custom agents, MCP server integrations, lifecycle hooks, and session management.\n- **GitHub Copilot app**: A desktop application for directing agent sessions across local repositories, git worktrees, and cloud sandboxes. The app uses GitHub Copilot CLI and GitHub Copilot SDK as its foundation and adds a user interface for parallel sessions, quick chats, GitHub issue and pull request workflows, automations, and canvases. When computer use is enabled, the app can also interact with desktop applications.\n\nThese features share common principles\u2014human oversight, review of outputs, and responsible use\u2014but differ in their execution environments, permissions, and data flows. The sections below describe each in context.\n\n## 2. Key terms\n\nThe following list provides a glossary of key terms related to GitHub Copilot Agents:\n\n- **Code suggestion**: A specific code change proposed by Copilot code review as part of its feedback on a pull request. Code suggestions are presented as suggested changes that can be applied with a couple of clicks.\n- **Content filtering**: A safety system that scans prompts and responses to detect and block harmful, offensive, or insecure content before it is shown to the user.\n- **Computer use**: An optional capability in GitHub Copilot CLI and GitHub Copilot app that allows an agent to interact with desktop applications. Its tools can read accessible application content and visual context through the operating system's accessibility tree or screenshots when visual context is needed, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across applications.\n- **Custom instructions**: Natural language descriptions of coding style and best practices that a repository maintainer can configure to guide Copilot code review's feedback. Custom instructions help Copilot understand the conventions and standards of a specific codebase.\n- **Hallucination**: A phenomenon where a language model generates output that sounds plausible but is factually incorrect, unsupported by the provided context, or entirely fabricated. In code review, hallucination can manifest as feedback that highlights problems that do not exist or are based on misunderstandings of the code.\n- **Large language model (LLM)**: A type of neural network trained on a large body of text data that can generate, analyze, and transform natural language and code. Copilot Agents use one or more LLMs to process context and produce responses.\n- **Ephemeral development environment**: A temporary, isolated compute environment created for each cloud agent session. The environment is destroyed after the session ends, ensuring that no state persists between runs.\n- **Firewall**: A network-level control enabled by default for the cloud agent that prevents outbound connections to unauthorized hosts, protecting against accidental or malicious exfiltration of code or data.\n- **AI credit**: A unit of consumption for Copilot features. Each use of Copilot code review consumes AI credits.\n- **Permission prompt**: An interactive confirmation step in Copilot CLI that asks the user to approve an action\u2014such as modifying a file, executing a command, or accessing files outside the current directory\u2014before the agent proceeds. Permission prompts are a key safety mechanism for local agentic execution.\n- **Copilot SDK**: A programmatic library (`@github/copilot-sdk`) that lets developers build custom AI-powered applications by creating sessions, sending prompts, and receiving streaming responses from Copilot. The SDK communicates with Copilot CLI over JSON-RPC.\n- **JSON-RPC**: The communication protocol used between the Copilot SDK and Copilot CLI. The SDK sends structured requests to the CLI process, which handles model interaction and tool execution.\n- **Custom agent (SDK)**: A named agent configuration within the SDK that has its own system prompt, scoped tools, and optional MCP servers. The SDK runtime can automatically delegate to sub-agents based on user intent.\n- **Hooks (SDK)**: Lifecycle callbacks in the Copilot SDK that let developers inject custom logic at specific points during a session, such as before or after tool use, on session start or end, and on error.\n\n## 3. Key features or capabilities\n\nThe key features and capabilities outlined here describe what GitHub Copilot Agents are designed to do and how they perform across supported tasks.\n\n- **Automated code review feedback**: When a user requests a review from Copilot, it scans the code changes plus additional relevant context and provides feedback on the code. Feedback may include natural language comments and specific code suggestions linked to particular lines and files.\n- **Customizable review guidance**: Copilot code review can be customized with custom instructions\u2014natural language descriptions of coding style and best practices\u2014so that feedback reflects a repository's conventions and standards.\n- **Autonomous pull request creation**: The Copilot cloud agent can pick up a task from an issue, a pull request comment, or Copilot Chat, create a branch, generate tailored code changes, and open a pull request. After the initial pull request is created, the agent can iterate based on your feedback and reviews.\n- **Ephemeral, firewalled execution**: While working on a task, the cloud agent has access to its own ephemeral development environment where it can make changes to code, execute automated tests, and run linters. A firewall is enabled by default to prevent data exfiltration.\n- **Automated security scanning**: During code generation, the cloud agent automatically analyzes newly generated code for security vulnerabilities using CodeQL, secret scanning, and dependency analysis, and attempts to resolve any issues before they are introduced.\n- **External integrations**: The cloud agent can receive information and context from MCP like workIQ and Microsoft 365, and external applications like Microsoft Teams, Linear, Slack, and Jira, enabling teams to assign tasks and track progress directly within their existing workflows.\n- **Local agentic execution (Copilot CLI)**: Copilot CLI provides a chat-like interface in the terminal that can autonomously create and modify files, execute commands, and perform multi-step tasks. By default, filesystem access is scoped to the directory where the CLI was started. The active permission mode determines whether the CLI prompts before modifying files or running commands.\n- **Desktop application interaction (computer use)**: In local Copilot CLI and Copilot app sessions, computer use can read accessible application content and visual context through the operating system's accessibility tree or screenshots when visual context is needed, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across applications.\n\n## 4. Intended uses\n\nGitHub Copilot Agents can be used in multiple scenarios across a variety of industries. Some examples of use cases include:\n\n- **Supplementing human code review**: Copilot code review is intended to quickly provide feedback on a developer's code, enabling developers to get code ready to merge more quickly and increasing overall code quality.\n- **Codebase maintenance**: The cloud agent can tackle security-related fixes, dependency upgrades, and targeted refactoring.\n- **Feature development**: The cloud agent can implement incremental feature requests, develop additional test suites, and create or update documentation.\n- **Prototyping new projects**: The cloud agent and Copilot CLI can greenfield new concepts, helping developers explore ideas quickly.\n- **Setting up your environment (CLI)**: Copilot CLI can run commands in your terminal to set up your local environment to work on existing projects.\n- **Finding the right command (CLI)**: Copilot CLI can suggest commands to perform tasks you're trying to complete, and explain unfamiliar commands in natural language.\n- **Working with legacy and GUI-only applications (computer use)**: Computer use can help with workflows in local desktop applications that do not provide an API, command-line interface, or MCP integration. Users should describe the outcome, applications, and important constraints, then review the actions and result.\n- **Building custom AI applications (SDK)**: The Copilot SDK enables developers to build applications that leverage Copilot for code generation, natural language interaction, and task automation in their own products and workflows.\n- **Multi-agent orchestration (SDK)**: Using custom agents and sub-agents, developers can build sophisticated workflows where multiple specialized agents collaborate on complex tasks, with automatic delegation based on user intent.\n- **Extending applications with external tools (SDK)**: The SDK's MCP server support allows developers to connect their applications to external data sources and services, expanding the range of tasks their agents can perform.\n\n## 5. Models and training data\n\nGitHub Copilot Agents leverage a variety of AI models to power the experience that users see. For a comparison of the models available for Copilot, see [AI model comparison](https://docs.github.com/en/copilot/reference/ai-models/model-comparison). For the full list of supported models, see [Supported AI models in GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models). For information on where models are hosted, see [Hosting of models for GitHub Copilot](https://docs.github.com/en/copilot/reference/ai-models/model-hosting). To learn more about the data used to train the foundation models behind GitHub Copilot Agents, refer to the linked AI model comparison above and [What data has GitHub Copilot been trained on?](https://github.com/features/copilot#faq) in the GitHub Copilot FAQ.\n\nCopilot code review is a purpose-built product that uses a carefully tuned mix of models, prompts, and system behaviors to deliver consistent, high-quality feedback across a wide range of codebases. Model switching is not supported, as changing the model is likely to compromise reliability, user experience, and the quality of review comments. Copilot code review may use models that are not enabled on your organization's \"Models\" settings page.\n\nThe Copilot cloud agent uses a large language model to reason about tasks, generate code, and leverage tools within its ephemeral development environment. The agent has been evaluated across a variety of programming languages. English is the primary supported language for prompts and responses.\n\nCopilot CLI uses a large language model to reason about tasks, generate code, modify files, and execute commands in your local terminal environment. The agent has been evaluated across a variety of programming languages. English is the primary supported language for prompts and responses.\n\nThe Copilot SDK communicates with Copilot CLI over JSON-RPC, using the same underlying models and capabilities. Applications built with the SDK use the same models available to the authenticated Copilot user or organization. Developers can also bring their own API keys (BYOK) to use custom model providers.\n\n## 6. Performance\n\n### Differences by experience\n\n#### Copilot cloud agent\n\nThe Copilot cloud agent works by using a combination of natural language processing and machine learning to understand your task and make changes in a codebase. This process can be broken down into a number of steps:\n\n1. **Prompt processing**: The task provided through an issue, pull request comment, or Copilot Chat message is combined with other relevant, contextual information to form a prompt. That prompt is sent to a large language model for processing. Inputs can take the form of plain natural language, code snippets, or images.\n2. **Language model analysis**: The prompt is passed through a large language model, which is a neural network that has been trained on a large body of data. The language model analyzes the input prompt to help the agent reason about the task and leverage necessary tools.\n3. **Response generation**: The language model generates a response based on its analysis of the prompt. This response can take the form of natural language suggestions and code suggestions.\n4. **Output formatting**: Once the agent completes its first run, it updates the pull request description with the changes it made. The agent may include supplemental information about resources it could not access and provide suggestions on steps to resolve. You may provide feedback by commenting within the pull request or explicitly mentioning the agent (`@copilot`). The agent will then resubmit that feedback for further analysis and respond with updated changes.\n\nCopilot cloud agent is intended to provide the most relevant solution for task resolution. However, it may not always provide the answer you are looking for. You are responsible for reviewing and validating responses generated by Copilot cloud agent to ensure they are accurate and appropriate.\n\n#### Copilot code review\n\nCopilot code review inspects your code and provides feedback using a combination of natural language processing and machine learning. This process can be broken down into a number of steps:\n\n1. **Input processing**: The code changes are combined with other relevant, contextual information (for example, the pull request's title and body), and any custom instructions that have been defined, to form a prompt. That prompt is sent to a large language model.\n2. **Language model analysis**: The prompt is passed through the Copilot language model, which is a neural network that has been trained on a large body of text data. The language model analyzes the input prompt.\n3. **Response generation**: The language model generates a response based on its analysis of the input prompt. This response can take the form of natural language suggestions and code suggestions.\n4. **Output formatting**: The response is presented to the user either directly in a supported editor or as a pull request review on GitHub.com, providing code feedback linked to specific lines of specific files. Where Copilot has provided a code suggestion, the suggestion is presented as a suggested change, which can be applied with a couple of clicks.\n\n#### Copilot CLI\n\nCopilot CLI works by using a combination of natural language processing and machine learning to understand your task and make changes in a codebase. This process can be broken down into a number of steps:\n\n1. **Input processing**: Your input is combined with relevant contextual information to form a prompt. That prompt is sent to a large language model for processing. Inputs can take the form of plain natural language, code snippets, or references to files in your terminal.\n2. **Language model analysis**: The prompt is passed through a large language model, which is a neural network that has been trained on a large body of data. The language model analyzes the input prompt to help the agent reason about the task and use the necessary tools.\n3. **Response generation**: The language model generates a response based on its analysis of the prompt. This response can take the form of natural language suggestions, code suggestions, file modifications, and command executions.\n4. **Output formatting**: The response is formatted and presented using syntax highlighting, indentation, and other formatting features. The agent may also execute commands in your local environment and create, edit, or delete files in your file system in order to complete the task. All such actions require explicit permission prompts.\n\nYou may provide feedback to the agent after it returns a response in the interactive chat window. The agent will resubmit that feedback to the language model for further analysis and return an additional response.\n\n#### Copilot SDK\n\nThe Copilot SDK provides a programmatic interface to Copilot's agentic capabilities. Applications built with the SDK follow this process:\n\n1. **Session creation**: The application creates a session with the SDK, specifying the model, system prompt, available tools, custom agents, MCP servers, and hooks. The SDK establishes a JSON-RPC connection to Copilot CLI.\n2. **Prompt submission**: User input is submitted to the session. The SDK routes the prompt (along with session context) to the CLI, which forwards it to the language model.\n3. **Agent execution**: The language model reasons about the task and may invoke tools, delegate to sub-agents, or connect to MCP servers. Lifecycle hooks fire at each stage, allowing the application to inject custom logic.\n4. **Response streaming**: Responses are streamed back to the application, which can present them in any format appropriate for its interface. The SDK provides structured events for text, tool calls, errors, and completion signals.\n\n## 7. Limitations\n\nUnderstanding GitHub Copilot agentic features' limitations is crucial to determine they are used within safe and effective boundaries. While we encourage customers to leverage these features in their innovative solutions or applications, it's important to note that they were not designed for every possible scenario. We encourage users to refer to [GitHub Terms](https://docs.github.com/en/site-policy/github-terms) as well as the following considerations when choosing a use case:\n\n- **Missed code quality problems**: Copilot may not identify all of the problems that are present in code, especially where changes are large or complex. To ensure that all relevant problems are identified and corrected, Copilot code review should be supplemented with careful human code review.\n- **False positives**: Copilot code review has a risk of hallucination\u2014it may highlight problems in reviewed code that do not exist or are based on misunderstandings of the code. Comments generated by Copilot code review should be carefully reviewed and considered before taking action and making changes.\n- **Inaccurate or insecure code suggestions**: As part of its comments, Copilot code review may provide specific code suggestions. The code generated may appear to be valid but may not actually be semantically or syntactically correct, or may not correctly resolve the problem identified in the comment. In addition, code generated by Copilot may contain security vulnerabilities or other issues. You should always carefully review and test code generated by Copilot.\n- **Potential biases**: Copilot's training data is drawn from existing code repositories, which may contain biases and errors that can be perpetuated by the tool. Additionally, Copilot code review may be biased toward certain programming languages or coding styles, which can lead to suboptimal or incomplete feedback.\n- **Limited scope (cloud agent)**: The language model used by the cloud agent has been trained on a large body of code but still has a limited scope and may not be able to handle certain code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data for that language.\n- **Inaccurate code (cloud agent)**: The cloud agent may generate code that appears to be valid but may not actually be semantically or syntactically correct, or may not accurately reflect the intent of the developer. You should carefully review and test generated code, particularly when dealing with critical or sensitive applications.\n- **Security risks (cloud agent)**: The cloud agent generates code and natural language based on the context of an issue or comment within a repository, which can potentially expose sensitive information or vulnerabilities if not used carefully. You should review all outputs generated by the agent thoroughly prior to merging.\n- **Public code matches (cloud agent)**: The cloud agent may generate code that is a match or near match of publicly available code, even if the \"Suggestions matching public code\" policy is set to \"Block.\" If this happens, Copilot will show matches in the agent session logs with a link to display details of the matched code.\n- **Limited scope (CLI)**: The language model used by Copilot CLI has been trained on a large body of code but still has a limited scope and may not be able to handle certain code structures or obscure programming languages. For each language, the quality of suggestions depends on the volume and diversity of training data for that language.\n- **Inaccurate code (CLI)**: Copilot CLI may generate code that appears to be valid but may not actually be semantically or syntactically correct, or may not accurately reflect the intent of the developer. You should carefully review and test generated code, particularly when dealing with critical or sensitive applications.\n- **Security risks (CLI)**: Copilot CLI generates code and natural language based on the context of your local environment, which can potentially expose sensitive information or vulnerabilities if not used carefully. You should review all outputs generated by the agent thoroughly.\n- **Public code matches (CLI)**: Copilot CLI may generate code that is a match or near match of publicly available code, even if the \"Suggestions matching public code\" policy is set to \"Block.\"\n- **Command execution risks (CLI)**: Additional caution is required when asking or allowing Copilot CLI to execute a command, particularly regarding the potential destructiveness of some suggested commands. You may encounter commands for file deletion or hard drive formatting, which can cause problems if used incorrectly. You are ultimately responsible for the commands executed by Copilot CLI.\n- **Interface interpretation (computer use)**: Computer use may select the wrong control, enter text in the wrong location, or have difficulty with non-standard or dynamic controls and complex workflows. Changes in timing or window state can produce different results, cause computer use to repeat an action, or prevent it from continuing.",
        "description": "Learn how to use GitHub Copilot agentic features responsibly by understanding their purposes, capabilities, and limitations.",
        "source": "web",
        "price": 0.0015,
        "length": 24954,
        "data_type": "unstructured",
        "source_type": "website",
        "publication_date": "2026-10-06",
        "crawl_date": "2026-10-06",
        "id": "https://docs.github.com/en/copilot/responsible-use/agents",
        "image_url": {
          "0": "https://docs.github.com/assets/cb-345/images/social-cards/copilot.png"
        },
        "relevance_score": 0.6071616657651597
      }
    ],
    "results_by_source": {
      "web": 10,
      "proprietary": 0
    },
    "total_deduction_dollars": 0.015,
    "total_characters": 114533
  }
}