Agent Fleet
Collective intelligence for agent fleets
d33pmemory works for a single personal agent or an entire fleet that shares a collective brain. Each agent builds its own private knowledge while contributing to a shared pool — new agents inherit everything the fleet has ever learned.
How fleet memory works
1 API key = 1 agent identity
Name your keys after your agents — slack-bot, customer-agent, personal-assistant. Each key is a separate brain.
Private memories stay private
Each agent's memories are isolated by default. Your Slack bot won't suddenly 'remember' things from your customer service agent.
Shared collective pool
Shared memories are automatically contributed to a collective pool. Every agent in the org benefits from accumulated knowledge.
Instant inheritance
Plug in a new agent tomorrow and it has access to everything the fleet has ever learned. No cold start.
Recall scoping
Agents choose what to see: own memories only, shared fleet knowledge, or both. You control the scope per recall.
User account (you@company.com)
├── slack-bot → private memories
├── customer-agent → private memories
├── personal-assistant → private memories
└── shared pool → all agents contribute & read
| Mode | Setup | What happens |
|---|---|---|
| Personal | 1 API key | Simple memory layer. No scoping needed. |
| Fleet | Multiple keys | Each agent has private + shared collective brain. |
| "own" | Only this agent's memories |
| "shared" | All shared memories across the fleet |
| "all" | Own + shared combined |
| "auto" | Own first, include shared if needed recommended |
Build your agent fleet
Fleet memory is available on the Pro plan.