#I'm happy with a raw graphql query if it
ashen creek
Can you clarify what you're trying to achieve? To make sure I give you a useful answer
uncut ore
Sure, I'm currently building an agent that needs host access – therefore going for the "custom application" a go binary that depends on the dagger host.
Inisde this agent I want to perform tool calls as I do with the dagger functions – for example like the workspace that you've built for the melvin agent.
I don't want to re-impelement those tools instead I would love to consume them as dagger modules from the daggerverse
the agent is concepted as a running service on a vm that receives a kafka message and starts building. – so a long lived service
ashen creek
Do you plan on using Dagger's LLM client for this agent?
Or are you trying to reimplement it on your end basically
uncut ore
no I would love to use daggers LLM client – my current prototype is a go binary that just shells out to the dagger call:
but I need to provide mor args and was looking into if I can still use daggers LLM client but from within a custom application
That's currently the dagger function I'm calling:
ashen creek
I see, and the fact that the LLM client can only call tools which bind to Dagger objects (and therefore no host access) is not an issue? I guess the part of your app that needs host access is in another part of the code?
uncut ore
yep that's not an issue the other parts of the app (surroundings need host access)
the llm just should operate inside the containerized workspaces provided
ashen creek
Ideally you would use this feature, I think: https://github.com/dagger/dagger/issues/9582
Unfortunately it's not fully implemented yet
But if you want to give it a try, there is a POC hidden in latest Dagger CLI release: dagger client --help
Otherwise for the safer "raw http/graphql" route: https://docs.dagger.io/api/http
To get a raw graphql client from your Go code:
dag, _ := dagger.Client(ctx)
gc := dag.GraphQLClient()
oh the proposal looks exactly what I'm looking for! Super promising – stoked to see this hopefully coming soon 🤞
I've already looked at the "safer graphql" way but could not find how do the llm part like I do here:
uncut ore
To get a raw graphql client from your Go code:
```golang
dag, _ := dagger.Clien...
oh this should help getting the graphql
Thanks will give it a try!
Can I use this in a dagger function to see how the dagger function is constructed as graphql query?
dag, _ := dagger.Client(ctx)
gc := dag.GraphQLClient()