RedPlanetHQ / RedPlanetHQ/core
BUG: Unable to delete/update stale or erroneous memories.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 194
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
I am trying to assign tasks via the butler to clean up old/stale memories and at first it was creating the tasks for me, but they would stall, never complete.
Then the butler stated I need to assign them write/delete access in order to complete the task, but there is no option I can see to extend/customize the butlers or task runners permissions.
Is this an oversight? The ability to clean up old/stale memories that potentially cause conflict when injected back into current conversations is pretty important.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the report. Start by reproducing a Butler task that attempts to update or delete a memory, then trace how Butler or task-runner permissions are configured and identify what prevents the operation. Done means stale memories can be updated or deleted through the supported task workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100