v2/docs/integrations/reasoningbank/REASONINGBANK-INTEGRATION-STATUS.md
Initialization: memory init --reasoningbank
.swarm/memory.db databaseStatus Check: memory status --reasoningbank
Mode Detection: memory detect
Direct CLI Memory Operations:
memory store key "value" --reasoningbank ❌memory query "search" --reasoningbank ❌Root Cause: Agentic-flow's ReasoningBank doesn't expose store/query as CLI commands. It's designed to be used by agents during task execution, not as a standalone memory store.
ReasoningBank is an agent-centric memory system:
# ✅ CORRECT: Use via agent execution
npx agentic-flow --agent coder --task "Build REST API using best practices"
# During execution, the agent:
# 1. Retrieves relevant memories from ReasoningBank
# 2. Uses them to inform its work
# 3. Stores new learnings back to ReasoningBank
# 4. Updates confidence scores based on success/failure
# ❌ INCORRECT: Direct CLI memory operations
npx claude-flow memory store pattern "..." --reasoningbank
# This doesn't work because ReasoningBank has no store/query CLI commands
# Standard key-value memory (always works)
claude-flow memory store api_pattern "Use environment variables for config"
claude-flow memory query "API"
claude-flow memory stats
# Initialize ReasoningBank
claude-flow memory init --reasoningbank
# Use agentic-flow agents (they'll use ReasoningBank automatically)
npx agentic-flow --agent coder --task "Implement user authentication"
# The agent will:
# - Query ReasoningBank for relevant patterns
# - Learn from past successes/failures
# - Store new learnings automatically
# View available tools
npx agentic-flow reasoningbank --help
# Available commands:
npx agentic-flow reasoningbank demo # Interactive demo
npx agentic-flow reasoningbank test # Validation tests
npx agentic-flow reasoningbank status # Statistics
npx agentic-flow reasoningbank benchmark # Performance tests
npx agentic-flow reasoningbank consolidate # Memory cleanup
npx agentic-flow reasoningbank list # List memories
Full CLI Integration:
store/query operationsmemory migrate --to reasoningbankImplementation Plan:
If you initialized ReasoningBank and want to use its learning capabilities:
# 1. Initialize (one-time)
claude-flow memory init --reasoningbank
# 2. Use basic memory for manual storage
claude-flow memory store api_best_practice "Always validate input"
# 3. Use agentic-flow agents for AI-powered learning
npx agentic-flow --agent coder --task "Build secure API endpoints"
# The agent will:
# - Access ReasoningBank automatically
# - Learn from your basic memory entries
# - Store new learnings with confidence scores
Architecture
┌─────────────────────────────────────┐
│ claude-flow memory │
├─────────────────────────────────────┤
│ │
│ Basic Mode (default) │
│ ├─ store/query/stats ✅ │
│ ├─ JSON file storage │
│ └─ Fast, simple KV store │
│ │
│ ReasoningBank Mode │
│ ├─ init ✅ │
│ ├─ status ✅ │
│ ├─ detect ✅ │
│ ├─ store ❌ (v2.7.1) │
│ └─ query ❌ (v2.7.1) │
│ │
└─────────────────────────────────────┘
│
├─ Used by ─┐
│ │
▼ ▼
┌────────────────┐ ┌────────────────────┐
│ Basic Memory │ │ agentic-flow │
│ (JSON file) │ │ agents │
└────────────────┘ │ │
│ ├─ coder │
│ ├─ researcher │
│ ├─ reviewer │
│ └─ etc. │
│ │
│ Uses ReasoningBank │
│ automatically ✅ │
└────────────────────┘
v2.7.0-alpha Status:
Recommended Approach:
Not a Bug: This is an architectural limitation, not a bug. ReasoningBank was designed for agent use, and v2.7.0 exposes that functionality correctly through agentic-flow agents.
The v2.7.1 release will add convenience CLI wrappers for direct memory operations.