---
title: "Comment by Julian Neagu on \"Session memory is not project memory. It fixes the same complaint.\" | Hashnode"
description: "This split matches what I’ve seen building agent tools. Personal memory is useful, but anything the whole project needs should live with the code."
url: "https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab7c0c6a3af45d6714e8094"
---

[Discussion](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586)

Comment [Session memory is not project memory. It fixes the same complaint.](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586)

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Sep 26](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab7c0c6a3af45d6714e8094)

This split matches what I’ve seen building agent tools. Personal memory is useful, but anything the whole project needs should live with the code.

[Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner)

[Sep 27](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab7c0c6a3af45d6714e8094#reply-6ab8c851ca90ae391a1aa3a1)

Exactly. Personal memory and project memory solve different problems.

If the knowledge should survive people, sessions and tools, keeping it with the code gives it the same ownership, history and review process as the project itself.

That's the core idea behind Keep the Why.