There are so many approaches to agent memory. I believe the simple solution is usually the best, and giving an agent access to a ticketing system like jira, linear, or even just any kind of popular database for it to manage locally like SQLite, will yield dramatically better results in the longer run than a collection of markdown files, or repos etc The reason organizations have used annoying tools like this for so long, is it’s how information and communication scales across an organization when it’s leveraged fully. If you’re trying to give your agent a memory, I recommend something queryable by its very nature, built to help anyone pull in more context about a problem. Agents can leverage jira (creating tickets, finding tickets, etc) better than humans ever could. Agents are the perfect middle managers. I tell my agent to use a local SQLite, and to just manage its own tickets and columns, so it knows how and what to query when I have a new feature or bug. The context just grows and grows - a ticket for every new bug or feature makes the memory naturally become more valuable the more tickets I complete. it fits for you as the driver, if you want to explore it in a tool like linear or your own built thing for kanban or table views etc submitted by /u/croovies
Originally posted by u/croovies on r/ClaudeCode
You must log in or # to comment.