spacedriveapp / spacedriveapp/spacebot
bug: bot forgets / disregards preferences in "Knowledge Context"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.4k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
Requirement: The user "preference" memories should be of higher priority for the LLM. Here is why:
I have made the bot create a memory "User wants every response to include a summary of operations performed as the last part." in Knowledge Context but it does not follow it. (see screen-shots). So what is the value of "Knowledge Context" if the bot does not use it anyway and tells me to write memories to ROLE.md !? The whole purpose of the memory system is for the bot to use it, isnt it? Maybe session instcutions should be changed for the LLM to prioritize and always follow "preference" memories.
Memory entry:
Chat: (I have made the bot reread the memories. Only after that it started to follow the preferences):
Contributor guide
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
Start by reproducing the behavior with a preference memory in Knowledge Context, then compare a normal response with one after the bot rereads its memories. Read the session instructions and memory-handling flow mentioned in the report; done means preference memories are consistently followed without requiring a reread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100