Guide
How to Tsumu
Tsumu remembers project context so you do not have to re-explain what happened, what matters, and what still needs attention.
Start with one project
Pick something real. Do not start with the whole life archive.
Add what you already have
Notes, docs, briefs, pasted thoughts. Messy is fine.
Work from what it knows
Ask questions, compare options, track follow-ups.
Keep it honest
Review memory and add better context as things change.
Start simple
Bring what you have. Tsumu finds the structure.
You do not need a clean document. Add rough notes, a brief, a meeting dump, or a few paragraphs explaining the situation. Tsumu can turn useful parts into project memory.
Sources
Drop in a doc or link to give the project its first context.Memory
Shows up after eligible chats, source imports, or notebook pages are added to memory.Chat
Start a thread. Ask about the project or just explain the situation.Basics
The words you will see in the app.
What is Tsumu?
Tsumu is a project memory app. It keeps useful context, decisions, follow-ups, and supporting sources together so you do not have to re-explain the project every time.
Workspace vs project
A project is the whole thing you are working on. A workspace is the current working area inside that project. Workspace context takes priority while Tsumu still keeps project memory in the background.
Sources
Sources are the fastest way to start. Add notes, docs, briefs, or pasted context. Tsumu reads them and turns useful parts into memory.
Memory
Memory is the structured project context Tsumu can reuse later: helpful facts, decisions, topics, follow-ups, and things worth checking again.
First workflow
Get useful memory in four steps.
Pick a real project
Use something you actually need to remember: a client handoff, launch, research brief, hiring round, or personal project.
Add context, even messy notes
Import a source, paste rough notes, or write a notebook page. Notebook pages can be saved on every plan; choose Add to memory when a note should become project memory.
Ask about the project
Ask what matters, what is missing, what changed, what follow-ups exist, or what decision was made.
Check what it remembered
Open Memory to see helpful context, topics, decisions, and follow-ups. Fixing memory keeps later answers cleaner.
What to bring
Useful input does not need to be polished.
Works well
- Meeting notes, even rough or unedited ones.
- Research dumps, specs, briefs, planning docs.
- Raw conversation logs or chat exports with a collaborator.
- Open questions, loose follow-ups, half-formed assumptions.
Leave out
- Passwords, API keys, payment details, or production secrets.
- Sensitive personal data (health, government IDs) without a clear legal basis.
- Huge unfiltered dumps - a short trusted brief usually works better.
First questions
Ask for project clarity, not generic chat.
Try asking
- What are the important facts in this project?
- What decisions have already been made?
- What follow-ups should I not forget?
- What is unclear or missing from the current context?
- Summarize this project for someone joining today.
Rule of thumb
The more project context Tsumu has, the better the answer. If an answer feels thin, add a source or notebook note first, then add the note to memory when it should be recalled later.