Feature: DakeraMemoryDriver — persistent cross-run memory backend for Griptape agents #2227
ferhimedamine
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Griptape has excellent in-session memory (ConversationMemory, TaskMemory) but no cross-run persistence. This proposes DakeraMemoryDriver as a persistent backend for Griptape agents using the self-hosted Dakera (https://dakera.ai) memory server.
Problem: Griptape agents lose all memory between process restarts. For agents running recurring tasks (daily report summaries, ongoing research assistants), context must be re-established on every run.
Proposed: DakeraMemoryDriver implementing BaseConversationMemoryDriver:
from griptape.drivers.memory.conversation import BaseConversationMemoryDriver
from griptape.artifacts import BaseArtifact
from dakera import DakeraClient
class DakeraConversationMemoryDriver(BaseConversationMemoryDriver):
base_url: str = 'http://localhost:3300'
api_key: str = ''
agent_id: str = 'griptape-agent'
Usage:
from griptape.structures import Agent
from griptape.memory.structure import ConversationMemory
Setup: docker run -d -p 3300:3300 -e DAKERA_API_KEY=demo ghcr.io/dakera-ai/dakera:latest / pip install dakera
Relevant: griptape/drivers/memory/conversation/
Happy to open a PR.
All reactions