#where are api references for llm modules?

1 messages ยท Page 1 of 1 (latest)

hazy elm
vocal zenith
hazy elm
#

aha. thanks. will look forward to the release. I suspect WithToyWorkspace() is also some type of generics api that can be applied to user-supplied data type?

vocal zenith
#

Yes, the static part of the LLM type is very small.

The "magic" comes from introspecting all available types (including from installed modules, like ToyWorkspace) and adding a setter and getter function for attaching them to the LLM state

#

So you can develop your own JCSuperModule; then LLM will magically have LLM.withJCSuperModule() and LLM.JSCuperModule()

hazy elm
#

got it. very cool. thanks for clearing that up.

vocal zenith
#

It also works with core Dagger types ๐Ÿ™‚ For example:

dagger <<EOF
SRC=$(git https://github.com/dagger/dagger | head | tree | directory ./docs)

llm | with-directory $SRC | with-prompt "you have access to a directory. Inspect its contents to determine what software project it is part of. Search for all .mdx or .md files, summarize them in 1 paragraph max, and write the summary to SUMMARY.md" | directory | terminal
EOF
#

or:

dagger <<'EOF'
llm | with-container $(container | from alpine) | with-prompt "you have access to a container. Install everything needed to develop in Python" | container | publish ttl.sh/my-python-dev-container
EOF
hazy elm
hazy elm