RESPECTARIUM·AI Sources
Leaderboards›AI Code Assistants›AI Sources

What AI reads before it recommends AI Code Assistants tools

One question, put to the two AI engines that hand back the pages they opened.

The question, as it was asked

“What are the best AI code assistants and AI-powered IDEs for software developers?”

asked Oct 7, 2026 · Perplexity and Google AI Overviews · US English

These are not the leaderboard's engines. The leaderboard and the debate ask ChatGPT, Claude and Gemini. This page asks Perplexity and Google, because they are the two that disclose what they read. What an engine reads here does not explain a rank there.

Who they named

The companies each engine's answer named, in the order it first mentioned them. Order of mention is not a rank — neither engine ranked anything.

PerplexityPerplexity named 7 companies
  1. 1GitHub Copilot×2#1
  2. 2Cursor×2#4
  3. 3Claude Code×2#8
  4. 4Codeium×2#3
  5. 5OpenAI Codex—
  6. 6Gemini Code Assist#11
  7. 7Cline×2—
Google AI OverviewsGoogle AI Overviews named 11 companies
  1. 1Cursor×2#4
  2. 2GitHub Copilot×2#1
  3. 3Claude Code×2#8
  4. 4Visual Studio Code (with Extensions)—
  5. 5Cline×2—
  6. 6Continue#20
  7. 7Codeium×2#3
  8. 8JetBrains AI Assistant#6
  9. 9Replit Ghostwriter#5
  10. 10Tabnine#2
  11. 11Aider#16

Named here, not on our leaderboard

3 companies the engines named are not on our leaderboard at all.

ClineVisual Studio Code (with Extensions)OpenAI Codex

What they read

Every page each engine retrieved while answering. Retrieved is not the same as relied on — the engines report the pages they pulled back, and no engine tells anyone which of them changed its answer.

PerplexityPerplexity retrieved 41 pages from 28 sites· 15 of those pages sit on a company's own site

Most-read sites

docs.github.comown site7 pages
github.comown site5 pages
github.blog2 pages
learn.microsoft.com2 pages
tech-insider.org2 pages
asianefficiency.com1 page
blogs.microsoft.com1 page
bluehost.com1 page
cloudzero.com1 page
cursor.comown site1 page

Every page retrieved

Google AI OverviewsGoogle AI Overviews retrieved 8 pages from 6 sites

Most-read sites

instagram.com2 pages
linkedin.comcommunity2 pages
axify.io1 page
flixcode.dev1 page
slashdot.org1 page
trustradius.comreview site1 page

Every page retrieved

Google's first page

The classic results Google listed for the same question, on the same call as the overview. Read 8 pages; 0 of them are on Google's first page.

  1. 1st result3 Best IDE & Editor AI Tools for Developers (2026)virtualoutcomes.io
  2. 2nd resultBest AI Coding Assistants for Developers in 2026 - BridgeAppbridgeapp.ai
  3. 3rd resultBest AI Code Assistants & Agentic IDEs for Windows 2026trustradius.com
  4. 4th resultWhat ai coding assistant is better if I want to rely on one for ...reddit.com
  5. 5th resultAI IDEs Every Developer Should Try in 2026flixcode.dev

A position here is a place in Google's classic results for this question, not a rank of a company and not one of ours. A check holds 7 to 10 of them.

The regulars

Sites this engine keeps coming back to. Page lists change week to week; the sites are much steadier, which is why this is the only thing here counted across checks.

Perplexity
  • tech-insider.org4/4
  • daily.dev4/4
  • memeburn.com4/4
  • pecollective.com4/4
  • resources.rework.com4/4
  • verdent.ai4/4
  • cloudzero.com3/4
  • miniloop.ai3/4
Google AI Overviews
  • axify.io3/4
  • instagram.com2/4
  • linkedin.com2/4
  • flixcode.dev2/4
  • slashdot.org2/4
  • trustradius.com2/4
What these numbers rest onOne question · the dates · how often each engine was asked

This page is about one question, not about the category. It says: when a buyer asks this exact question, here is what each engine retrieved and who each one named. It does not say these are the pages AI reads about this category — measured, one question finds only about a third of the sites the engines keep returning to across a whole market.

  • Retrieved, never cited. The engines hand back the pages they pulled; none of them says which ones it leaned on.
  • Per engine, never pooled. The engines read mostly different webs, so a combined page count would describe a list neither of them produced. The only cross-engine facts here are that both engines read a site and that both engines named a company.
  • Counts, never rates. Every number here counts a named thing. There is no percentage anywhere on this page.
  • An engine we could not read is said so plainly and enters no count. It is never shown as a zero.

When an engine returns nothing — the call fails, Perplexity answers without searching, or Google shows no overview — it is asked again, up to 3 times in all. Whatever the last attempt gave is what is published, with the number of attempts beside it.

  • Perplexity — asked once on Oct 7, 2026
  • Google AI Overviews — asked once on Oct 7, 2026

We do not open the retrieved pages. Everything here comes from what the engines themselves handed back. Both engines are asked from the United States, in English.

These are not the leaderboard's engines. The leaderboard and the debate ask ChatGPT, Claude and Gemini. This page asks Perplexity and Google, because they are the two that disclose what they read. What an engine reads here does not explain a rank there.

Methodology version 1.1.0Read the full methodology →

This check is one of a set. The same question is put to the same two engines in every tracked category, once a week.

What the engines read across every category →

Earlier checks

Each week's check is kept on that week's archive page, beside the leaderboard and the debate it shares a date with.

Sep 27, 2026 →Sep 20, 2026 →Sep 13, 2026 →