---
title: "Discussion on \"Memory for AI coaches, tutors and companions: what to store per user, and what not to\" | Hashnode"
description: "Discussion on \"Memory for AI coaches, tutors and companions: what to store per user, and what not to\". How to give an AI coach, tutor or companion app memory per user: what to store, what to skip, how to scope it by user, and how to let users reset it."
url: "https://hashnode.com/posts/ai-coach-tutor-companion-memory-per-user/6af735fdc274b4098fae4743"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Memory for AI coaches, tutors and companions: what to store per user, and what not to](https://memorysync.hashnode.dev/ai-coach-tutor-companion-memory-per-user?utm_source=hashnode&utm_medium=feed)

How to give an AI coach, tutor or companion app memory per user: what to store, what to skip, how to scope it by user, and how to let users reset it.

4h ago · 7 min read · memorysync.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#llm](https://hashnode.com/tag/llm)
-   [#python](https://hashnode.com/tag/python)
-   [#tutorial](https://hashnode.com/tag/tutorial)

## Written by

[MemorySync](https://hashnode.com/@memorysync)

@memorysync · San Francisco, USA

  
[View profile](https://hashnode.com/@memorysync)

Building MemorySync (memorysync.io) — persistent memory infrastructure for AI agents, Cursor, and Claude Code.

Building MemorySync (memorysync.io) — persistent memory infrastructure for AI agents, Cursor, and Claude Code.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.