Replies: 5 comments 9 replies
-
I think I figured it out. If you the phrase: "Output the results to a file", it will put the file in 'auto_gpt_workspace' |
Beta Was this translation helpful? Give feedback.
-
Now I'm starting to get a bunch of JSON parse errors along with this: |
Beta Was this translation helpful? Give feedback.
-
It does seem to try and fix the errors but eventually gives up. But it does continue to press on... It finished. It generated 3 files with minimal output. Not what I was expecting. So... it did create the files and placed them in 'auto_gpt_workspace'. However, the end result leaves much to be desired, but that is beyond the scope of this post. |
Beta Was this translation helpful? Give feedback.
-
Looks like they fixed a lot of the JSON parsing issues last night. After pulling the updates down this morning, it's operating a lot cleaner without so much unformatted JSON in the output. I now suspect that the 'auto_gpt_workspace' is basically a temporary scratch pat for Auto-GPT to use while it's working and that is not the final output. Going by the preloaded data from the pull, the final output file should be in the 'output' directory, and the prior JSON errors were keeping the final output from happening. I'll report back as soon as my latest run finishes. |
Beta Was this translation helpful? Give feedback.
-
I have the same problem. auto_gpt_output seems to have very little of what i expected to find given that it says that it generated the report : This is the final couple of steps (redacted) SYSTEM: Command do_nothing returned: No action performed.
|
Beta Was this translation helpful? Give feedback.
-
I asked it to create a text file with the final output, but I can't seem to find it.
Beta Was this translation helpful? Give feedback.
All reactions