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

AutoGPT overwrites same text file with each action instead of appending to the end. #4384

Closed
1 task done
johnjac-cisco opened this issue May 24, 2023 · 7 comments
Closed
1 task done
Labels
bug Something isn't working function: fileops Stale

Comments

@johnjac-cisco
Copy link

⚠️ Search for existing issues first ⚠️

  • I have searched the existing issues, and there is no existing issue for my problem

Which Operating System are you using?

Docker

Which version of Auto-GPT are you using?

Latest Release

Do you use OpenAI GPT-3 or GPT-4?

GPT-4

Which area covers your issue best?

Challenges

Describe your issue.

The task was to give a detailed explanation of something, and auto-gpt broke the task in to several "writing sections" but instead of appending each section to the text file, it over wrote each time
activity.log

Upload Activity Log Content

No response

Upload Error Log Content

No response

@W3Warp
Copy link

W3Warp commented May 26, 2023

This has to with STM not contain enough context, in other words agpt has forgotten why its doing what its doing. One possible workaround is to have more detailed goals and role. Where core concepts remain in STM as they are viewed as crucial to function according to AutoGPT. This is my experience anyway.

@Boostrix
Copy link
Contributor

Boostrix commented Jun 3, 2023

you can also tell it explicitly not to overwrite existing files - also see the update_file PR: #3643

@lc0rp lc0rp added bug Something isn't working function: fileops labels Jun 8, 2023
@bishi3000
Copy link

There are quite a few ways to solve this issue. IMO the current implementation is quite prone to loosing the context of what it is currently doing (or was just doing).

If using simple files is the desired storage mechanism (as opposed to a document DB for example) then, maybe a scheme such as writing into a folder names by a session ID, or creating filenames with a session ID suffix, where the 'session ID' relates to the current task.

This would also help for cleanup of files afterwards

@W3Warp
Copy link

W3Warp commented Jun 15, 2023

There are quite a few ways to solve this issue. IMO the current implementation is quite prone to loosing the context of what it is currently doing (or was just doing).

If using simple files is the desired storage mechanism (as opposed to a document DB for example) then, maybe a scheme such as writing into a folder names by a session ID, or creating filenames with a session ID suffix, where the 'session ID' relates to the current task.

This would also help for cleanup of files afterwards

#3536 (comment)

@Boostrix
Copy link
Contributor

There is also the update_file PR which contains related discussions

@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
@github-actions
Copy link
Contributor

This issue was closed automatically because it has been stale for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working function: fileops Stale
Projects
None yet
Development

No branches or pull requests

5 participants