Repository navigation
Bug: Agent memory files saved in root directory instead of project folder #145
Description
Activity
Raven does not write memory, sessions or skills into the directory it is launched from: all of it lives under the Raven home (RAVEN_HOME, default ~/.raven), and global_mem.txt is not a Raven file. When this was filed, RAVEN_HOME did not yet move config.json or the workspace, so two copies could not be kept apart; commit e724aa7 fixed that (completed by 824412a and 2048f62, with the --home flag from 14e270f), so each instance can now be isolated with its own home, for example RAVEN_HOME=/path/to/instance-a raven tui. Copies that share the default home share its data by design. Please reopen with the exact file paths and command if memory files still appear inside your clone.
Summary
After cloning the Raven repository and running Raven directly at the root directory, the agent's memory files (such as conversation history and skill data) are saved to the root directory instead of the Raven project folder. This causes multiple Raven instances to conflict with each other, resulting in data mixing across instances.
Steps to reproduce
Expected behavior
Memory files should be saved within the Raven project directory (e.g., Raven/memory/ or Raven/data/). Each Raven instance should maintain its own isolated memory storage so that multiple instances can run independently without data conflicts.
Actual behavior
Memory files (conversation history, agent skill data, etc.) are saved to the root directory (the directory where Raven is executed). When multiple Raven instances run from different locations, their memory data gets mixed together, causing data pollution.
Environment
OS: Windows / Linux
Python: 3.10+
Raven: latest main branch
Logs or screenshots