Operating Modes Overview

NikCLI operates in three distinct modes, each optimized for different development scenarios. Understanding and effectively using these modes is key to maximizing your productivity.

💬 Default Chat

Interactive conversational development with step-by-step guidance

📋 Planning Mode

Strategic planning and review before implementation

🤖 Autonomous Mode

Independent AI execution with minimal supervision

Mode Switching Commands

Quick Mode Navigation

Primary Method - Shift+Tab Cycling
Shift+Tab: Cycle through modes
💬 Default → 📋 Planning → 🤖 Autonomous → 💬 Default

ESC: Return to Default Chat mode (from any mode)
Visual Indicators:
Current Mode: 💬 Default Chat
Press Shift+Tab to cycle modes

Current Mode: 📋 Planning Mode  
Press Shift+Tab to cycle modes

Current Mode: 🤖 Autonomous Mode
Press Shift+Tab to cycle modes

Default Chat Mode (💬)

Mode Characteristics

Best Use Cases

Learning & Exploration

  • Understanding new concepts
  • Exploring different approaches
  • Getting detailed explanations
  • Step-by-step tutorials

Precision Work

  • Critical system modifications
  • Custom requirement implementations
  • Code review and refinement
  • Complex debugging scenarios

Planning Mode (📋)

Planning Workflow

1

Plan Creation

Generate comprehensive implementation plans
/plan create "User authentication system with social login"

📋 Creating comprehensive implementation plan...

## User Authentication System Implementation Plan

### Project Analysis
- Current stack: React + Node.js + MongoDB
- Authentication needs: Email/password + OAuth
- Security requirements: JWT tokens, password hashing
- Integration points: Frontend auth context, protected routes

### Implementation Phases

#### Phase 1: Backend Foundation (2-3 hours)
- User model with Mongoose schema
- Password hashing with bcrypt
- JWT token generation and validation
- Authentication middleware
- Basic login/register endpoints

#### Phase 2: OAuth Integration (1-2 hours)  
- Passport.js setup for Google/GitHub
- OAuth callback handling
- User account linking logic
- Social profile data integration

#### Phase 3: Frontend Implementation (2-3 hours)
- Authentication context/provider
- Login and registration forms
- Social login buttons
- Protected route wrapper
- User profile management

#### Phase 4: Security & Testing (1-2 hours)
- Input validation and sanitization
- Rate limiting implementation
- Unit and integration tests
- Security audit and hardening

### Technical Specifications
- Database: MongoDB with Mongoose ODM
- Authentication: JWT with refresh tokens
- OAuth: Passport.js with Google/GitHub strategies
- Frontend: React Context API for state management
- Validation: Joi for backend, custom hooks for frontend

### Dependencies
- Backend: bcryptjs, jsonwebtoken, passport, passport-google-oauth20
- Frontend: react-router-dom, axios for API calls

Do you want to proceed with this plan? (y/n/modify)
2

Plan Review & Modification

Review and refine the implementation plan
> I'd like to modify the plan to include email verification

📝 Plan Modification Request: Add email verification

Updated Phase 1: Backend Foundation (3-4 hours)
- User model with email verification fields
- Email verification token generation
- Email service setup (SendGrid/Nodemailer)
- Email verification endpoints
- Modified registration flow

Updated Phase 3: Frontend Implementation (2.5-3.5 hours)
- Email verification page component
- Verification status handling
- Resend verification email functionality
- Updated registration flow with verification step

Additional Dependencies:
- Backend: nodemailer or @sendgrid/mail
- Email templates for verification

Updated timeline: 7-9 hours total

Save modified plan? (y/n)
3

Plan Execution

Execute the approved plan systematically
/plan execute

🚀 Executing Authentication System Plan

Phase 1: Backend Foundation [ACTIVE]
├── ✅ User model with Mongoose schema (5 min)
├── ✅ Password hashing implementation (3 min)
├── 🔄 JWT token system (in progress - 8 min)
├── ⏳ Email verification system
├── ⏳ Authentication middleware
└── ⏳ API endpoints

Current Task: Implementing JWT token generation and validation
Estimated completion: 15 minutes

Progress: 2/6 tasks complete (33%)

Would you like to:
[C] Continue automatic execution
[P] Pause and review current progress  
[M] Switch to manual mode for this phase
[S] Skip to next phase
4

Progress Monitoring

Track implementation progress against the plan
/plan status

📊 Authentication System Implementation Status

Overall Progress: ████████████░░░░░░░░ 60%

✅ Phase 1: Backend Foundation (100% complete)
├── ✅ User model and schema
├── ✅ Password hashing system  
├── ✅ JWT token management
├── ✅ Email verification system
├── ✅ Authentication middleware
└── ✅ Login/register/verify endpoints

🔄 Phase 2: OAuth Integration (40% complete)
├── ✅ Passport.js configuration
├── 🔄 Google OAuth strategy (in progress)
├── ⏳ GitHub OAuth strategy
├── ⏳ Account linking logic
└── ⏳ Profile data integration

⏳ Phase 3: Frontend Implementation (0% complete)
⏳ Phase 4: Security & Testing (0% complete)

Current Focus: Google OAuth integration
Next Milestone: Complete OAuth setup (ETA: 30 min)

Issues Found: None
Deviations from Plan: None

Planning Commands

Best Use Cases

Complex Projects

  • Multi-component features
  • System integrations
  • Architecture changes
  • Large refactoring efforts

Team Collaboration

  • Shared project planning
  • Task delegation
  • Progress tracking
  • Milestone management

Autonomous Mode (🤖)

Autonomous Operation

Autonomous Commands

# Start autonomous execution
/auto "task description"          # Begin autonomous mode
/autonomous "task description"    # Alias for /auto

# Execution control
pause                            # Pause execution
resume                           # Resume execution  
stop                            # Stop and save progress
abort                           # Emergency stop

# Progress monitoring
/status                         # Show execution status
/dashboard                      # Open live dashboard
/agents                         # Show agent status

Best Use Cases

Rapid Development

  • Prototyping and MVP development
  • Boilerplate generation
  • Routine implementation tasks
  • Time-sensitive projects

Large Scale Tasks

  • Full-stack feature implementation
  • System-wide refactoring
  • Migration projects
  • Performance optimization

Mode Comparison

FeatureDefault Chat 💬Planning Mode 📋Autonomous Mode 🤖
SupervisionHighMediumLow
SpeedSlowMediumFast
LearningHighMediumLow
ComplexitySimple-MediumMedium-HighAny
ApprovalEvery stepMajor milestonesSafety checkpoints
Best ForLearning, precisionComplex planningRapid development

Advanced Mode Features

Mode-Specific Configuration

Mode Transitions

💬 Default Chat Mode
> I need to plan a complex feature implementation

/plan
📋 Switched to Planning Mode

> create "E-commerce checkout system"
📋 Plan created with 4 phases, 15 tasks

> This looks good, let's implement it autonomously

/auto execute
🤖 Switched to Autonomous Mode
🚀 Beginning execution of checkout system plan...

Next Steps

Master mode switching to optimize your development workflow. Use Default Chat for learning, Planning Mode for complex projects, and Autonomous Mode for rapid implementation.