Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move history to the flow #122

Merged
merged 1 commit into from
Jun 17, 2024
Merged

Move history to the flow #122

merged 1 commit into from
Jun 17, 2024

Conversation

jlowin
Copy link
Member

@jlowin jlowin commented Jun 17, 2024

moves history object storage from the controller (which is not user facing) to the flow (which is). This has a few benefits:

  • users can specify different history objects for different flows (previously had to set a global default for the controller to load)
  • direct history manipulation becomes possible
  • subflows can inherit the parent flow's history, but create a branch to avoid modifying it. This means that you can create a subflow to let agents confer privately, without polluting the parent thread, while still having full access to its information

@jlowin jlowin merged commit 7809e9b into main Jun 17, 2024
1 of 4 checks passed
@jlowin jlowin deleted the history branch June 17, 2024 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant