#github.com/dagger/agents => not merging into github.com/dagger/dagger

1 messages · Page 1 of 1 (latest)

harsh field
#

I updated the PR: https://github.com/dagger/dagger/pull/9726

Now the whole dagger/agents repo is merged at ./agents, with history preserved.

Fun fact, this repo migration was automated by a 15 line Dagger function 🙂

github.com/shykes/dagger/agents@agents | .help migrate
#

adding @late jolt @indigo zealot @neon lake @surreal stump @sharp lagoon for finishing touches tomorrow

harsh field
#

Quick checkpoint on this:

  1. We're not merging the agents directory. README & docs only. All modules should spin out to their author's respective repos, just like any other modules. Make sure they are well documented & up to date! We will link to them

  2. I will try to get the main README to consensus (questions of balance between CI & AI use case etc)

  3. We're going to add content to the docs right away, as part of this PR. @sharp lagoon is doing the first pass.

  4. We are explicitly careful not to cross the "rabbithole line" - where the rewards of better integrating the CI & AI content is not worth the effort at this time.

  5. When README is stabilized, we will sync it to docs intro page, as part of the same PR (fyi @vernal grotto )

  6. Goal is to merge today

sharp lagoon
harsh field
#

we have well-defined jurisdictions so conflicts shouldn't be an issue 🙂

sharp lagoon
# harsh field yeah just push to the branch

pushed, going to wait for a preview environment to verify a few things. Mostly the links to the examples will need to be updated. Pretty sure some are from @late jolt and will live on his repository - but the new structure is done going to fine tooth the content and make sure everything is 💯 from the changes

sharp lagoon
harsh field
#

@sharp lagoon I'm going to nuke my branch and start clean, with your 2 commits cherry-picked

#

(I see 2 commits so far)

#

@sharp lagoon done, had to force push

#

btw @sharp lagoon you can run a review env locally 🙂

github.com/shykes/dagger@agents | docs | server | up
harsh field
#

Update: I'm getting close on README

#

@sharp lagoon is your side mergeable as-is?

sharp lagoon
sharp lagoon
sharp lagoon
#

@harsh field pushed some changes. Updated the tutorial on developing AI agents since the modules are no longer relative. I also removed some examples but thinking maybe I should re-add them but link to the dagger/agents repo since they will still work?

Edit: I added them with a link to dagger/agents because I think those were great examples to keep

indigo zealot
#

🙏

harsh field
#

Thanks!

#

Yeah, I think for now we can link to the modules where they are currently (including dagger/agents)

Then as we gradually spin out modules from dagger/agents (which I think we should, to avoid creating 2 separate points of entry), we can update the links

harsh field
#

@indigo zealot I think midwest / east coast crew is out. Ready for the final push?

#

On the docs I was going to ask for small title tweaks

#

on my end, finishing touches on formatting, then pushing README for review

indigo zealot
#

Let's do it!

harsh field
#

@indigo zealot do we have the ability to redirect broken links, if needed?

#

I'm thinking the "CI quickstart" should move to docs.dagger.io/ci/quickstart but that would break /quickstart

indigo zealot
harsh field
#

I think we did a big pass of those redirects as part of daggerize-the-world?

indigo zealot
#

did one recently

#

testing

#

@harsh field I see, move all of this under Dagger for CI under /ci, eh?

image.png
#

and redirect /quickstart, etc

harsh field
#

if not too hard, yeah, will feel more consistent

indigo zealot
#

cool, docs suggest it's this in the netlify.toml

[[redirects]]
  # redirect /quickstart pages to CI-specific ones
  from = "/quickstart/*"
  to = "/ci/quickstart/:splat"
  status = 301
#

will do same for Integrating with CI and Adopting Dagger (aka Day 2)

#

turns out makes most sense to move ALL the integrations under ci for now. Since all of them are in there include the CI ones as the bulk, or...might split...we'll see

harsh field
#

@indigo zealot can you make the following title renames:

  • "Adopting Dagger" -> "Dagger for CI: Day 2"
  • "Quickstart" -> "Dagger for CI: quickstart"
#

I'm going to go ahead and synchronize the docs intro with README

indigo zealot
#

fixing some many relative links. done

indigo zealot
#

got some commits for your agents branch @harsh field good to push there?

harsh field
indigo zealot
harsh field
#

Oh man docs are about to get so much better 🙂

# 
### SDKs

Dagger SDKs provide resources for developing Dagger modules using a familiar language and toolchain. Each SDK provides:

1) A *client generator*, to *consume* Dagger types with native code.
2) A *server generator*, to *extend* Dagger types with native code.
3) Examples and reference documentation
#

We have accumulated so many insights in how to explain Dagger. Going to cash some of that in

harsh field
#

@indigo zealot quick feedback on docs preview;

Quickstart

  • In the navbar: could just be "Quickstart" since it's very visibly nested
  • In the title: should be "Dagger for CI: Quickstart" for the inverse reason (could be ambiguous otherwise)

Day 2

  • Navbar: should just be "Day 2" for the same reason as above
  • Title: "Dagger for CI: Day 2" for consistency

IMO

indigo zealot
#

cool. easy

harsh field
#

@indigo zealot I just pushed also

#

Trying a mermaid diagram, have to "push and pray" it

indigo zealot
harsh field
#

I think I got them

#

then had to force push

#

sorry

#

can you check I didn't wipe anything?

# 
commit 36b14f6334aa9f6bc2076c0324370923fd6ae0cb (HEAD -> agents, origin/agents)
Author: Jeremy Adams <jeremy@dagger.io>
Date:   Fri Feb 28 17:47:37 2025 -0800

    docs: naming consistency quickstart/day2

    Signed-off-by: Jeremy Adams <jeremy@dagger.io>
#

latest commit? 👆

indigo zealot
#

I saw your shame!! 😆 (I was sure I'd broken the build 😅 )

/src/docs/current_docs/index.mdx"
Cause: Expected a closing tag for `<img>` (31:227-31:285) before the end of `paragraph`
harsh field
#

yeah it's stupid, github markdown renders the same img tag without problem.

#

@indigo zealot that svg is the best asset we have for now

#

will swap it out when we get something better

#

@indigo zealot merge?

indigo zealot
#

maybe like this

- **LLM augmentation**. Connect to any LLM endpoint (OpenAI, Google, Anthropic, LLama, DeepSeek, etc.) and give it access to your Dagger objects. Dagger automatically handles the agentic loop. No complicated framework needed.
<p align="center">
  <img src="docs/static/img/spider-robot-1.svg" width="15%">
</p>
image.png
#

just noticed I should change from Introduction to Dagger for CI here

image.png
#

Making sure some of my changes weren't lost in the force push.

#

All good.

I think we can fix this guy up the same way by going to next line

image.png
sharp lagoon
#

back at the computer after doing remote grandma IT support 😓 - anything I can help with?

indigo zealot
#

I can push the image changes @harsh field if you're ok with next line style

harsh field
#

going to fix the img

#

turning my attention to CI errors...

indigo zealot
#

cool

sharp lagoon
#

man, the images are 🔥!

harsh field
#

Here's a sneak preview of the next one. The goal is to be the counter-point to the "50 crazy people memes" from my presentation

image.png Screenshot_2025-02-28_at_18.27.16.png
#

@indigo zealot heads up I'm going to squash some of my commits, then force push

indigo zealot
sharp lagoon
#

Maybe add Kyle's repo in the examples?

#

I'll add it and Sam's as well if thats ok

indigo zealot
#

It's on first page, right? Prob just wait for the force push, pull and go 🙂

harsh field
#

force push done

#

Oh I have to rebase on main also

#

hold your pushes

#

force-pushed

indigo zealot
harsh field
#

removing draft status

indigo zealot
#

Just pushed my last change for now.
@sharp lagoon if you want to pull and push

harsh field
#

also pushed small change

#

trying to pass docs linter

sharp lagoon
#

pushed up some more examples

indigo zealot
#

🤩

sharp lagoon
#

🎉

indigo zealot
#

✅

#

all green

harsh field
#

I may have tweeted the link to this PR 🙂 https://x.com/solomonstre/status/1895671390176747682

Solomon Hykes (@solomonstre) on X

This is blowing up. It looks like building Dagger from first principles is paying off.

Dagger is a runtime for composable workflows. Sure it's great for CI. But it turns out AI agents also need more repeatable, modular and observable workflows - very badly! So here's the plan🧵

X ·
#

OK merging

indigo zealot
#

dinner time! Great working with y'all!!! 🙌

harsh field
#

THANK YOU!

indigo zealot
#

Going to publish

harsh field
indigo zealot
harsh field
#

good catch

surreal stump
#

Should we send the banner on the home page to the new docs page now?

indigo zealot
#

👆 @vernal grotto
I just changed the link and reckon I could hit publish, eh?

indigo zealot
indigo zealot
#

Could add hyperlinks for "AI agents" and "CI/CD" though it's in the sidebar.

image.png
vernal grotto
indigo zealot
#

for anyone worried 🙂 we got it sorted. It was live, but now it's ALIVE! 😉

harsh field
#

one remains problem is that the twitter thread points to dagger/agents and that README duplicates our new content

harsh field
#

Update: I'm going to quickly trim the content from dagger/agents. I have a few minutes in between personal chores

harsh field
neon lake
indigo zealot
#

cc @late jolt 👆

#

wonder if I can just change dep to ../toy-programmer/toy-workspace and dagger develop

late jolt
indigo zealot
harsh field
#

sorry I didn't realize others imported toy-workspace directly!

indigo zealot
#

my prob was the casing fix for TypeScript too!

-      .ToyWorkspace();
+      .toyWorkspace();
#

going to module style 👍

"dependencies": [
     {
       "name": "toy-workspace",
-      "source": "../toy-workspace"
+      "source": "github.com/dagger/agents/toy-programmer/toy-workspace",
+      "pin": "7ed02cb9dfdcf491b538984d83d8b1749a5cca11"
     }
   ]
#

Was pretty delightful as this went by in the Shell @neon lake with syntax highlighting!! 🤩

image.png image.png
neon lake
#

side note: maybe we should set up CI for the AI agents, would be kind of cute to show both use cases at once, and see variance in model performance over time

indigo zealot
#

@harsh field not sure if either of us can merge fixes/updates to dagger/agents, or what current repo etiquette is around our own content. @neon lake if you're around, can you give this a 👍 and I can try to merge it. That way folks who try it aren't broken. done! ✅

harsh field
#

@indigo zealot i would just go for it

#

do you have permissions?

indigo zealot
harsh field
#

weird

#

on it

#

@indigo zealot should be fixed. I had added all dagger team, but accidentally read only

indigo zealot
harsh field
indigo zealot
indigo zealot
# late jolt yeah that should do it I think

I fixed the path your mult-agent example Kyle, super simple style so it's not broken. Will let you decide if you switch to git ref style later.

"dependencies": [
     {
       "name": "toy-workspace",
-      "source": "../toy-workspace"
+      "source": "../toy-programmer/toy-workspace"
     }
   ]

cc @neon lake thanks for reporting!

tested with
demo --chat-model gpt-4o --coder-model gpt-4o

image.png
late jolt