Problem

A customer asked whether they can use Github Copilot as an LLM provider for the nao open source agent. Today the nao OSS agent supports a set of LLM providers (OpenAI, Anthropic, etc.) but Github Copilot is not one of them.

Some developers already pay for Copilot and want to route nao's agent calls through their Copilot subscription instead of bringing a separate API key.

Expected behavior

Investigate and, if feasible, add Github Copilot as a supported LLM provider in the nao OSS agent:

• Identify the right Copilot API surface (Copilot Chat API / OpenAI-compatible endpoint exposed via Copilot)
• Handle auth (Github OAuth / Copilot token)
• Wire it into the existing provider abstraction so users can select copilot as their model provider
• Document the setup in the nao CLI / context docs

Impact

Lowers the barrier to adoption for developers who already have a Copilot subscription and don't want to manage a separate OpenAI/Anthropic key. Also broadens the set of enterprises where nao can run (some orgs standardise on Copilot for LLM spend).

Reported by

Customer question