Different shapes, complementary more than competing. jevmem is a thin automatic layer: watch the coding session, keep a flat scored JEVMEM.md (decisions/constraints/bugs/todos) in the repo, inject the relevant live lines next turn. Built around Claude Code hooks; Cursor/Codex share the same file.
From what I can see on deciduous.dev, you’re building a shared decision graph (goals → options → decisions → observations, multi-agent credit, archaeology from commits, Postgres + MCP). That’s richer reasoning-trail / multi-agent collaboration than jevmem aims for.
From what I can see on deciduous.dev, you’re building a shared decision graph (goals → options → decisions → observations, multi-agent credit, archaeology from commits, Postgres + MCP). That’s richer reasoning-trail / multi-agent collaboration than jevmem aims for.
I’d love a side-by-side if you try it — npm i -g jevmem and https://github.com/Avinash-jetwani/jevmem. Curious where deciduous feels clearly better.