Maintainer Triage

Use this as the default triage pass for new issues and discussions.

Bug reports

Check:

• can it be reproduced?
• is the reported version current?
• is it a docs/config misunderstanding rather than a product bug?
• does it affect MCP, CLI, web, retrieval, or storage?

If reproducible:

• add the right area label
• note severity and scope
• point to the likely subsystem if obvious

Feature requests

Check:

• what problem is being solved?
• is this retrieval, storage, docs, or integration work?
• does it fit Engram’s scope?
• is there a smaller first version worth accepting?

Security or conduct concerns

Do not handle these in public issues.

Redirect to:

• contact@engram-memory.dev

Good maintainer habits

• close duplicates with a link
• ask for repro steps instead of guessing
• keep labels simple and consistent
• prefer narrowing scope over leaving vague “maybe someday” issues open forever