Skip to main content
Memory in Timbal agents enables multi-turn conversations and context persistence across agent interactions. Agents automatically maintain conversation history without requiring additional configuration.

​
How Memory Works

Timbal implements memory through its tracing system, which captures conversation history during agent execution. When an agent runs, it automatically resolves memory from previous interactions to maintain conversational context.

​
Automatic Memory Resolution

During each agent execution:
  1. The agent checks for previous conversation context
  2. If found, it retrieves conversation history from the tracing data
  3. Previous messages are automatically included in the current conversation
  4. The agent processes the new input with full conversation context
This happens transparently - agents receive conversation memory without any code changes.

​
Storage Options

Memory storage depends on your deployment environment:
  • Timbal Platform: Conversation history is automatically persisted with high availability and cross-instance sharing
  • Local Development: Uses in-memory storage that’s fast but cleared on restart

​
Nested Agent Memory

When agents call other agents, memory flows seamlessly between them. Child agents automatically receive conversation context from their parent, enabling sophisticated multi-agent workflows while maintaining conversation continuity. 
# Parent agent
class SupportAgent(Agent):
    model = "anthropic/claude-3-sonnet"
    tools = [billing_agent, technical_agent]

# Child agents automatically inherit conversation context
class BillingAgent(Agent):
    model = "anthropic/claude-3-haiku"
    # Receives full conversation history from parent

​
Configuration

Memory is automatically configured based on your deployment:
  • Platform Deployment: No configuration needed
  • Self-Hosted: Uses in-memory storage by default, with platform integration available
Memory works automatically. For deeper understanding of the underlying mechanisms, see Tracing and Context.

​
Rewind

Timbal supports conversation branching, allowing you to rewind to any previous point and explore alternative conversation paths.

​
How Branching Works

Each agent interaction creates a unique run with its own context. You can branch from any previous run by referencing its run_id, creating independent conversation paths that diverge from that point. 
from timbal import Agent
from timbal.state import RunContext, set_run_context

agent = Agent(name="example", model="openai/gpt-4o-mini")

# Main conversation
step1 = await agent(prompt="Hello").collect()
step2 = await agent(prompt="My name is David").collect() 
step3 = await agent(prompt="What's my name?").collect()
# Output: "Your name is David"

# Branch from step 1 (before name was shared)
context = RunContext(parent_id=step1.run_id)
set_run_context(context)

branch = await agent(prompt="What's my name?").collect()
# Output: "I don't know your name"
This creates branching conversations: 
"Hello"
├── "My name is David" → "What's my name?" → "David"
└── "What's my name?" → "I don't know"

​
Common Use Cases

  • A/B Testing: Compare different conversation strategies
  • Error Recovery: Return to a state before an error occurred
  • Debugging: Isolate specific conversation states for testing
  • Exploration: Test “what if” scenarios without affecting the main conversation
Each branch maintains independent memory from the branching point. Learn more about the underlying mechanisms in Context.