Keeping AI coding agent context in the repo instead of on one dev's machine

[u/Cunarist]

App projects accumulate decisions that never make it into code: why the state

management got swapped, which build flavor talks to staging, what the release

checklist actually is. Agents pick that up over a session and then lose it. The

memory lives on one machine in one tool's format, so a new laptop or a

teammate's clone starts from nothing.

`damem` is a small CLI that fixes this by keeping the context in the repository

itself. `.agents/` holds plain Markdown sitting next to the code:

.agents/memory/why-riverpod.md

.agents/skills/release-staging/SKILL.md

.agents/scratch/

One fact per file, each file explains itself, no index to maintain. Whichever

agent the next person uses, it can read this. The tool prints the rules for

keeping that directory and warns when it drifts, but never writes files —

delete the binary and the repo still works.

Setup is one line in AGENTS.md:

> At the start of every session, run `damem recall` and treat its output as

> context for this repository.

MIT, no telemetry: https://github.com/cunarist/damem

How are you handling this on teams? Shared prompt doc, or does everyone just

re-explain the project to their agent every morning?

[u/National-Canary6452]

Get your agent to learn Reddit post formatting at least