Integrations
Customize Integration Behavior
Keep your Nowledge Mem behavior tweaks across plugin and extension updates.
If you tune how an integration behaves, that change should survive the next plugin update.
The safe rule is simple: put your rule in the host's own instruction file or settings surface. Do not edit installed plugin files inside a cache or marketplace directory.
First useful move
Pick the tool you use, add one small rule in the file or settings listed below, then update the plugin once later to confirm your tweak still survives.
Where To Put Your Changes
| Tool | Put your custom behavior here | Best for |
|---|---|---|
| Codex CLI | project AGENTS.md | Repo-specific memory behavior |
| Claude Code | CLAUDE.local.md for personal rules, CLAUDE.md for shared repo rules | Personal tweaks or team-wide repo guidance |
| Copilot CLI | .github/instructions/*.instructions.md for shared repo rules, ~/.copilot/instructions/*.instructions.md for personal rules | Shared or personal Copilot guidance |
| Cursor | .cursor/rules/*.mdc or .cursorrules | Project-local Cursor behavior |
| Gemini CLI | project GEMINI.md, optional ~/.gemini/GEMINI.md | Shared repo rules or personal defaults |
| Hermes Agent | HERMES.md for repo rules, ~/.hermes/SOUL.md for personal rules | Repo-specific or global Hermes behavior |
| OpenCode | project AGENTS.md, ~/.config/opencode/AGENTS.md, or files listed in opencode.json instructions | Shared or personal OpenCode guidance |
| Pi | project AGENTS.md | Project-local Pi guidance |
| OpenClaw | OpenClaw plugin settings and OpenClaw's own prompt or agent config | Behavior toggles and custom prompting |
| Alma | Alma settings and an optional manually loaded Alma skill prompt | Recall and capture behavior, extra instructions |
| Bub | Bub's own runtime prompt or config, plus shared nmem config | Bub-specific behavior and connection settings |
| Droid | Droid's own prompt or instruction surface, plus shared nmem config | Droid-specific behavior and connection settings |
| Raycast | Raycast preferences | Fixed launcher behavior such as server, key, and optional space |
What Not To Do
- Do not edit files inside installed plugin directories such as
~/.codex/...,~/.copilot/installed-plugins/...,~/.cursor/plugins/..., or similar cache paths. - Do not patch bundled skills in place and expect updates to preserve those changes.
- Do not invent a new override filename unless the host actually reads it.
What Success Looks Like
Your setup is in a good state when all three are true:
- Your custom rule lives in a file or settings surface the host actually owns.
- The integration still works after a normal plugin or extension update.
- Your behavior tweak is still active after that update without re-editing installed files.
Good First Tweaks
- "Search prior release work before answering regression questions."
- "Prefer saving Chinese notes when the user is working in Chinese."
- "Be more aggressive about thread search when the user asks what we decided before."
Keep the rule short. The goal is to shape behavior, not replace the whole integration guide.