AWS shows Sprout, a $5–9/month AgentCore + OpenClaw assistant

The post frames a common frustration with off-the-shelf assistants: they answer well but start every conversation from zero, forcing users to re-explain context such as a garden's soil or a preference for organic fertilizer. AWS's answer is to pair OpenClaw, an open source agentic system, with AgentCore memory, which stores conversation turns as events and asynchronously extracts longer-lived records. Three extraction strategies are configured: USER_PREFERENCE, SEMANTIC, and SUMMARIZATION.

Several engineering choices are load-bearing. Records are filed into per-user namespaces, with the Telegram chat ID as the only variable segment, so two gardeners never mix. A retrieval step runs on every turn, and an assembly function ranks explicit preferences ahead of inferred facts before injection into the system prompt. AWS also routes image turns directly from server.py to the Bedrock Converse API rather than through the OpenClaw gateway, because the in-container build dropped image content parts. Model choice is treated as configuration, not code.

The cost story rests on consumption-based pricing and prompt caching: the stable persona and memory block go first, the volatile user message last, letting Bedrock skip recompute on the unchanged prefix. Whether the pattern holds up for a given team likely hinges on how much memory injection inflates each prompt and how tolerant users are of the extraction delay, since new facts typically become retrievable only in a later session.