Copilot Web App: ?q= parameter no longer populates chat input (regression)
Description
Previously, the Copilot web app accepted queries passed via the URL parameter ?q= and auto‑populated them into the chat box. This allowed browsers (e.g., Floorp, Firefox derivatives) to set Copilot as a search engine with https://copilot.microsoft.com/?q=%s, so that typing into the browser’s search bar flowed directly into Copilot chat.
As of late 2025, this behavior has changed:
?q= still loads Copilot, but only displays the query at the top of the page.
The chat box remains empty, requiring an extra click to start a conversation.
This breaks the previous integration with browser search engines and reduces usability.
Steps to Reproduce
Set Copilot as a search engine in a browser using https://copilot.microsoft.com/?q=%s.
Type a query in the browser’s search bar.
Observe that Copilot opens, but the query does not appear in the chat box.
Expected Behavior
Queries passed via ?q= (or a documented alternative parameter) should auto‑populate the Copilot chat input, restoring the seamless search‑to‑chat flow.
Actual Behavior
The query is shown only as a heading/result, not injected into chat.
Impact
Breaks existing search engine integrations in browsers like Floorp/Firefox.
Adds friction (extra click) for users who relied on direct search‑to‑chat flow.
Reduces accessibility and efficiency of Copilot as a default search engine.
Request
Please either:
- Restore support for
?q= to populate the chat box, or
Document a new parameter/API that allows browsers to pass queries directly into Copilot chat.
This would re‑enable Copilot as a true search engine option and preserve the streamlined UX many users relied on.
Copilot Web App: ?q= parameter no longer populates chat input (regression)
Any feedback would be appreciated, why this feature no longer is operational, and if there is an alternative that has a similar experience. I would like to phase out my search engine and replace it with copilot.