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

State management, persistence and resumption #4105

Closed
5 tasks
Tracked by #5178
Boostrix opened this issue May 11, 2023 · 1 comment · Fixed by #5612
Closed
5 tasks
Tracked by #5178

State management, persistence and resumption #4105

Boostrix opened this issue May 11, 2023 · 1 comment · Fixed by #5612
Assignees
Labels
function: state management meta Meta-issue about a topic that multiple issues already exist for re-arch

Comments

@Boostrix
Copy link
Contributor

Boostrix commented May 11, 2023

Objectives 🚀

  • Organize the application state into well-defined components
    • Update: the easiest way to realize this seems to be autogpt.core (Re-arch #4770)
  • Implement a persistence mechanism
  • Implement a rehydration mechanism
  • Allow application state to be exported/transferred
  • Allow resuming a run from any point in the execution history (important for debugging/development)

Note
This issue has been converted to a roadmap item by a maintainer (@Pwuts). Thanks for creating this overview @Boostrix! <3

Original description
meta issue to keep track of everything that's been said in the context of suspending/resuming previous [crashed] agpt sessions - ideally with a capability to resume the agent so that it can validate its known workspace artefacts and use not only any data files it has used previously, but especially any custom files, and especially tools/scripts it may have generated - this implies some fort of dependency tracking (e.g. timestamp between folders/files).

Related

Keywords for people searching: saving, resuming, checkpoint, storing, continuing, serializing, pickle

Motivation 🔦

We need to be able to deal with different forms/types of stateful behavior, for example:

  • the actual goal/objective at hand
  • LLM interpretation
  • local results errors/warnings/success
  • side effects (think file system, directories/files)
@github-actions
Copy link
Contributor

github-actions bot commented Sep 6, 2023

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

@github-actions github-actions bot added the Stale label Sep 6, 2023
@Pwuts Pwuts moved this to Todo in AutoGPT Roadmap Sep 8, 2023
@Pwuts Pwuts self-assigned this Sep 8, 2023
@Pwuts Pwuts added this to the v0.5.0 Release milestone Sep 8, 2023
@Pwuts Pwuts moved this to 🚧 Needs work in AutoGPT development kanban Sep 8, 2023
@Pwuts Pwuts changed the title [WIP] Checkpointing / Persistence / Serialization State management, persistence and resumption Sep 8, 2023
@Pwuts Pwuts mentioned this issue Sep 8, 2023
3 tasks
@Pwuts Pwuts linked a pull request Sep 8, 2023 that will close this issue
5 tasks
@github-actions github-actions bot removed the Stale label Sep 9, 2023
@Pwuts Pwuts moved this from Todo to In Progress in AutoGPT Roadmap Sep 9, 2023
@Pwuts Pwuts moved this from 🚧 Needs work to ⏩ In Progress in AutoGPT development kanban Sep 10, 2023
@Pwuts Pwuts added the meta Meta-issue about a topic that multiple issues already exist for label Sep 14, 2023
@Pwuts Pwuts linked a pull request Oct 17, 2023 that will close this issue
9 tasks
@github-project-automation github-project-automation bot moved this from ⏩ In Progress to ✅ Done in AutoGPT development kanban Oct 18, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in AutoGPT Roadmap Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
function: state management meta Meta-issue about a topic that multiple issues already exist for re-arch
Projects
Status: Done
Archived in project
3 participants