Batch Send/Process Messages #3
Description
Currently, the Daemon class has a single message method that intakes a single string message with some options, and works through the lifecycle. This tends to be a bit inflexible since without running any additional tools, there's no easy way to handle recurring context. The main option is to run something like the MemoryServer found in mcp, however this adds extra latency and is only privy to information within the lifecycle it is called.
A common pattern with apps using the OpenAI SDK (or other analogs) is to send multiple messages for the purpose of context. These messages would still need to be stored with external fixtures outside of Daemon, but it would provide a simple and standard method of keeping history, as well as short-lived context injection without the need for using a memory server.
TLDR:
- Simpler state management
- Lower latency
- Opens the door for hybrid implementations