A comprehensive task management framework designed specifically for Claude Code integration. ClaudeTask provides a visual web interface for managing development tasks while leveraging Claude's AI capabilities for automated analysis, implementation, and code review.
- Visual Task Board: Kanban-style interface for managing tasks across different stages
- Claude Code Integration: Seamless MCP (Model Context Protocol) integration with Claude
- Automated Workflow: Tasks are automatically analyzed and implemented by Claude
- Project Memory System: Automatic conversation persistence with RAG-based semantic search
- No context loss between sessions
- Intelligent summarization of project knowledge
- ChromaDB-powered semantic search
- AUTO Mode: Fully autonomous task execution with automatic PR creation
- Git Worktree Support: Isolated development environments for each task
- Local Merge Workflow: Complete workflow for projects without remote repositories
- Technology Agnostic: Works with any programming language or framework
- Coordinator-Executor Pattern: Claude acts as coordinator, delegating work to specialized agents
βββββββββββββββββββ βββββββββββββββββββ βββββββββββββββββββ
β Frontend β β Backend β β MCP Server β
β (React + TS) ββββββ€ (FastAPI + DB) ββββββ€ (Claude Bridge) β
βββββββββββββββββββ βββββββββββββββββββ βββββββββββββββββββ
β²
β
βββββββββββββββββ
β Claude Code β
βββββββββββββββββ
Before installing ClaudeTask, ensure you have the following installed:
- Python 3.8+
- Verify:
python3 --version - Install pip:
python3 -m pip --version
- Verify:
- Node.js 16+ and npm
- Install Node.js
- Verify:
node --versionandnpm --version
- Git
- Verify:
git --version
- Verify:
- Claude Code (latest version)
Note: ClaudeTask runs directly on your system (not in Docker) to maintain access to your terminal, Git, and Claude Code integration.
-
Clone the repository:
git clone https://github.com/pnvoroshilov/claude-code-feature-framework.git cd claude-code-feature-framework -
Install Backend:
cd claudetask/backend # Create virtual environment (recommended) python3 -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate # Install dependencies pip install -r requirements.txt # Start backend server python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reload
Backend will be available at:
- API: http://localhost:3333
- API Docs: http://localhost:3333/docs
- Health Check: http://localhost:3333/health
-
Install Frontend (in a new terminal):
cd claudetask/frontend # Install dependencies npm install # Start frontend development server REACT_APP_API_URL=http://localhost:3333/api PORT=3000 npm start
Frontend will be available at: http://localhost:3000
-
Install MCP Server (optional - for Claude Code integration):
cd claudetask/mcp_server pip3 install -r requirements.txtThe MCP server will be configured per-project (see Project Setup section below).
After installation, set up your first project:
-
Open ClaudeTask UI: http://localhost:3000
-
Navigate to "Project Setup" (gear icon in sidebar)
-
Create a new project:
- Project Name: e.g., "My App Development"
- Project Path: Absolute path to your project directory
- Description: Optional description
- Click "Initialize Project"
-
Configure Claude Code integration:
The initialization creates a
.mcp.jsonfile in your project directory. Example:{ "mcpServers": { "claudetask": { "command": "python3", "args": [ "/Users/youruser/.claudetask_mcp/native_stdio_server.py" ], "env": { "CLAUDETASK_PROJECT_ID": "generated-uuid", "CLAUDETASK_PROJECT_PATH": "/path/to/your/project", "CLAUDETASK_BACKEND_URL": "http://localhost:3333" } } } } -
Restart Claude Code:
- Close Claude Code completely
- Open your project directory in Claude Code
- MCP tools should now be available
-
Verify MCP connection:
# In Claude Code terminal, try: mcp:get_task_queue
You need to run both backend and frontend in separate terminals:
Terminal 1 - Backend:
cd claudetask/backend
source venv/bin/activate # Activate virtual environment
python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reloadTerminal 2 - Frontend:
cd claudetask/frontend
REACT_APP_API_URL=http://localhost:3333/api PORT=3000 npm startTips:
- Use
tmuxorscreento manage multiple terminals - Or use process managers like
pm2orsupervisor - Keep both services running while working with ClaudeTask
- Backlog β Analysis β Ready β In Progress β Testing β Code Review β Done
- Create Tasks: Use the web interface to create and prioritize tasks
- Claude Analysis: Claude automatically analyzes tasks and creates implementation plans
- Automated Development: Claude works in isolated git worktrees to implement features
- Worktrees automatically sync with the latest main branch before creation
- Each task gets the most recent code updates from origin/main
- Works gracefully with both remote and local-only repositories
- Testing & Review: Automated testing and code review process
- Merge: Completed tasks are merged back to main branch
ClaudeTask supports Claude Code integration through MCP (Model Context Protocol).
- Auto-initialize in your project:
# From your project directory
python3 "/path/to/framework/claudetask/scripts/init_project.py"- Manual setup - Add to your project's
.mcp.json:
{
"mcpServers": {
"claudetask": {
"command": "python3",
"args": [
"/path/to/framework/claudetask/mcp_server/native_stdio_server.py"
],
"env": {
"CLAUDETASK_PROJECT_ID": "ff9cc152-3f38-49ab-bec0-0e7cbf84594a",
"CLAUDETASK_PROJECT_PATH": "/path/to/your/project",
"CLAUDETASK_BACKEND_URL": "http://localhost:3333"
}
}
}
}- Restart Claude Code in your project
Ensure these services are running:
- Backend:
cd claudetask/backend && python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 - Frontend:
cd claudetask/frontend && REACT_APP_API_URL=http://localhost:3333/api PORT=3334 npm start
mcp:get_task_queue- View all tasks in queuemcp:get_next_task- Get highest priority taskmcp:get_task <id>- Get specific task details with next stepsmcp:analyze_task <id>- Analyze task and create planmcp:update_task_analysis <id> "<analysis>"- Save analysismcp:update_status <id> <status>- Update task statusmcp:create_worktree <id>- Create git worktreemcp:delegate_to_agent <id> <agent> "<instructions>"- Delegate to agentmcp:complete_task <id>- Complete and merge task
# Start task workflow
mcp:get_task_queue
mcp:get_next_task
mcp:get_task 4
# Follow the next steps provided by MCP responses
mcp:update_status 4 "In Progress"
mcp:delegate_to_agent 4 "frontend-developer" "Implement the feature"ClaudeTask consists of three main components that run separately:
cd claudetask/backend
source venv/bin/activate
python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reloadcd claudetask/frontend
REACT_APP_API_URL=http://localhost:3333/api PORT=3000 npm startThe MCP server runs automatically when Claude Code starts (configured in .mcp.json of your project).
- Hot Reload: Both backend (
--reload) and frontend automatically reload on changes - API Documentation: Visit http://localhost:3333/docs for interactive API docs
- Database: SQLite database is created automatically at
claudetask/backend/claudetask.db - Logs: Backend logs are in
claudetask/backend/server.log
claude-code-feature-framework/
βββ claudetask/
β βββ backend/ # FastAPI backend (Python)
β β βββ app/
β β β βββ models.py # SQLAlchemy database models
β β β βββ schemas.py # Pydantic schemas for API
β β β βββ main.py # FastAPI application entry point
β β β βββ database.py # Database configuration
β β β βββ services/ # Business logic services
β β β βββ task_service.py
β β β βββ project_service.py
β β β βββ real_claude_service.py
β β β βββ rag_service.py # RAG semantic search
β β βββ requirements.txt
β β βββ claudetask.db # SQLite database (auto-created)
β β βββ server.log # Application logs
β β
β βββ frontend/ # React frontend (TypeScript)
β β βββ src/
β β β βββ components/ # Reusable React components
β β β βββ pages/ # Page components (TaskBoard, Dashboard)
β β β βββ services/ # API client services
β β β βββ App.tsx # Main React app
β β βββ package.json
β β βββ public/
β β
β βββ mcp_server/ # MCP bridge (Python)
β βββ claudetask_mcp_bridge.py # Main MCP server
β βββ native_stdio_server.py # STDIO wrapper
β βββ requirements.txt
β βββ rag/ # RAG indexing system
β βββ indexer.py
β βββ embeddings.py
β
βββ framework-assets/ # Reusable agent configs
β βββ claude-agents/ # Agent markdown files
β βββ claude-configs/ # CLAUDE.md templates
β βββ claude-commands/ # Slash commands
β
βββ .claude/ # Project-specific Claude config
β βββ agents/ # Agent configurations
β βββ commands/ # Custom slash commands
β
βββ worktrees/ # Git worktrees for tasks (auto-created)
β βββ task-<id>/ # Isolated dev environment per task
β
βββ install.sh # Installation script
βββ README.md # This file
When you initialize a project, ClaudeTask creates:
.claudetask/directory with project metadata.mcp.jsonfile for Claude Code integrationCLAUDE.mdwith project-specific instructions- Default agent configurations
DATABASE_URL: Database connection stringREACT_APP_API_URL: Backend API URL for frontend
- Tasks run in isolated git worktrees
- No direct file system access from web interface
- MCP server requires project-specific configuration
- All changes go through git workflow
# Backend tests
cd claudetask/backend
pytest
# Frontend tests
cd claudetask/frontend
npm test- Installation & Setup - Complete installation guide
- Project Setup - First project configuration
- Project Memory System - Cross-session context preservation
- AUTO Mode - Autonomous task execution
- Local Worktree Merge - Merging without remote repository
- Testing Workflow - Manual and automated testing
- System Architecture - Complete technical overview
- Intelligent Workflow - 7-phase development workflow
- Hooks System - Automation with Claude Code hooks
- MCP Tools - Complete MCP command reference
- REST API Endpoints - Backend API documentation
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
MIT License - see LICENSE file for details
Problem: Backend fails to start or crashes immediately
Solutions:
# Check Python version
python3 --version # Should be 3.8+
# Check virtual environment is activated
which python # Should point to venv/bin/python
# Reinstall dependencies
cd claudetask/backend
rm -rf venv
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# Check port is not in use
lsof -i :3333
# Kill process if needed: kill -9 <PID>
# Check logs
python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reloadProblem: mcp:get_task_queue returns "command not found"
Solutions:
- Verify
.mcp.jsonexists in your project directory - Check MCP server path in
.mcp.jsonis correct - Restart Claude Code completely (quit and reopen)
- Check MCP server is installed:
ls ~/.claudetask_mcp/ python3 ~/.claudetask_mcp/native_stdio_server.py --help
Problem: Frontend shows "Failed to connect to backend"
Solutions:
# 1. Check backend is running
curl http://localhost:3333/health
# Should return: {"status": "healthy"}
# 2. Check backend process
ps aux | grep uvicorn
# 3. Check backend is listening on correct port
lsof -i :3333
# 4. Restart backend
cd claudetask/backend
source venv/bin/activate
python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reload
# 5. Check CORS settings if accessing from different originProblem: "database is locked" or migration errors
Solutions:
# 1. Stop backend
# Press Ctrl+C in backend terminal
# 2. Remove old database
cd claudetask/backend
rm -f claudetask.db
# 3. Run migrations (if migration script exists)
python migrate_db.py
# 4. Restart backend
python -m uvicorn app.main:app --host 0.0.0.0 --port 3333 --reloadProblem: http://localhost:3000 shows blank page or errors
Solutions:
# 1. Check Node version
node --version # Should be 16+
# 2. Clear npm cache and reinstall
cd claudetask/frontend
rm -rf node_modules package-lock.json
npm install
# 3. Check environment variable
echo $REACT_APP_API_URL
# Should be: http://localhost:3333/api
# 4. Start with environment variable
REACT_APP_API_URL=http://localhost:3333/api PORT=3000 npm start
# 5. Check browser console for errors (F12)Problem: "Port already in use" error when starting services
Solutions:
# Find what's using the port
lsof -i :3000 # Frontend
lsof -i :3333 # Backend
# Kill the process
kill -9 <PID>
# Or use different ports:
# Backend: python -m uvicorn app.main:app --port 3334
# Frontend: PORT=3001 npm startProblem: "Cannot create worktree" or "worktree already exists"
Solutions:
# 1. List existing worktrees
git worktree list
# 2. Remove stuck worktree
git worktree remove worktrees/task-<id>
# Or force remove: git worktree remove --force worktrees/task-<id>
# 3. Prune invalid worktrees
git worktree prune
# 4. Check worktrees directory permissions
ls -la worktrees/If you encounter issues not covered here:
-
Check the logs:
# Backend logs cd claudetask/backend tail -f server.log # Or check terminal output where backend is running
-
Check environment:
# Python version python3 --version # Node version node --version # Virtual environment which python # Process status ps aux | grep uvicorn ps aux | grep node
-
Search existing issues:
-
Create a new issue:
- Include error messages
- Include relevant logs
- Include your environment (OS, Python version, Node version)
- Include output of:
ps aux | grep -E "(uvicorn|node)"
For issues and questions:
- Check the Troubleshooting section above
- Search existing issues
- Create a new issue with:
- Detailed problem description
- Error messages and logs
- Environment information (OS, versions)
- Steps to reproduce
- Project Memory System (2025-11-23) - Automatic conversation persistence with RAG search
- AUTO Mode Improvements (2025-11-22) - Automatic PR creation after successful tests
- Local Worktree Merge (2025-11-22) - Complete workflow for projects without remote repos
- RAG-Enhanced Analysis (2025-11-20) - Semantic code search for better context
- RAG-Enhanced Analysis - Semantic code search for better context (β Completed)
- Project Memory System - Cross-session context preservation (β Completed)
- Advanced agent configurations with custom tools
- Integration with more Git providers (GitHub, GitLab, Bitbucket)
- Real-time task notifications via WebSocket (Partial - WebSocket infrastructure exists)
- Performance metrics and analytics dashboard
- Plugin system for custom agents
- Multi-project workspace support (β Exists, needs enhancement)
- Task templates and automation workflows
- Integration with CI/CD pipelines
- Mobile-friendly UI