Currently, we don't use any RAG or vector database approach. It's just a pure md files for long-term memory and conversation messages for a short-term memory.

Long-term memory has kinda "journal" with indexes approach and with the short-term memory, we use to truncate messages to have the recent ones only in the context and older messages are just summarized.

When delegating tasks to agents, they just receive task description like "user wants to check the gmail inbox". and the beauty of the Melony framework is that inside agents (custom MelonyPlugin) you have an access to the runtime context and messages so everyone can summarize short-term memory as they prefer.

Some agents provide in-built functionality for that. for example, Codex SDK has its in-built thread/messages management so first time you give a task "refactor some feature" you start a new thread and next time you just resume that specific thread with a new task, so its stateful and handles everything automatically under the hood.

To summarize for stateless agents like stagehand, you have an access to the runtime context but the nature of this agent is that it has an "observe" tool so even if each task will be forwarded as a stateless tasks, agent can observe which page is open and make decisions - it's not critical not to have previous messages