Memory MCP solves a critical problem: context loss between sessions.
Instead of searching through knowledge bases, Memory MCP provides:
✓ Instant automatic recall (no search latency)
✓ Natural context reference in conversations
✓ Zero setup required (just say 'Remember:')
✓ Works even when embedding service is down
✓ Full-text searchable JSON storage
✓ Human-readable memory format
Key Features:
- Say 'Remember: [info]' to save
- Ask 'What did we work on yesterday?' for automatic recall
- Search memories by title, content, or tags
- All memories stored in ~/.claude/mcp-servers/memory/data/memories.json
Use Cases:
- Project context across days/weeks
- Technical insights from debugging
- Architecture decisions and rationale
- Quick reference facts about the codebase
- Avoiding repetition in explanations
Memory MCP + Code-Forge KB + Git Hooks = Complete knowledge system
- Memory: What we're working on this week
- KB: How the entire codebase works
- Hooks: Automatic updates on commits
This is how professional AI coding tools maintain context.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Complete analysis of Block 122 (Tuffy Appointment Form) including:
- Architecture analysis of 43KB enterprise-grade form
- 4-phase deprecation migration strategy
- Technical insights on Block.rb rendering engine
- Data binding and conditional rendering patterns
- Implementation approach with Rails components
- Testing strategy for complex form migration
- Effort estimation (3-4 weeks per block)
This research complements the detailed case study and provides
a comprehensive foundation for Block deprecation project.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
- BLOCKS_DEPRECATION_STRATEGY.md: Comprehensive 4-phase migration plan from Block system to Rails views
- Architecture analysis of Block.rb rendering engine
- 7 pain points for deprecation
- Detailed implementation steps for each phase
- Risk mitigation strategies
- Benefits comparison table
- BLOCK_CASE_STUDY_TUFFY_APPOINTMENT_FORM.md: Deep analysis of Block 122 (Tuffy Appointment Form)
- Real production block: 43KB, ~1,150 lines, enterprise-grade form
- Complexity metrics and comparison
- Complete decomposition strategy into Rails components
- Presenter class design
- 4-step form partials with code examples
- Service layer architecture
- External JavaScript extraction
- 8-week implementation timeline
- Risk assessment and testing strategy
This case study provides the blueprint for migrating all 100+ form blocks in PISTN.
If Block 122 can be successfully migrated, all blocks can be migrated.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
✨ Features Added:
- Delete button on each document card (appears on hover)
- Confirmation modal with document preview before deletion
- Backend DELETE API endpoint for removing documents
- Frontend integration with React Query mutations
- Proper error handling and success feedback
📝 Implementation Details:
- New deleteDocument() API function in frontend/src/lib/api.ts
- Delete button styled in blaze-orange with hover effects
- Modal dialog with file name display and confirmation
- Automatic KB stats and document list refresh after deletion
🎯 User Experience:
- Delete button hidden until hover (prevents accidental clicks)
- Confirmation modal prevents irreversible mistakes
- Real-time list updates after deletion
- Success/error messages with 3s auto-dismiss
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Features:
- Fixed Ollama configuration for native (localhost) instead of Docker
- Increased LLM timeout from 30s to 120s for quality answers
- Implemented KB slug system for clean MCP endpoint URLs
- Added multiple knowledge base support with type metadata
- Integrated MCP server with FastAPI (port 8051)
- React frontend with KB management UI
- PostgreSQL + pgvector for vector embeddings
Performance:
- 33-56% faster than Docker setup with native Ollama
- Direct Metal GPU acceleration on Apple Silicon
- Optimized RAG engine with caching
- ~40s response time for comprehensive answers
Documentation:
- Complete native setup guide (README_NATIVE_SETUP.md)
- Performance benchmarking and comparison
- MCP endpoint documentation
- Slug implementation details
- Decision rationale for native vs Docker
Cleanup:
- Removed old Streamlit setup files
- Consolidated setup scripts to single setup_native.sh
- Consolidated service management scripts
- Removed test artifacts and old analysis docs
- Ready for sharing with team
🚀 Production-ready for local team deployment
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
