Skip to content

Should there be a Standard for memory banks? #40

@rhysburnie

Description

@rhysburnie

Hello,

This is not a bug and I know its not Roo Code teams responsibility.
But given the openness of Roo Code and popularity I feel like it could be a good driving force for a standard.

Currently each platform seem to have their own take even tho they are all quite similar

Often they have the same file setup etc but with most the differences being entry points:

  • Cline has .clinerules
  • roo code has entry via the mode-specific custom instructions field
  • clause has CLAUDE.md chain and .claude folders
  • cursor has .cursor
  • it goes on for others

It would be so great if there was a universal standard something like:

./assistant
./ASSISTANT.md

(or whatever universal name even .ai ?)

In the case of roo code the entry point via mode-specific custom instructions field could just state:

Memory Bank

  • @ASSISTANT.md or a memory-bank specific file

Currently I have a setup of

CLAUDE.md (instructs where the memory bank instructions and memory-bank location is)
.claude
  claude-code-memory-bank (as submodule that instructs what memory bank is and how it works)
  memory-bank

And I told Roo where it is and it says it understands, im just worried it may potentially end up in disaster.

How nice would it be to be able to switch between systems etc and have a consistent memory bank in one place?

Maybe the reason they are all different is to lock user in, but I feel like if a popular solution like Roo Code could create/adopt a universal standard it might gain traction with the others.
At the very least I have seen its quite common for people to use roo/clien/cursor + claude, not only as provider but als as claude on its own in the ide terminal and in the roo panel etc.

If there was a guarantee that bot used the same memory bank even when you may switch provider in roo it would be so awesome.

Anyway just an idea.
Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions