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

Theres no meta data in the memories #3451

Closed
1 task done
philliplastcall opened this issue Apr 28, 2023 · 3 comments
Closed
1 task done

Theres no meta data in the memories #3451

philliplastcall opened this issue Apr 28, 2023 · 3 comments
Labels
AI model limitation Not related to AutoGPT directly. function: memory Stale

Comments

@philliplastcall
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?

Linux

Which version of Auto-GPT are you using?

Stable (branch)

GPT-3 or GPT-4?

GPT-3.5

Steps to reproduce 🕹

def add(self, data):
vector = get_ada_embedding(data)
### # no metadata here. We may wish to change that long term.
self.index.upsert([(str(self.vec_num), vector, {"raw_text": data})])
_text = f"Inserting data into memory at index: {self.vec_num}:\n data: {data}"
self.vec_num += 1
return _text

Current behavior 😯

it gets stuck in loops because it thinks failed repeated attempts are relevant and therefore should be tried again and again

Expected behavior 🤔

know he difference between good and evil...hell i'd take the difference between pass ad fail

Your prompt 📝

# Paste your prompt here

read important_info.txt

Your Logs 📒

it rolls down alone or in pairs, everyone wants a 
@Boostrix
Copy link
Contributor

Boostrix commented May 3, 2023

it gets stuck in loops because it thinks failed repeated attempts are relevant and therefore should be tried again and again
know he difference between good and evil...hell i'd take the difference between pass ad fail

for that to work, an outer/parent agent would need to be able to look at the objective in question and the state (log file) and output (files) of the sub-agent. I started doing some early experiments related to this: #3593 (comment)

The idea here would be split up objectives into "atomic" steps, whose completion status is logged to disk - so that the agent/task manager can observe progress (or lack thereof, to keep the loop running).

I am hoping, that in conjunction with hashing agent state, this could also be used to detect redundant looping, as per: #3668

@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 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AI model limitation Not related to AutoGPT directly. function: memory Stale
Projects
None yet
Development

No branches or pull requests

3 participants