π AutoPilot AI
An intelligent AI-powered platform that turns your software concepts into comprehensive, structured project plans in minutes
Features β’ Quick Start β’ Architecture β’ Usage β’ API β’ Contributing β’ License
AutoPilot AI is an intelligent, AI-powered project planning platform that transforms vague software concepts into comprehensive, structured, and execution-ready project plans. Powered by agentic AI architecture, it analyzes requirements, recommends optimal tech stacks, assesses risks, and creates detailed execution plansβall in minutes.
|
|
β‘ Lightning Fast Planning
Generate comprehensive project plans in minutes, not days. Our multi-agent AI system processes your requirements in parallel, delivering results 50x faster than manual planning.
π€ Multi-Agent AI Architecture
Four specialized AI agents work in concert:
- Requirements Agent - Extracts functional & non-functional requirements
- Tech Stack Agent - Recommends optimal technologies with confidence scores
- Risk Assessment Agent - Identifies potential blockers and mitigation strategies
- Task Planner Agent - Creates detailed execution roadmaps with dependencies
π Data-Driven Intelligence
Every recommendation comes with:
- Confidence ratings (0-100%)
- Detailed reasoning and justification
- Risk severity indicators
- Performance metrics and KPIs
π¨ Beautiful, Accessible UX
- Modern glassmorphic design with smooth animations
- Full dark mode support with system preference detection
- WCAG AA compliant with keyboard navigation
- Responsive across all devices (mobile, tablet, desktop)
π Global & Inclusive
- Multi-language support (EN, ES, FR, DE)
- Internationalized date/time formatting
- RTL language support ready
- Accessible to screen readers
Before you begin, ensure you have the following installed:
| Requirement | Version | Download |
|---|---|---|
| Node.js | 20.x or higher | nodejs.org |
| npm | 9.x or higher | Included with Node.js |
| Git | Latest | git-scm.com |
| PostgreSQL | 14+ (optional) | postgresql.org |
1οΈβ£ Clone the Repository
# Clone via HTTPS
git clone https://github.com/Arnav10090/autopilot-ai.git
# Or clone via SSH
git clone git@github.com:Arnav10090/autopilot-ai.git
# Navigate to project directory
cd autopilot-ai2οΈβ£ Install Frontend Dependencies
# Install frontend packages
npm install
# Verify installation
npm list --depth=0Expected output:
frontend@0.1.0
βββ next@16.1.1
βββ react@19.2.3
βββ typescript@5.x
βββ tailwindcss@4.x
3οΈβ£ Install Backend Dependencies
# Navigate to backend directory
cd backend
# Install backend packages
npm install
# Return to root
cd ..Expected output:
backend@1.0.0
βββ express@4.18.2
βββ @google/generative-ai@0.24.1
βββ passport@0.7.0
βββ pg@8.16.3
4οΈβ£ Configure Environment Variables
Frontend Configuration (.env.local in root):
# Application URL
NEXT_PUBLIC_APP_URL=http://localhost:3000
# Backend API URL
NEXT_PUBLIC_API_URL=http://localhost:5000
# Feature Flags (optional)
NEXT_PUBLIC_ENABLE_ANALYTICS=true
NEXT_PUBLIC_ENABLE_CHAT=trueBackend Configuration (backend/.env):
# Server Configuration
PORT=5000
NODE_ENV=development
# Groq AI (Primary - Free tier: 14,400 requests/day)
GROQ_API_KEY=your_groq_api_key_here
# Get your key: https://console.groq.com/keys
# Model: llama-3.1-8b-instant (default, fastest)
# Alternative models: llama-3.3-70b-versatile, mixtral-8x7b-32768
# Google Gemini AI (Optional - Legacy support)
GOOGLE_API_KEY=your_gemini_api_key_here
# Get your key: https://makersuite.google.com/app/apikey
# Note: Current implementation uses Groq by default
# LLM Provider Selection (Optional)
# LLM_PROVIDER=groq # Options: groq, gemini
# GROQ_MODEL=llama-3.1-8b-instant # Override default model
# Database Configuration (Optional)
DATABASE_URL=postgresql://user:password@localhost:5432/autopilot_ai
DB_HOST=localhost
DB_PORT=5432
DB_NAME=autopilot_ai
DB_USER=your_db_user
DB_PASSWORD=your_db_password
# OAuth Configuration (Optional - for Authentication)
GOOGLE_CLIENT_ID=your_google_client_id
GOOGLE_CLIENT_SECRET=your_google_client_secret
GOOGLE_CALLBACK_URL=http://localhost:5000/auth/google/callback
GITHUB_CLIENT_ID=your_github_client_id
GITHUB_CLIENT_SECRET=your_github_client_secret
GITHUB_CALLBACK_URL=http://localhost:5000/auth/github/callback
# Session Secret (Required if using OAuth)
SESSION_SECRET=your_random_session_secret_here
# Generate with: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
# CORS Configuration
CORS_ORIGIN=http://localhost:30006οΈβ£ Start Development Servers
Option A: Run Both Servers Simultaneously
# Terminal 1 - Frontend
npm run dev
# Terminal 2 - Backend
cd backend
npm startOption B: Use Process Manager (Recommended)
# Install PM2 globally
npm install -g pm2
# Start both servers
pm2 start npm --name "frontend" -- run dev
pm2 start npm --name "backend" --cwd backend -- start
# View logs
pm2 logs
# Stop servers
pm2 stop all7οΈβ£ Access the Application
Open your browser and navigate to:
- Frontend: http://localhost:3000
- Backend API: http://localhost:5000
- API Health Check: http://localhost:5000/health
Expected Response:
{
"status": "healthy",
"timestamp": "2024-01-15T10:30:00.000Z",
"services": {
"database": "connected",
"ai": "ready"
}
}You should now see the AutoPilot AI homepage. Try creating your first project plan!
|
Automated Extraction
Smart Actions
|
// Example Output
{
functional: [
"User authentication system",
"Real-time notifications",
"Data export functionality"
],
nonFunctional: [
"99.9% uptime SLA",
"< 200ms API response time",
"GDPR compliance"
],
assumptions: [
"Users have modern browsers",
"Cloud infrastructure available"
]
} |
{
"frontend": {
"framework": "Next.js",
"confidence": 95,
"reasoning": "SSR support, SEO optimization, excellent DX"
},
"backend": {
"runtime": "Node.js",
"confidence": 90,
"reasoning": "JavaScript ecosystem, async I/O, scalable"
},
"database": {
"primary": "PostgreSQL",
"confidence": 88,
"reasoning": "ACID compliance, JSON support, mature"
}
} |
Intelligent Selection
Comprehensive Coverage
|
|
Risk Identification
Risk Categories
|
Mitigation Strategies
Interactive Features
|
graph LR
A[Project Kickoff] --> B[Module 1: Auth]
A --> C[Module 2: Core Features]
B --> D[Module 3: Integration]
C --> D
D --> E[Module 4: Testing]
E --> F[Deployment]
Task Organization
- π¦ Module-based breakdown
- π Dependency mapping
- β±οΈ Time estimates per task
- π₯ Resource allocation suggestions
- π― Priority levels (P0, P1, P2, P3)
Interactive Management
- π±οΈ Drag & drop task reordering
- β¨οΈ Full keyboard navigation support
- π Visual progress tracking
- π Bulk copy operations
- π Real-time updates
|
Capabilities
|
Features
|
- π OAuth 2.0 - Google & GitHub integration
- π Account Linking - Multiple providers, single account
- π€ Profile Management - Update details, change password
- ποΈ Secure Deletion - Account removal with confirmation
- π Session Management - Secure token handling
- π‘οΈ CSRF Protection - Built-in security measures
|
i18n Support
|
Accessibility (WCAG AA)
|
Key Performance Indicators
- π Projects analyzed over time
- β Average confidence ratings
- π€ Agent performance metrics
- π° Cost estimation tracking
- β±οΈ Average processing time
Data Visualization
- π Interactive charts (Chart.js)
- π Date range filtering (24h, 7d, 30d, 90d)
- π€ Export capabilities (CSV, JSON, PDF)
- π― Custom metric tracking
Export your project plans in multiple formats:
| Format | Use Case | Features |
|---|---|---|
| π PDF | Presentations, printing | Professional layout, embedded images |
| π DOCX | Editing, collaboration | Fully editable, styled sections |
| π CSV | Data analysis, Excel | Structured data, easy import |
| π§ JSON | API integration, backup | Complete data structure |
| π Markdown | Documentation, GitHub | Clean formatting, version control |
Export Options
- β Select specific sections to include
- π¨ Customizable templates
- π Include attachments and notes
- π Preserve links and references
graph TB
subgraph "Frontend Layer"
A[Next.js App Router]
B[React Components]
C[Context Providers]
D[TailwindCSS]
end
subgraph "Backend Layer"
E[Express Server]
F[Passport Auth]
G[Agent Orchestrator]
end
subgraph "AI Agents"
H[Requirements Agent]
I[Tech Stack Agent]
J[Risk Assessment Agent]
K[Task Planner Agent]
end
subgraph "External Services"
L[Groq API - Llama 3.1]
N[PostgreSQL]
O[OAuth Providers]
end
A --> E
B --> A
C --> B
D --> B
E --> F
E --> G
G --> H
G --> I
G --> J
G --> K
H --> L
I --> L
J --> L
K --> L
F --> O
E --> N
Key Features:
|
Key Features:
|
π€ Why Groq + Llama 3.1?
Architecture Decision:
AutoPilot AI originally supported both Google Gemini and Groq, but has migrated to use Groq exclusively for all AI agents. Here's why:
Performance Benefits:
- β‘ Blazing Fast: Up to 750 tokens/second (10-20x faster than alternatives)
- π Generous Free Tier: 14,400 requests/day (vs Gemini's 60/min limit)
- π Large Context: 128K token context window
- π High Throughput: Perfect for multi-agent orchestration
Cost Efficiency:
- Free tier sufficient for most use cases
- No credit card required for getting started
- Predictable rate limits
- No surprise billing
Model Quality:
- Llama 3.1 8B Instant: Fast, accurate for structured outputs
- Llama 3.3 70B: Available for complex reasoning tasks
- Mixtral 8x7B: Alternative for specialized use cases
Implementation:
// All agents use the same interface
export async function callGemini(prompt) {
return callGroq(prompt); // Redirects to Groq
}The callGemini function name is maintained for backward compatibility, but internally routes all requests to Groq. This allows seamless switching between providers if needed.
Fallback Strategy:
- Automatic retry with exponential backoff
- Rate limit detection and handling
- Graceful degradation to deterministic fallbacks
- Schema validation ensures consistent outputs
π Requirements Agent
Responsibilities:
- Extract functional requirements from user input
- Identify non-functional requirements (performance, security, etc.)
- Document assumptions and constraints
- Categorize and prioritize requirements
AI Model: Groq (Llama 3.1 8B Instant) Output Format: Structured JSON with categorized requirements
π οΈ Tech Stack Agent
Responsibilities:
- Analyze project requirements
- Recommend optimal technologies
- Provide confidence scores (0-100%)
- Explain reasoning for each choice
- Suggest alternatives
AI Model: Groq (Llama 3.1 8B Instant) Output Format: JSON with technology recommendations and confidence scores
β οΈ Risk Assessment Agent
Responsibilities:
- Identify potential project risks
- Classify severity (Low, Medium, High, Critical)
- Suggest mitigation strategies
- Estimate impact and likelihood
AI Model: Groq (Llama 3.1 8B Instant) Output Format: JSON with risk items and mitigation plans
π Task Planner Agent
Responsibilities:
- Break down project into modules
- Create detailed task lists
- Identify dependencies
- Estimate time and resources
- Prioritize tasks
AI Model: Groq (Llama 3.1 8B Instant) Output Format: JSON with module-based task breakdown
π How to get API keys
Groq API Key (Primary - Required):
- Visit Groq Console
- Sign up for a free account
- Navigate to API Keys section
- Generate a new key
- Copy to your
.envfile
Free Tier Benefits:
- 14,400 requests per day
- 128K context window
- Extremely fast inference (up to 750 tokens/sec)
- Multiple models available (Llama 3.1, Llama 3.3, Mixtral)
Google Gemini API Key (Optional - Legacy):
- Visit Google AI Studio
- Sign in with your Google account
- Click "Create API Key"
- Copy the key to your
.envfile
Note: The current implementation uses Groq by default for all AI agents. Gemini support is maintained for backward compatibility but not actively used.
OAuth Credentials (Optional - for Authentication):
- Google: Google Cloud Console β APIs & Services β Credentials
- GitHub: GitHub Settings β OAuth Apps β New OAuth App
5οΈβ£ Initialize Database (Optional)
If you want to use authentication and project persistence:
# Create PostgreSQL database
createdb autopilot_ai
# Run initialization script
cd backend
node src/db/init_db.js
# Verify tables created
psql autopilot_ai -c "\dt"Expected tables:
usersprojectsanalytics
Port Already in Use
# Find process using port 3000
lsof -i :3000
# Kill the process
kill -9 <PID>
# Or use a different port
PORT=3001 npm run devModule Not Found Errors
# Clear npm cache
npm cache clean --force
# Delete node_modules and reinstall
rm -rf node_modules package-lock.json
npm install
# Do the same for backend
cd backend
rm -rf node_modules package-lock.json
npm installAPI Key Issues
- Verify your API key is correct and active
- Check for extra spaces or quotes in
.envfile - Ensure
.envfile is in the correct directory - Restart the backend server after changing
.env
# Test API key
curl -H "Content-Type: application/json" \
-d '{"contents":[{"parts":[{"text":"Hello"}]}]}' \
"https://generativelanguage.googleapis.com/v1/models/gemini-pro:generateContent?key=YOUR_API_KEY"Database Connection Errors
# Check PostgreSQL is running
pg_isready
# Test connection
psql -h localhost -U your_user -d autopilot_ai
# Check connection string format
# postgresql://username:password@host:port/database
|
// Direct navigation
router.push('/create');
// Or use the SearchBar
// Press '/' and type "create" |
π Step 1: Basic Information
Required Fields:
- Project Name - Clear, descriptive name (e.g., "E-commerce Platform")
- Description - Detailed explanation of your project idea (min 50 characters)
Tips:
- Be specific about your goals
- Mention target users
- Include key features you envision
Example:
Project Name: TaskMaster Pro
Description: A collaborative task management platform for remote teams
with real-time updates, Kanban boards, time tracking, and integration
with popular tools like Slack and Google Calendar.
π₯ Step 2: Team & Timeline
Fields:
- Team Size - Number of developers (1-100+)
- Project Deadline - Target completion date
- Budget Range - Estimated budget (optional)
Impact on Recommendations:
- Smaller teams β Simpler tech stacks
- Tight deadlines β Proven, stable technologies
- Limited budget β Open-source solutions prioritized
π οΈ Step 3: Technical Constraints
Specify:
- Must-use technologies - Required by your organization
- Technologies to avoid - Known limitations or preferences
- Existing infrastructure - Cloud provider, databases, etc.
- Compliance requirements - GDPR, HIPAA, SOC 2, etc.
Example:
Must use: AWS, PostgreSQL, React
Avoid: MongoDB (team lacks experience)
Existing: AWS EC2, S3, RDS
Compliance: GDPR, SOC 2
π― Step 4: Quality & Scope
Define:
- Performance requirements - Response times, throughput
- Scalability needs - Expected user growth
- Security level - Standard, High, Critical
- Testing requirements - Unit, Integration, E2E
Slider Options:
- MVP (Minimum Viable Product)
- Standard (Production-ready)
- Enterprise (High-scale, high-security)
β Step 5: Review & Submit
Final Review:
- Verify all information is correct
- Add any additional notes
- Click "Generate Project Plan"
Processing Time:
- Simple projects: 30-60 seconds
- Complex projects: 1-2 minutes
What Happens Next:
- Requirements Agent analyzes your input
- Tech Stack Agent recommends technologies
- Risk Assessment Agent identifies potential issues
- Task Planner Agent creates execution roadmap
We welcome contributions from the community! Here's how you can help make AutoPilot AI better.
- π Report Bugs - Found a bug? Open an issue
- π‘ Suggest Features - Have an idea? Start a discussion
- π Improve Documentation - Help us make docs clearer
- π§ Submit Pull Requests - Fix bugs or add features
- π Add Translations - Help us support more languages
- β Star the Project - Show your support!
1. Fork & Clone
# Fork the repository on GitHub
# Then clone your fork
git clone https://github.com/YOUR_USERNAME/autopilot-ai.git
cd autopilot-ai
# Add upstream remote
git remote add upstream https://github.com/Arnav10090/autopilot-ai.git2. Create a Branch
# Create a feature branch
git checkout -b feature/your-feature-name
# Or a bugfix branch
git checkout -b fix/bug-descriptionBranch Naming Convention:
feature/- New featuresfix/- Bug fixesdocs/- Documentation updatesrefactor/- Code refactoringtest/- Test additions/updateschore/- Maintenance tasks
3. Make Changes
Code Style:
- Follow existing code patterns
- Use TypeScript for type safety
- Write meaningful commit messages
- Add comments for complex logic
- Update tests if applicable
Commit Message Format:
type(scope): subject
body (optional)
footer (optional)
Examples:
git commit -m "feat(chat): add message history persistence"
git commit -m "fix(export): resolve PDF generation error"
git commit -m "docs(readme): update installation instructions"4. Test Your Changes
# Run linter
npm run lint
# Run type check
npm run type-check
# Test frontend
npm run dev
# Test backend
cd backend
npm startTesting Checklist:
- β Code runs without errors
- β No TypeScript errors
- β No linting errors
- β Tested in multiple browsers
- β Responsive design works
- β Accessibility maintained
5. Submit Pull Request
# Push to your fork
git push origin feature/your-feature-namePR Guidelines:
- Provide clear description of changes
- Reference related issues (e.g., "Fixes #123")
- Include screenshots for UI changes
- Ensure all checks pass
- Request review from maintainers
PR Template:
## Description
Brief description of what this PR does
## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update
## Testing
How has this been tested?
## Screenshots (if applicable)
Add screenshots here
## Checklist
- [ ] Code follows project style
- [ ] Self-review completed
- [ ] Comments added for complex code
- [ ] Documentation updated
- [ ] No new warnings generatedWe are committed to providing a welcoming and inclusive environment. Please:
- β Be respectful and considerate
- β Welcome newcomers and help them learn
- β Focus on constructive feedback
- β Accept responsibility for mistakes
- β No harassment or discrimination
- β No trolling or insulting comments
- β No spam or self-promotion
- π¬ GitHub Discussions - Ask questions
- π GitHub Issues - Report bugs
- π§ Email: support@autopilot-ai.com
- π¦ Twitter: @AutoPilotAI
This application uses an external uptime monitor to periodically ping:
GET /api/health
to reduce cold starts on the Render free tier.
Render's free tier spins down inactive services after ~15 minutes of inactivity. Because internal cron jobs stop executing when the service is sleeping, this project relies on an external scheduler (cron-job.org or UptimeRobot) that pings the backend every 10 minutes from outside the Render VM β keeping the process warm without any in-process timer.
Health endpoint response:
{
"status": "ok",
"timestamp": "2026-06-14T12:00:00.000Z"
}- β‘ No database access
- π No authentication required
- π¦ < 5 ms response time
For full setup instructions (cron-job.org, UptimeRobot, environment variables, troubleshooting), see KEEP_ALIVE_SETUP.md.
This project is licensed under the MIT License - see the LICENSE file for details.
MIT License
Copyright (c) 2024 Arnav10090
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
|
Next.js |
React |
TypeScript |
Tailwind |
Node.js |
Express |
PostgreSQL |
Made with β€οΈ by Arnav10090