# Aaron Tay

- Researcher: Aaron Tay
- Role: Librarian; writes "Aaron Tay's Musings about Librarianship"; says he is a member of Clarivate's Academia AI Advisory Council (as disclosed on the page)
- Field: library and information science
- Tools: Codex (GPT-5.5, extra-high effort; GPT-5.4-mini, low effort); Claude (model not named); Primo MCP server (forked); vibe coding
- Published: 2026-06-24
- Source: https://aarontay.substack.com/p/what-changes-when-an-llm-agent-searches
- Latest flagship models when written: Claude Fable 5 and GPT-5.5. Latest now: Claude Opus 5.5 and GPT-6.1 Sol.

## What they did

Tay forked an open-source Primo MCP server so an agent could search his institution's library catalogue, then took selected 2023 searches that had returned zero results and ran them through 2026 models. He compared the agent loop with the vendor's own Natural Language Search, which turns a query into one Boolean string. The agent recovered from misspellings (for example reading "statis" as the database Statista) and widened over-specific queries, where the one-shot expansion mostly did not. A weaker model did about as well, which he attributes to the search loop.

## In their words

> "I was vibe coding almost the whole way: run it, look at what broke, ask Codex or Claude to fix it."

> "to see how far one-shot query expansion gets without a loop. The answer is: not far."

> "nothing in my current setup forces the final answer to contain only fields returned by Primo"

## Lessons they draw

- The gain came from the iterative search loop rather than model tier (Tay).
- Grounding in tool output holds at retrieval, not in the final answer; generated links should be validated (Tay).
- The test is exploratory: non-random 2023 queries replayed on 2026 models (Tay).

## Limits of this account

First post of a series; read in the opening sections only. The coding was done with the agents and the research object is a search system, so part of the account is software building. The page names no Claude model. Quotes checked against the fetched page text on 2026-11-05.
