4 ms·
o3/o4 seem to know how to search things like pypi, crates.io, pkg.go.dev etc and apply those changes on the first try. My application (running on an older versi
by hadlock 1y ago
o3/o4 seem to know how to search things like pypi, crates.io, pkg.go.dev etc and apply those changes on the first try. My application (running on an older version of code) had a breaking change to how the event controller functioned in the newer version, o3 looked at the documentation and rewrote it to use the new event controller. It used to be that you were trapped with the LLM being 3-8 months behind on package versions.
- simonw 1y agoHuh, now I'm thinking that maybe a target for release notes should be to provide enough details that a good LLM can be used to apply fixes for any breaking changes.
- rd 1y agoMCP maybe? A release notes MCP (maybe into ReadTheDocs or pypi) that understands upgrade instructions for every package.
- sanderjd 1y agoThis is the thing I don't really love about MCP: Why should it require a separate protocol, rather than just good readable documentation?
- navinsylvester 1y agoIronically, https://context7.com/ https://context7.com/
- sitkack 1y agoThis is devdocs to be consumed by LLMs, https://github.com/upstash/context7 https://github.com/upstash/context7 Brilliant (and one less think I don't have to build)!
- sanderjd 1y agoI'm glad this exists, but can you describe to me why it needs to? Why can't agents just read the docs directly?
- sitkack 1y agoBy returning detailed docs for exactly what the AI is coding at the time, it greatly reduces the the likelihood it will make a mistake. It moves from a recall from the training data problem, to a transcription problem. This is RAG but for API docs.