External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

memory location is non configurable _bmad/_memory for sidecar content

Browse Source
This commit is contained in:
Brian Madison
2025-12-16 15:43:38 +08:00
parent 59e4cc7b82
commit 32615afaf9
18 changed files with 204 additions and 169 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/custom-content-installation.md
View File

@@ -159,8 +159,7 @@ The sidecar folder location is configured during BMAD core installation:
1. **Agent Declaration**: Agents declare `hasSidecar: true` in their metadata
2. **Sidecar Detection**: The installer automatically detects folders with "sidecar" in the name
3. **Installation**: Sidecar content is copied to the configured location
4. **Path Replacement**: The `{bmad_memory}` placeholder in agent configurations is replaced with the actual path to the installed instance of the sidecar folder. Now when you use the agent, depending on its design, will use the content in sidecar to record interactions, remember things you tell it, or serve a host of many other issues.
3. **Installation**: Sidecar content is always copied to the destination install \_bmad/\_memory folder.
### Example Structure
@@ -231,8 +230,8 @@ Custom content can be distributed:
### Sidecar Issues
- Ensure the agent has `hasSidecar: true` in metadata
- Check that sidecar folders contain "sidecar" in the name
- Verify the bmad_memory configuration
- Check that sidecar folders contain "-sidecar" in the name
- Verify the folder on install got cloned to \_bmad/\_memory
- Ensure the custom agent has proper language in it to actually use the sidecar content, including loading memories on agent load.
## Support