Back

Towards self-learning coding agents

/2 minute read

So often, you work with coding agents when its making mistakes and you ask why don’t you remember this? A human would have remembered many of the small details and feedback it’d have given. With coding agents, this doesn’t come by default and they need to store this information somewhere.

You also dont wan’t to manage this manually, as its a quite tedious and involved process. To solve this, we’ve built an experimental plugin for self learning:

https://cursor.com/marketplace/cursor/continual-learningfavicon for cursor.com

Towards self-learning coding agents – image 1

This will read existing chats, extract learnings, preferences and other relevant workspace information and then store it in AGENTS.md in a simple bulleted format.

Last year, we both shipped and unshipped memories. They built on a sidecar approach where a smaller model would monitor chats and extract the same information when it found something useful. We found this approach to be clunky, require more technical hoops, but most importantly not provide good memory suggestions. And that is why we unshipped it.

However, a need for long term persisted memory has not gone away. Agents have gotten better, and we have started adapting Cursor harness to be more file first focused: Dynamic context discoveryfavicon for cursor.com

As chat transcripts are just text stored in files, agent can access them with two tools it already has access to:

  1. Search (grep + semsearchfavicon for cursor.com)
  2. Read file

One challenge becomes formatting the transcripts in way that its flexible for rendering and easy to query. Fortunately, agents are good at retrieving and reasoning over what is relevant information given the task at hand, and that has enabled a plugin like this to exist

See the demo on Xfavicon for x.com

Building truly continual learning on a deeper level is something that’ll take time, but is something we’re working towards!

Try out the pluginfavicon for cursor.com and let me know what you think!


Originally published as an article on Xfavicon for x.com.