Documentation/Memory System
Memory System
Crowdi agents learn from past experiences to provide more realistic testing over time.
Short-term Memory (Session)
During a single simulation run, agents remember:
- Pages they've visited
- Actions they've taken
- Elements they've interacted with
- Errors they've encountered
This prevents agents from repeating failed actions and getting stuck in loops.
Long-term Memory (Historical)
Across multiple simulations, agents learn:
- Common UI patterns in your app
- Successful paths to goals
- Elements that typically cause confusion
- Optimal interaction sequences
Memory Persistence
By default, agents retain memories across simulations for the same project. This can be controlled:
# Fresh start - no historical memory
crowdi run --url https://your-product.com --fresh
# Use historical memory (default)
crowdi run --url https://your-product.com
When to Use Fresh Simulations
- Testing a completely redesigned interface
- Validating first-time user experience
- After major navigation changes
Memory Analytics
View what agents have learned:
crowdi memory --project your-project
Last updated: Today
Edit this page on GitHub →