Notes & memory

Memory in TrailSail is a file you can open. Notes live as plain markdown in two places:

  • Project notes — in <project>/.trailsail/notes, so they live with the code.
  • Global notes — in the app's support folder, for things that apply everywhere.

No vector store, no embeddings database. If you can read markdown, you can audit what the model remembers.

How it works in a session

  1. At the start of every session the model is given the topic list — the names and first lines of your notes — so it knows what exists before it asks.
  2. As it learns things worth keeping (decisions, gotchas, conventions) it saves them to the right topic: project notes for this codebase, global for you.
  3. Before history is compacted, the model gets one pass to write notes — its chance to turn a long session into durable memory before the summary shrinks it.

Wrap up

Every chat has a Wrap up action. One click, it writes:

  • a ticket summary of what the chat did, and
  • the durable decisions it made, into the right note topic.

Use it the way you would use git commit -m for a conversation: at the end of meaningful work.

The Notes panel

⇧⌘N opens the Notes panel: browse topics in both folders, edit notes in place (a change you make is what the model reads next session), and create, rename or delete topics.

Conventions that help

  • One topic per decision. decisions/sqlite-over-postgres.md beats a giant notes.md.
  • Write the why, not just the what. “Used SQLite because the export is a file” is still useful next month; “used SQLite” is not.
  • Delete confidently. A stale note is worse than no note — the model notices the topic is gone and stops citing it.

Found a problem, or is something here unclear? Report it.