Skip to content
Tisty icon Tisty

Give your AI coding agent memory that lasts between sessions

Your agent is brilliant at the file in front of it and forgets the picture: why something was decided six months ago, what failed last time, what is still left. Every new session starts with you explaining the project again.

By Mario Hidalgo G.

What people usually do

  1. 1

    Write it into CLAUDE.md or AGENTS.md

    Good for what rarely changes: how to build, the conventions. Progress and decisions written there turn it into a diary the agent rereads whole, every session.

  2. 2

    Keep a NOTES.md or a memory-bank folder

    Often hidden behind .gitignore. It grows, nobody corrects it in place, and it stays on one machine and one branch.

  3. 3

    Start a TASKS.md, or a Markdown file per session

    Easy to begin. Within weeks there are dozens of files, half of them stale, and nothing says which one still holds.

What that costs

  • The agent rereads every file, whole, every session: the bigger the memory, the more each session costs before any work starts.
  • Nothing is dated or archived, so «how did we solve this last year?» has no answer.
  • The files go stale, pile up and get lost between branches, machines and projects.

A memory your agent reads a section at a time

  • Tisty keeps tasks with their steps and a dated journal, and documents one per subject, as Markdown on your own disk.
  • Over MCP, your agent asks what moved since the last session, reads an outline first and then only the section it needs: on a 256 KB log, picking up the work costs about 99% less than rereading it.
  • A finished task goes to the archive whole, and a search answers «how did we solve this?» with the line that says it.
  • Free and open source, for Windows and macOS, with no account.
Tisty icon Meet Tisty The working memory for you and your AI agent. Free, open source, no account, no telemetry. Docs for Tisty

Frequently asked questions

Does Tisty replace CLAUDE.md or AGENTS.md?

No, it sits beside them. Instructions that rarely move stay in the files your repository hands the assistant; progress, decisions, what was ruled out and what is left go in Tisty.

Which assistants can use it?

Any that speaks MCP: GitHub Copilot in VS Code, Claude Code, Codex, Cursor and Gemini CLI connect with one line, and Settings › Assistants in Tisty connects the ones it finds on your computer.

Carry on with