Welcome — what discussions are for

[fdaviddpt]

This is the home for everything that isn't a bug report.

Why discussions, not issues

Issues are for "this is broken" or "this is missing." Everything else lives here. If you're not sure which to use, default to discussions — we'll move it to an issue if it turns out to be one.

What goes where

• Q&A — How does the pipeline handle X? Why is now.md empty? What does this config key do? Anyone who's hit it before can answer and the next person finds the answer in search.
• Ideas — "What if .remember/ could…" — features, behavior changes, new hooks. Before you open one, search existing issues + ideas. Discussion here is cheaper than a half-built PR.
• Show and tell — Your identity.md, your hooks.d/ setup, what you do with the daily compression output, the workflow you built on top of this. We love seeing the variants.
• Announcements — Maintainer-only. Releases, deprecations, behavior changes that affect existing installs.
• General — Anything that doesn't fit above. Conversations about Claude Code, memory in agents, where this should go next.

What this project is

Continuous memory for Claude Code. Sessions get extracted, summarized through Haiku, compressed into layered daily logs (buffer → daily → recent → archive → core). Plain-text files in .remember/, editable, gitignored. The agent remembers what it learned across sessions.

Default install: per-project. External mode: ~/.remember/<slug>/ shared dir. Opt-in git backup pushes memory to a private repo you control. See README.md for the full picture and CHANGELOG.md for what changed when.

What we appreciate in a post

• Concrete over abstract. "Here's the hook I wrote, here's what it does, here's why" beats "what if there was a hook system." (There is. It's hooks.d/.)
• Reproductions over symptoms. If something's behaving oddly, the contents of .remember/now.md or a log snippet (.remember/logs/memory-*.log) is worth 100 words of description.
• Patience. Maintainers and contributors are mostly building this in spare time. Replies may take a few days.

What we're allergic to

• Posts asking the maintainers to add a feature without engagement about the design.
• "Does this work with X?" — try it and tell us what happened. Both answers are useful.
• Anything that should be an issue (a bug with steps to reproduce, a CI failure, a regression). Use Issues for those.

Security

Don't report vulnerabilities in discussions or issues. Email fdavid@digitalprocesstools.com — see SECURITY.md.

Code of conduct

CODE_OF_CONDUCT.md. Contributor Covenant 2.1. Be kind, be specific, assume good faith.

---

We made this because we wanted it. The fact that anyone else uses it is genuinely a surprise and a pleasure. Tell us what you're building.

— Max & Florian (Digital Process Tools)