• Loading…

Memory and project rules

What SoreQen remembers between sessions, and how a project tells it about itself.

Memory

SoreQen remembers what it learns as it works, such as a server it set up for you, how your project deploys, or how you like things done, and knows it in your next session. When it saves something it says so: "Remembered for next time: …".

It never saves passwords or keys.

CommandWhat it does
/memoryShows what SoreQen remembers.
/memory forget <name>Removes one memory.

In the desktop app, Settings → Memory shows the same and lets you edit it.

Memories are kept per project, in ~/.soreqen/projects/<project>/memory/, as Markdown files you can read.

Project rules

A project can describe itself in a rulebook: how to build and test it, its conventions, what to avoid. SoreQen reads the first of these it finds in the folder:

  1. .soreqenrules
  2. SOREQEN.md
  3. .soreqen/rules.md
  4. .cursorrules

/rules shows the one in use.

A rulebook is written by whoever wrote the repository, who may not be you. SoreQen uses it as information about the project; it does not let it override what you ask.