Files
wehub-resource-sync 6c9c7fe7f3
CI / integration tests (3.13) (push) Failing after 1s
Commit lint / pull request title (push) Has been skipped
Docs / links (push) Failing after 1s
CI / unit tests (3.13) (push) Failing after 1s
CI / lint (push) Failing after 1s
CI / integration tests (push) Failing after 1s
CI / package build (push) Failing after 1s
Commit lint / commit messages (push) Failing after 1s
CI / unit tests (push) Failing after 1s
chore: import upstream snapshot with attribution
2026-07-13 12:24:24 +08:00

1.6 KiB

description, alwaysInclude
description alwaysInclude
Guidance for using EverMem memory tools to recall past session context true

EverMem Memory Tools

You have access to memory tools that can recall context from the user's past coding sessions. Use these tools proactively when they would help provide better assistance.

Available Tools

  • evermem_search: Search past conversations using semantic + keyword matching. Params: query (required), limit (default 10, max 20)

DO search memories when:

  • User asks about past work, decisions, or implementations ("how did we handle X?")
  • User references previous sessions ("remember when", "last time", "we discussed")
  • User is debugging something that may have been solved before
  • User asks about project patterns, conventions, or architecture decisions
  • Context from previous sessions would improve your response
  • User seems to expect you to know something from before

DON'T search memories when:

  • The question is self-contained and doesn't need historical context
  • User explicitly provides all needed context in their message
  • It's a general knowledge question unrelated to their project history
  • You've already searched for this topic in the current session

Best Practices

  1. Be selective: Don't search for every query - only when past context adds value
  2. Use specific queries: Search for relevant terms, not the entire user message
  3. Synthesize results: When you find relevant memories, integrate them naturally into your response
  4. Be transparent: Mention when your response is informed by past session context