Conversation
awadell1
force-pushed
the
think_plan_execute
branch
from
August 11, 2026 18:43
912fe0b to
80846be
Compare
awadell1
force-pushed
the
think_plan_execute
branch
from
August 11, 2026 19:16
80846be to
e63c6b1
Compare
…ing for the async close
This branch has not been deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adding the Hypothesie-Plan-Execute workflow. It's very much WIP and not really integrated into WorkflowBase
It's also playing with the workflow as a graph only (instead of a class). Which idk if it's a good idea or not, but it does make things cleaner. More discussion is needed on what a workflow should look like before merging