​

Agent Management

​

What is an Agent?

• Unique identifier - Never changes (e.g., customer-support-bot)
• Memory namespace - Isolated from other agents
• Multiple sessions - Can have sessions at different times
• Long-term context - Memories persist across sessions

​

Agent Lifecycle

Create Agent (Auto-Activates) → Store/Recall Memories → Deactivate Session → Reactivate Later
                                                                                      ↓
                                                                               Delete Agent (optional)

​

Managing Agents

• CLI Reference: See Agent Commands and Session Commands.
• API Reference: See Agents API and Sessions API.
• Session Guide: See Session Management Guide for details on session lifecycles.

​

Agent Namespaces

Agent: customer-support
Namespace: memanto_agent_customer-support

​

Search Isolation

Agent: customer-support (namespace: memanto_agent_customer-support)
    Query: "user preferences"
    Search: ONLY in memanto_agent_customer-support

Agent: project-manager (namespace: memanto_agent_project-manager)
    Query: "project status"
    Search: ONLY in memanto_agent_project-manager

​

When You Need Shared Memory

Agent: shared-context
    Namespace: memanto_agent_shared-context
    Stores: company policies, product features, shared customer context

Sales Agent: recalls from its own namespace + shared-context
Support Agent: recalls from its own namespace + shared-context

​

Namespace Naming

memanto_agent_{agent_id}

• customer-support -> memanto_agent_customer-support
• project-manager -> memanto_agent_project-manager
• research-bot -> memanto_agent_research-bot

​

Namespace Best Practices

• Create separate agents for different domains
• Keep related memories in the same agent
• Use a shared-context agent for cross-team knowledge

• Put all memories in one agent
• Expect cross-agent search automatically
• Reuse one agent for unrelated purposes

​

Deleting Agents

​

CLI Method

memanto agent delete customer-support

memanto agent delete customer-support --force

​

What Gets Deleted

​

REST API Method

import httpx

# Local metadata only (cloud namespace retained)
response = httpx.delete(
    "http://localhost:8000/api/v2/agents/old-agent"
)

# Also delete the Moorcheh namespace
response = httpx.delete(
    "http://localhost:8000/api/v2/agents/old-agent",
    params={"delete-backup-too": "true"},
)

if response.status_code == 200:
    print(response.json()["message"])

​

Agent Metadata

​

View Agent Metadata

memanto agent bootstrap customer-support

• Agent ID
• Created timestamp
• Memory count by type
• Last session info
• Summary of important memories

​

Agent Isolation & Scaling

• Per User/Role: alice-support-rep, bob-support-rep
• Per Domain/Task: customer-preferences, billing-issues
• Per Environment: prod-support-bot, staging-support-bot

​

Performance Considerations

​

Agent Limits

• No hard limit on number of agents (free tier up to 5 agents)
• Each agent can have unlimited memories
• Sessions limited to 1 active per agent at a time
• Memories queryable in under 100ms on average

​

Optimization Tips

1. Reuse agent sessions - Don’t create new sessions frequently if active session is available
2. Batch operations - Store multiple memories at once
3. Deactivate sessions - Deactivate sessions when no longer needed to free resources

​

Next Steps

• Store Memories: Memory Operations Guide
• Session Management: Session Management Guide
• CLI Reference: Agent Commands