You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a recent trend for libraries to provide a file that contains enough context about the library for an LLM to be able to act as an assistant for using that library. The idea behind it being a file is that you can provide it to any LLM that supports such an import, and it also makes distribution very easy.
In our case we'd probably build it in the "push to docs-latest" job, and have a button somewhere on our website to download it.
There are some tools that can generate such an export, which we should try out. One such example is repopack.
If none of the available tools are suitable, we'd have to develop something on top of the existing search index build infrastructure. The LLM would likely want a lot more information about the available symbols, their fields/parameters/return types, all the doc comments, full import paths per-language, etc., plus all our examples/snippets. We could limit it to Python-only in the MVP.
The text was updated successfully, but these errors were encountered:
There's a recent trend for libraries to provide a file that contains enough context about the library for an LLM to be able to act as an assistant for using that library. The idea behind it being a file is that you can provide it to any LLM that supports such an import, and it also makes distribution very easy.
In our case we'd probably build it in the "push to docs-latest" job, and have a button somewhere on our website to download it.
There are some tools that can generate such an export, which we should try out. One such example is repopack.
If none of the available tools are suitable, we'd have to develop something on top of the existing search index build infrastructure. The LLM would likely want a lot more information about the available symbols, their fields/parameters/return types, all the doc comments, full import paths per-language, etc., plus all our examples/snippets. We could limit it to Python-only in the MVP.
The text was updated successfully, but these errors were encountered: