Agent Orchestration
Command
/claude-flow-memory
Interact with Claude-Flow memory system
> /plugin marketplace add ruvnet/ruflo
Command definition
claude-flow-memory.mdname: claude-flow-memory
description: Interact with Claude-Flow memory system
🧠 Claude-Flow Memory System
The memory system provides persistent storage for cross-session and cross-agent collaboration with CRDT-based conflict resolution.
Store Information
# Store with default namespace
./claude-flow memory store "key" "value"
# Store with specific namespace
./claude-flow memory store "architecture_decisions" "microservices with API gateway" --namespace arch
Query Memory
# Search across all namespaces
./claude-flow memory query "authentication"
# Search with filters
./claude-flow memory query "API design" --namespace arch --limit 10
Memory Statistics
# Show overall statistics
./claude-flow memory stats
# Show namespace-specific stats
./claude-flow memory stats --namespace project
Export/Import
# Export all memory
./claude-flow memory export full-backup.json
# Export specific namespace
./claude-flow memory export project-backup.json --namespace project
# Import memory
./claude-flow memory import backup.json
Cleanup Operations
# Clean entries older than 30 days
./claude-flow memory cleanup --days 30
# Clean specific namespace
./claude-flow memory cleanup --namespace temp --days 7
🗂️ Namespaces
- **default** - General storage
- **agents** - Agent-specific data and state
- **tasks** - Task information and results
- **sessions** - Session history and context
- **swarm** - Swarm coordination and objectives
- **project** - Project-specific context
- **spec** - Requirements and specifications
- **arch** - Architecture decisions
- **impl** - Implementation notes
- **test** - Test results and coverage
- **debug** - Debug logs and fixes
🎯 Best Practices
Naming Conventions
- Use descriptive, searchable keys
- Include timestamp for time-sensitive data
- Prefix with component name for clarity
Organization
- Use namespaces to categorize data
- Store related data together
- Keep values concise but complete
Maintenance
- Regular backups with export
- Clean old data periodically
- Monitor storage statistics
- Compress large values
Examples
Store SPARC context:
./claude-flow memory store "spec_auth_requirements" "OAuth2 + JWT with refresh tokens" --namespace spec
./claude-flow memory store "arch_api_design" "RESTful microservices with GraphQL gateway" --namespace arch
./claude-flow memory store "test_coverage_auth" "95% coverage, all tests passing" --namespace test
Query project decisions:
./claude-flow memory query "authentication" --namespace arch --limit 5
./claude-flow memory query "test results" --namespace test
Backup project memory:
./claude-flow memory export project-$(date +%Y%m%d).json --namespace project
Read more
name: claude-flow-memory description: Interact with Claude-Flow memory system
🧠 Claude-Flow Memory System
The memory system provides persistent storage for cross-session and cross-agent collaboration with CRDT-based conflict resolution.
Store Information
# Store with default namespace ./claude-flow memory store "key" "value" # Store with specific namespace ./claude-flow memory store "architecture_decisions" "microservices with API gateway" --namespace arch
Query Memory
# Search across all namespaces ./claude-flow memory query "authentication" # Search with filters ./claude-flow memory query "API design" --namespace arch --limit 10
Memory Statistics
# Show overall statistics ./claude-flow memory stats # Show namespace-specific stats ./claude-flow memory stats --namespace project
Export/Import
# Export all memory ./claude-flow memory export full-backup.json # Export specific namespace ./claude-flow memory export project-backup.json --namespace project # Import memory ./claude-flow memory import backup.json
Cleanup Operations
# Clean entries older than 30 days ./claude-flow memory cleanup --days 30 # Clean specific namespace ./claude-flow memory cleanup --namespace temp --days 7
🗂️ Namespaces
- **default** - General storage
- **agents** - Agent-specific data and state
- **tasks** - Task information and results
- **sessions** - Session history and context
- **swarm** - Swarm coordination and objectives
- **project** - Project-specific context
- **spec** - Requirements and specifications
- **arch** - Architecture decisions
- **impl** - Implementation notes
- **test** - Test results and coverage
- **debug** - Debug logs and fixes
🎯 Best Practices
Naming Conventions
- Use descriptive, searchable keys
- Include timestamp for time-sensitive data
- Prefix with component name for clarity
Organization
- Use namespaces to categorize data
- Store related data together
- Keep values concise but complete
Maintenance
- Regular backups with export
- Clean old data periodically
- Monitor storage statistics
- Compress large values
Examples
Store SPARC context:
./claude-flow memory store "spec_auth_requirements" "OAuth2 + JWT with refresh tokens" --namespace spec ./claude-flow memory store "arch_api_design" "RESTful microservices with GraphQL gateway" --namespace arch ./claude-flow memory store "test_coverage_auth" "95% coverage, all tests passing" --namespace test
Query project decisions:
./claude-flow memory query "authentication" --namespace arch --limit 5 ./claude-flow memory query "test results" --namespace test
Backup project memory:
./claude-flow memory export project-$(date +%Y%m%d).json --namespace project
Stats
81,370
Stars
9,577
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withruflo
📖 RuFlo Explained — Build an AI Team That Plans, Remembers, Tests, and Improves A 14-chapter guide: from the basic idea to a first useful task, then memory, agent teams, plugins, cost and verification. Agent = Model + Harness.
80k200 skills169 agents3 MCP
Other commands on ruflo.
More commands from other plugins.
ask
CommandThis compatibility command keeps `/oh-my-claudecode:ask` available without loading the full `ask` skill description in every…
automation
CommandManage durable recurring session automations through the daemon API.

