This repository was archived by the owner on Apr 14, 2025. It is now read-only.
docker-optimizer: complete rewrite with a smaller prompt and smaller toolset#20
Merged
Conversation
…toolset Signed-off-by: Sam Alba <216487+samalba@users.noreply.github.com>
Signed-off-by: Sam Alba <216487+samalba@users.noreply.github.com>
Signed-off-by: Sam Alba <216487+samalba@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a complete rewrite of the initial implementation of the dockerfile-optimizer agent.
The new version implements a better pattern that aims for better results in the optimization, leaving less control to the LLM, reducing the randomness in result. There is a simple eval done with
wagoodman/diveto assess the Dockerfile optimization and calling the LLM in a loop as needed.This also shows a better example of leveraging the Dagger API while calling the LLM only when needed (which also has access to the API via the Workspace).