You know the image exists. You uploaded it, you can picture it, and you have no idea what it is called. The media library gives you a search box that, until recently, only looked at titles, and nobody edits the title of an uploaded image. So you scroll.
The 1.7.4 media search fixed the thing that made this frustrating. It now matches the filename and the alt text as well, which is where the real detail about an image actually lives. This prompt uses that, and it changes nothing.
I am looking for an image in the media library and I only half remember it.Read only, change nothing.
Search the library for [conference]. The search matches filenames and alt textas well as titles, so try the fragments I can actually remember: bits of thefilename, and words someone would plausibly have written in the alt text.
If the first search comes back thin, try [2024] and [keynote] as separatesearches rather than giving up.
For anything that looks close, read the item in full and tell me its caption,its dimensions, its file size, and what it is attached to. Then give me yourbest match with its URL and id.
List the near misses too, with one line each on why you ruled them out. I wouldrather see a wrong guess than be told there is nothing.Why this is safe to run
Both abilities are reads. The list returns matching items with their URL, alt text, mime type, and dimensions plus the full match count; the single-item read opens one attachment for its caption, description, date, filesize, parent, and image sizes. Neither can rename a file, rewrite alt text, or delete anything.
The reason this works better than it used to is worth being precise about. Before 1.7.4, media search went through core’s standard search parameter, which matches the post title. An uploaded image inherits its title from the filename and then nobody touches it again, so the searchable text was whatever the file happened to be called at upload, and only that. From 1.7.4 the search also matches the stored filename and the alt text. Alt text is the useful half: it is written by a person, describing what is actually in the picture, for accessibility reasons that have nothing to do with search. Now it is searchable too.
Ask for the near misses as well. A search that comes back empty tells you very little, since the image might not be there or your fragment might simply be wrong. Three wrong images tell you the library is being read properly and your guess needs adjusting.
Already connected? Skip the paste. Ask your agent for the “find an image by its filename or alt text” recipe, describe what you remember, and it runs the same reads against your own library.