[FEATURE] check claude.md file on vendor's website when a vendor is mentioned in the prompt

Resolved 💬 3 comments Opened May 11, 2026 by ediril Closed May 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Could claude code fetch <vendor>/llms.txt or <vendor>/claude.md and incorporate it into context before proceeding to tackle a task that the prompt explicitly calls out for the said <vendor>?

Right, and that's the honest gap. With today's stock Claude Code, there is no mechanism that lets a cold-start agent reflexively install a vendor's plugin from a bare prompt like "build a Fivetran connector for GitHub." Because: - Agents don't auto-fetch <vendor>/llms.txt when a vendor is named — there's no reflex, no spec. - The plugin marketplace isn't queried automatically when a topic comes up; the user (or a skill) has to invoke it. - Plugins aren't surfaced from training data unless the model genuinely "knows" the plugin exists — which fivetran_csdk_tools doesn't, yet.

As you can see above, Claude Code admitted it assumes it knows and does not reach out to vendor sites to see what is available. It should NOT assume it knows because the training will always be stuck in the past.

Proposed Solution

That claude would reach out to <vendor>/llm.txt or <vendor>/agents.md or <vendor>/claude.md and incorporate it into its context before proceeding to respond to the prompt

Alternative Solutions

There is none today

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

A prompt like "please build a csdk connector for Fivetran for github api" and claude code would first look for https://<vendor>.com/claude.md

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗