‹ BackHN Continuity

Thread

Jevmem – automatic project memory for Claude Code, built on Jev

62 points · 49 comments · avinashjetwani

  1. rhgraysonii · · focus · HN ↗
    Curious how this compares to my own tool, <a href="https:&#x2F;&#x2F;deciduous.dev" rel="nofollow">https:&#x2F;&#x2F;deciduous.dev

    I will have to give it a run-through today.

    I haven&#x27;t used Jev yet so this should be interesting. I&#x27;d be interested to see if any Deciduous users have opinions, too.

    1. avinashjetwani · · focus · HN ↗
      Different shapes, complementary more than competing. jevmem is a thin automatic layer: watch the coding session, keep a flat scored JEVMEM.md (decisions&#x2F;constraints&#x2F;bugs&#x2F;todos) in the repo, inject the relevant live lines next turn. Built around Claude Code hooks; Cursor&#x2F;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 &#x2F; multi-agent collaboration than jevmem aims for.

      I’d love a side-by-side if you try it — npm i -g jevmem and <a href="https:&#x2F;&#x2F;github.com&#x2F;Avinash-jetwani&#x2F;jevmem" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Avinash-jetwani&#x2F;jevmem. Curious where deciduous feels clearly better.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.