Z llms.txt and agents.md

Publish llms.txt and agents.md with Zed

Publishing llms.txt and agents.md with Zed means using the Agent Panel in the editor to have StoreSEO check, generate and reset the AI discovery files your Shopify store serves, with Zed's tool prompts as a second check on each call.

Jump to the prompts Connect Zed

Last updated: October 2026

Set up Zed for StoreSEO

Skip this if Zed is already connected. The full guide, with the alternatives, is on the Zed page.

1
Add StoreSEO as a remote server

Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON

{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
2
Sign in and check the dot

Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
Prompt

Use StoreSEO to show me my store's SEO score breakdown.

How does this work in Zed?

You are in Zed with the Agent Panel open next to your theme files, and you ask whether the store has a current llms.txt and a custom agents.md. The agent calls storeseo_start, storeseo_get_llms_txt_status and storeseo_get_agents_md_status. With Zed's default of confirm for tool actions, each of those calls shows an approval prompt before it runs, even though they only read. That is the unusual part of this client: an audit that touches three tools means three clicks before you see an answer.

The prompts become useful once you reach the writes. StoreSEO tells the agent to say what storeseo_generate_llms_txt will do, which is to write a template into your live theme and upload a copy to Shopify Files, and what storeseo_generate_agents_md will do, which is publish live and spend credit. You answer in the panel, and then Zed prompts again when the tool call is about to run. Two checks stack: the one StoreSEO asks the agent for, and the one Zed enforces. The Zed one is the hard stop, because it blocks the call until you click.

You can tune that without losing the stop on writes. Per-tool keys in agent.tool_permissions use the format mcp:storeseo:tool_name, so you can allow the read tools such as storeseo_get_llms_txt_status and storeseo_list_llms_txt_versions and leave generate, activate, delete and reset on confirm. Since Zed is an editor, you can also open the theme's llms.txt template in the next tab and compare it with the active version after a generation, or paste the agents.md text into a project file for a diff.

Zed + StoreSEO Illustrative session

You: Reset my agents.md to Shopify's default.
storeseo_start read-only
storeseo_get_agents_md_status read-only
Zed: A custom agents.md is live. Resetting removes it for good, there is no history to restore from, and Shopify's default serves again within seconds. Reset it?
You: Yes, reset it.
storeseo_reset_agents_md needs approval
Zed: Reset. Shopify's default is serving at your /agents.md. I can generate a fresh custom one whenever you want.

What to ask Zed

Prompt 1

Use StoreSEO to check my llms.txt and agents.md status. Which version is live and is a rebuild due?

Prompt 2

Generate a new llms.txt and tell me what it writes to my theme first. I will confirm in the panel.

Prompt 3

Reset agents.md to Shopify's default, but fetch the current text and save it into this project first.

Is my llms.txt up to date, and which version is live right now?
Generate a new llms.txt that includes products and collections but not blog posts. Warn me before it goes live.
Show me my llms.txt versions and switch back to the one from last week.
Does my store serve a custom agents.md or Shopify's default?
Write an agents.md for my store and publish it. Tell me what it costs first.
Reset agents.md to Shopify's default.

What StoreSEO does: llms.txt and agents.md

llms.txt is a curated map of your store for AI crawlers, and agents.md tells AI shopping agents who you are and how to buy. StoreSEO generates both from your store data and publishes them to your live theme; the agent checks status, generates, switches llms.txt versions and resets agents.md to Shopify's default.

Requires: agents.md generation spends AI Content Optimizer credit and needs at least one published product.

1

Check what is live

The agent reads the llms.txt status (settings, latest version, whether a rebuild is due, public URL) and the agents.md status (custom file or Shopify's default, public URL).
2

Warn before publishing

Generating llms.txt writes a template to your live theme and uploads a copy to Shopify Files in the same run, with no separate publish step. Generating agents.md publishes it live at once and spends credit. The agent says so and waits for your yes.
3

Generate and wait

llms.txt generation takes a minute or two; the agent polls the status until it finishes. agents.md returns the published text and its URL straight away.
4

Manage versions

StoreSEO keeps the latest ten llms.txt versions. The live file serves the active version, which is not always the newest, and any version can be made active again.
5

Roll back

Deleting a version is permanent. Resetting agents.md drops the custom file so Shopify's default serves again, and there is no history to restore it from.

storeseo_get_llms_txt_statusstoreseo_generate_llms_txtstoreseo_list_llms_txt_versionsstoreseo_activate_llms_txt_versionstoreseo_delete_llms_txt_versionstoreseo_get_agents_md_statusstoreseo_generate_agents_mdstoreseo_reset_agents_md

llms.txt and agents.md reference

llms.txt	Generated from your products, collections, pages and posts; served at your store's /llms.txt
Where it is written	A template in the live theme plus a copy in Shopify Files, in the same run
Schedule	llms.txt can regenerate on a saved schedule; settings passed with a run are saved for scheduled runs
Versions kept	The latest ten; the live file serves the active one
Generation time	About one to two minutes for llms.txt
agents.md	AI-written from your brand profile, top products, collections and contact details; served at /agents.md
agents.md publish	Live immediately; replaces Shopify's native default
agents.md reset	Shopify's default serves again within seconds; the custom text is gone for good

Rules Zed follows

The agent tells you that llms.txt generation writes to your live theme before it starts.
agents.md generation publishes live and spends credit, so the agent says both and waits for your yes.
Deleting an llms.txt version and resetting agents.md cannot be undone; the agent confirms each one.
Deleting the active llms.txt version promotes the next newest automatically, so the agent says which version will go live.

In Zed

Zed's default is to prompt before every tool action, reads included, so checking both statuses and listing versions takes several approvals. Allow only the read tools with per-tool keys such as mcp:storeseo:storeseo_get_llms_txt_status and keep the write tools on confirm. Setting agent.tool_permissions.default to allow removes Zed's check, and then the confirmation StoreSEO asks the agent for is the only stop before a live theme write or an irreversible reset, so use allow sparingly for this job.

What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.

Questions

Why does Zed ask me to approve a read of my llms.txt status?

Zed's default tool permission is confirm, which prompts before any tool action, including reads. You can allow the read tools by name with keys in the mcp:storeseo:tool_name format and keep the generate and reset tools on confirm.

Can Zed show me what changed after llms.txt was regenerated?

Yes, in a practical way. After the generation finishes you can ask the agent to open the theme's llms.txt template or fetch the public URL and compare it with a copy you saved earlier, using the editor's own diff tools.

What is the difference between llms.txt and agents.md?

llms.txt is a curated map of your store for AI crawlers and answer engines, served at /llms.txt. agents.md is the file AI shopping agents read to understand your brand and how to shop with you, served at /agents.md. StoreSEO can generate both.

Does generating llms.txt change my theme?

Yes. The same run writes an llms.txt template into your live theme and uploads a copy to Shopify Files. There is no separate publish step, which is why the agent should warn you before it starts.

Can I go back to an older llms.txt?

Yes. StoreSEO keeps the latest ten versions, and any of them can be made the active one, which republishes it to your storefront. Deleting a version is permanent.

Can I undo a generated agents.md?

You can reset it, which makes Shopify's native default serve again within seconds. The custom text is discarded with no history, so keep a copy if you might want it back.