[Feature request] Adding url of documentation and being able to reference it
Resolved 💬 3 comments Opened Aug 6, 2025 by MauScheff Closed Oct 7, 2025
I've found that sometime when I'm using the latest version of a tool I manually have to go
and read the docs and tell codex that there is a better / new way, sometimes codex insisting
on doing it the old way (based on training), technologies are evolving all the time and we
want to use the latest versions when writing new code, would there be a way to point codex
to that documentation url and having it lookup without slowing it down too much?
3 Comments
If by tool, you mean library/framework/language,etc and their documentation - you could just use context7 MCP. It's made for exactly this. You could also try Cole Medin's Crawl4AI-Rag-MCP though it's not as versatile as context7. They both solve the same problem, just in slightly different ways.
@Shaurya-Sethi that seems like a pretty good idea, however, I'm wary of third-party MCP servers because, as I understand, they open up the security vulnerability surface, some of this attack vectors we still don't know of. I think if every library/framework/language offered their own official MCP server to access their documentation, I may be more willing to take the risk. But wouldn't it also be great if we could include URLs in prompts so that the agent knows that it can call a tool to fetch it and understand it and maybe cache it somehow? That would be simpler both for the tools and the users, and more versatile too. I'm thinking something similar to Vertex AI's URL context. But that we could somehow, in an ideal case, include the URL of a new tool in AGENTS.md and codex could like fetch / crawl, get what it needs and cache it locally or something so it's not doing it on every call.
I saw that in the latest cli there is
--searchI guess this can solve this? Any good patterns for using search to provide a url with documentation, for example on a latest release of an API?