Notes & memory
A single conversation forgets everything when it ends. Notes are how you give Kinn a durable memory for facts about your product that should outlive any one chat — and then have those facts resurface automatically when they're relevant later.
What notes are good for
Save anything Kinn should keep on hand about your product:
- Release and launch dates — "We shipped v2.0 on June 10."
- Recurring bugs or known issues — "Login times out intermittently on Android; engineering is aware."
- Changelog entries — what changed in a given patch.
- Decisions and context — "We decided to deprioritize the Steam forums for now."
- Roadmap facts — what's planned and when.
Because these are tied to your product rather than a conversation, Kinn can pull them back up in a future chat — for example, knowing a launch date when you later ask "how did feedback change after we shipped?"
How to save and use them
Just tell Kinn to remember something:
- "Remember that we launched the 2.1 patch on Monday."
- "Make a note that the checkout crash was fixed in build 4502."
Kinn saves the fact, and it becomes searchable shortly after (it's indexed in the background). From then on, the agent can surface it when you ask a related question, and you can ask it to recall what it knows: "What launch dates do you have on file?"
Good to know
Notes are immutable — once saved, a note isn't edited in place. To correct or update one, Kinn deletes the old note and creates a new one in its place. You can ask it to do exactly that: "That date was wrong — we actually launched on the 11th. Update the note."
- Notes are scoped to one product. A note saved for one product is never visible to another.
- Saving and deleting notes requires edit access (see reading vs. making changes). Anyone can benefit from the notes already on file; changing them needs permission.
- Keep facts plain and specific. The clearer the statement you save ("v2.0 launched 2026-06-10"), the more reliably Kinn can match it to a later question.