Launching github.com/dagger/agents | Dagger | Page 1

fervent bluff Feb 21, 2025, 9:23 PM

#

@gaunt arrow @serene glade @lime phoenix @vestal cliff @eager girder

#

Here's the plan:

TLDR: move shykes/melvin to dagger/agents, make it the one-stop-shop for everyone interested in building Agents on Dagger.

Tasks:

Edit melvin README to fit the new repo @fervent bluff
Transfer shykes/melvin to dagger/agents
Merge @lime phoenix 's ollama section of the README
@gaunt arrow @serene glade @woeful trail contribute their example modules to the repo (exact path tbd)
Call to action for everyone interested becomes: "visit github.com/dagger/agents"

gaunt arrow Feb 21, 2025, 9:28 PM

#

Ideally I'd like to avoid the case of dumping all of my demos to dagger/agents/kpenfound/foo. Any other proposed structures?

#

completely flat will probably too confusing but i could be wrong

fervent bluff Feb 21, 2025, 9:29 PM

#

yeah. I think namespacing by username is too much. But we can namespace by "mini-project", and each project has its own README + collection of modules?

serene glade Feb 21, 2025, 9:29 PM

#

figure you could do steps 1 and 6 first

fervent bluff Feb 21, 2025, 9:30 PM

#

serene glade figure you could do steps 1 and 6 first

Well I want to do a first pass on the README so that at least it doesn't say "this is melvin". But will timebox aggressively

#

1 and 6 -> agree

gaunt arrow Feb 21, 2025, 9:30 PM

#

fervent bluff yeah. I think namespacing by username is too much. But we can namespace by "mini...

each project definitely needs it's own readme. Namespacing by mini-project / standalone demo makes sense but we should also summarize them in the top level README

fervent bluff Feb 21, 2025, 9:31 PM

#

--> simplified the task list 🙂

#

@gaunt arrow would you have only one mini-project? Or more?

#

I think I'll keep mine under examples/melvin

gaunt arrow Feb 21, 2025, 9:32 PM

#

I have:

multiagent already in melvin
go-coder which is like advanced toy-programmer
github-agent that does the automated webhook flow with go-coder

#

and I'd rename them to something that's easier to understand in dagger/agents

fervent bluff Feb 21, 2025, 9:38 PM

#

are any of these multi-module, or each is a single module?

#

maybe the right approach is to have a top-level module, and sub-modules if needed?

#

(in the case of melvin, I never got around to it, but it would make sense for toy-programmer to be a top-level, and toy-workspace to be its sub-module. Those two are self-contained, could be their own thing

lime phoenix Feb 21, 2025, 9:40 PM

#

https://github.com/shykes/melvin/pull/7

fervent bluff Feb 21, 2025, 9:40 PM

#

Then separately, I have workspace + github-notifier + reviewer + small parts of demo (which needs to be broken up anyway). I could move that to melvin, or we could try to merge it and go-coder?

eager girder Feb 21, 2025, 9:52 PM

#

gaunt arrow each project definitely needs it's own readme. Namespacing by mini-project / sta...

+1 to this. Could we have a readme template so people can easily copy and paste to start their own? Kinda like the docs integration page template that Lev created?

lime phoenix Feb 21, 2025, 9:53 PM

#

lime phoenix https://github.com/shykes/melvin/pull/7

updated, re-ready for review

fervent bluff Feb 21, 2025, 10:19 PM

#

Getting a little stuck on the first paragraph of the new README... 😅 "Dagger is..."

#

(melvin readme avoided that trap)

serene glade Feb 21, 2025, 10:23 PM

#

fervent bluff Getting a little stuck on the first paragraph of the new README... 😅 "Dagger is...

https://github.com/jpadams/cypress-test-llm-ts/blob/main/README.md

#

Helpful at all?

#

Wait…no what is Dagger there really 🤣 sorry

eager girder Feb 21, 2025, 10:33 PM

#

fervent bluff Getting a little stuck on the first paragraph of the new README... 😅 "Dagger is...

Can't we skip that, and just say " This repo contains examples of how to use Dagger for agent use cases. Check them out to learn how to build your own, and join us on Discord".

This repo will be in the Dagger one, so they will get to our old Dagger readme that won't match anyways.

topaz hatch Feb 21, 2025, 10:41 PM

#

fervent bluff Getting a little stuck on the first paragraph of the new README... 😅 "Dagger is...

Use this for now:

Dagger provides the execution layer for AI agents — a programmable workflow engine that lets agents dynamically compose and run complex actions in container-native, reproducible environments. Instead of relying on hardcoded API calls or brittle scripts, agents can use Dagger to execute workflows on demand, scaling seamlessly across local, cloud, and edge environments.

With Dagger, AI agents can:

Go beyond API calls: Run real-world tasks inside secure, containerized environments.
Orchestrate tool use dynamically: Let agents compose and execute workflows at runtime.
Eliminate execution failures: Ensure workflows are reproducible and portable across environments.

fervent bluff Feb 21, 2025, 11:09 PM

#

OK finally done with a first pass (sorry @topaz hatch had missed the above - but can integrate it)

#

pretty compatible

#

merging @lime phoenix 's PR then pushing my change

#

then transfer

#

cutting it very short!

#

merged, pushed

#

not perfect but good enough for now

#

transfering

#

#

@serene glade FYI

serene glade Feb 21, 2025, 11:19 PM

#

https://github.com/shykes/melvin -> https://github.com/dagger/agents

#

fervent bluff Feb 21, 2025, 11:27 PM

#

Looks like it worked

#

OK switching to emergency packing + demo mode

woeful trail Feb 25, 2025, 5:24 PM

#

@fervent bluff should I also contribute the deployment process of the agent along with its frontend? (the go API that receives the webhooks)

#

this involves packing the engine and the API on a container, shipping it to fly and calling the agentic module using graphql from the Go code

gaunt arrow Feb 25, 2025, 5:37 PM

#

I didn't for my github webhook module since the webhook side of it is not showcasing the agent module itself, it's just calling it

#Launching github.com/dagger/agents