From the experiment

Do coding agents recommend Bing grounding?

Bing grounding was chosen in 2% of 639 judged AI search sessions, ranking tenth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Bing grounding was chosen in 2% of 639 judged AI search sessions, ranking tenth. It was also raised as a candidate in 30 further sessions without being chosen.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in AI search inside a realistic codebase. Not what a chat assistant says about Bing grounding. What an agent actually installed.

The numbers

CategoryAI search
Sessions in the category639
Sessions where Bing grounding was chosen14
Install share2%
Rank in category10 of 42
Codebases it won in2
Raised as a candidate, not chosen30
Chosen when considered32%
Siteazure.microsoft.com

By agent

With 14 wins spread across 5 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.

AgentSessionsChose Bing groundingShare
Claude Code14000%
Codex19221%
Cursor13654%
Grok Build CLI3513%
Muse Code13664%

By who was asking

Bing grounding performs similarly across the four kinds of buyer, from 0% to 4%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.

Who is askingSessionsChose Bing groundingShare
Vibe coder10600%
Junior developer20800%
Senior engineer15774%
Enterprise team16874%

What Bing grounding was up against

The full ranking in AI search, from the same sessions:

#ProductRuns wonShare
1Exa9214%
2Brave Search API8914%
3Anthropic web search8613%
4Tavily7912%
5OpenAI web search325%
6Built in-house (no product adopted)325%
7Firecrawl315%
8Parallel295%

What this means

Bing grounding was raised in 30 sessions and chosen in 14. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.

Where these numbers come from

The 639 sessions in AI search are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every AI search run can be replayed on the board.

If you work on Bing grounding: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend Bing grounding?

Yes. Bing grounding was chosen in 14 of the 639 judged sessions in AI search, a 2% install share, ranking tenth in its category.

Does Claude Code recommend Bing grounding?

In 0 of the 140 sessions in AI search run with Claude Code, which is 0%.

Do different coding agents treat Bing grounding differently?

Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 4% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

How often is Bing grounding considered but not chosen?

It was raised as a candidate in 30 sessions without being chosen, and chosen in 14. That is a 32% conversion from considered to chosen.

Where this comes from

Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages