The /initialize-project command outputs the MCP URLs directly,
so no need to tell users to manually find them in the UI.
Just note that the command shows the URLs to use.
Much cleaner and simpler.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changed:
- Updated MCP Integration section title to reference Claude CLI
- Updated feature list to mention Claude CLI integration
- Updated 'Perfect For' section to mention Claude CLI
- Updated 'Initialize Your Project' section
- Updated 'Via Claude CLI' in knowledge base query section
- Updated Architecture diagram to show Claude CLI instead of Desktop
The MCPs are designed for use with Claude CLI, not Claude Desktop.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changed:
- Removed detailed MCP integration instructions
- Removed old example MCP names (pistn, pistn-agent-os)
- Simplified to note that /initialize-project creates 4 MCPs automatically
- Explained the 4 auto-generated MCPs and their purposes
- Directed users to Project Setup modal for MCP URLs
The initialize-project skill handles all MCP creation, so manual
configuration instructions were unnecessary and outdated.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changed:
- Replaced misleading one-liner curl command with explicit clone + setup flow
- Updated 'Quick Install' section to show 3 clear steps
- Updated 'Installation (Step by Step)' to include clone step
- Changed step numbering from 4 to 5 steps total
- Made it clear that setup.sh must be run from within the repo
The setup.sh script requires relative paths to work, so users must
clone the repository first before running setup.
This matches standard Git project workflows and is now honest about
what's required to get the full installation.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Updated Step 3 to be crystal clear:
- Users must OPEN Claude Code and copy-paste the command
- Added prominent instruction: 'Open Claude Code and copy-paste'
- Added warning to replace project ID with actual number
- Added 3 clear examples with different project IDs
- Detailed what happens after running the command
- Explained the benefits: Claude becomes an expert, auto-updates on commits
This makes the workflow much clearer for users.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Added:
- One-line installer instructions with prerequisites clearly listed
- Step-by-step installation guide for macOS and Linux
- Detailed Scripts Guide documenting all 8 shell scripts
- Project initialization workflow (3 steps to make Claude an expert)
- Clear explanation of setup.sh vs setup_native.sh differences
- Honest documentation of what auto-installs vs what needs pre-installation
Changes:
- Reorganized Quick Start section with prerequisites at top
- Added one-line curl installer option prominently
- Expanded Scripts Guide with individual sections for each script
- Added "Initialize Your Project" section with project creation and ID steps
- Clarified that Python 3.11+ and Git must be pre-installed
- Documented that Ollama and Redis auto-install if missing
This makes Claude OS onboarding much clearer and more professional.
🤖 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>
