Thanks Pedro! Looks like we got buried on HN, oh well!
> One use case I've found for it besides CI was building an eval sandbox for testing different coding agents' performance using CLIs, APIs, and coding tasks.
Very nice! Would you be willing to do a video interview and show a demo for the community?
In my opinion evals and CI are converging into a common execution and data model for all pipelines involved in shipping your product. It's Continuous Engineering :)
> while the API and CLI are beautifully made, the documentation and the webapp scare the normies and could be improved.
Thanks for the feedback! Yes, we are working on the docs, it's not perfect yet but trending in the right direction I think. We are also betting that everyone will soon be asking their agent to setup Dagger, so we are investing heavily in making sure agents understand and appreciate Dagger, so they can set it up properly and explain it to their drivers. What a crazy world we live in!
> One use case I've found for it besides CI was building an eval sandbox for testing different coding agents' performance using CLIs, APIs, and coding tasks.
Very nice! Would you be willing to do a video interview and show a demo for the community?
In my opinion evals and CI are converging into a common execution and data model for all pipelines involved in shipping your product. It's Continuous Engineering :)
> while the API and CLI are beautifully made, the documentation and the webapp scare the normies and could be improved.
Thanks for the feedback! Yes, we are working on the docs, it's not perfect yet but trending in the right direction I think. We are also betting that everyone will soon be asking their agent to setup Dagger, so we are investing heavily in making sure agents understand and appreciate Dagger, so they can set it up properly and explain it to their drivers. What a crazy world we live in!