Generating generators #91
Merged
Conversation
This file contains 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
|
Fixes #89 |
|
Related to #63 |
AndrewBKang
reviewed
Aug 30, 2024
| name: "four_digit_passcode", | ||
| description: "an uncommon and difficult to guess four digit passcode" | ||
|
|
||
| llm_output_adapter type: :list_of_named_strings, |
There was a problem hiding this comment.
gonna open an issue for this.
one idea here is that we can create a very flexible output adapter that is as amorphic as (direct translation of) the json shema (essential takes type as a named param and can do so recursively)
it could serve as both a fallback adapter as well as a simple adapter for this kind of use case (prompts)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New CLI command coming!
This new command
sublayer generate generatordrops you into a walkthrough for generating a new sublayer generator for your project.Seeing a longer prompt like this definitely makes me think we need a better abstraction for prompts - this could probably be a good place to look at and experiment with for #75 I think. There are some clear sections that I'd like to break out into methods to build the prompt, a mix of background information, few shot (1 for now) examples, and instructions.
I also had an issue where I was using the same heredoc delimiter in the example and in the code so it blew up when I tried to just inline everything. Gotta be a better way to handle this.
Also ran into an issue trying to integration test this command as running the CLI on a separate thread wouldn't allow VCR to hook into and record the requests. Would love a better solution there to actually testing these commands. Probably need to come up with a mock provider for things like this.
Anywho, this sets the stage pretty well for doing the same thing with Agents and Actions which should come through a lot quicker and be ready for a release very shortly!