Not an AI assistant. An AI engineering fleet.
β‘ Parallel Agents β’ π§ AI-Native β’ π§ Developer First β’ π Production Ready
- Overview
- The Problem
- AI Agent Fleet
- Key Features
- Tech Stack
- Quick Start
- How It Works
- Architecture
- Project Structure
- Example Use Cases
- Production Features
- Security
- Roadmap
- Contributing
- License
ForgeFlow Fleet is a multi-agent AI engineering system that turns messy error logs, screenshots, or vague ideas into complete, production-ready Vercel AI agent blueprints β debugged, designed, and ready to ship β in under 60 seconds.
- π§© Debugs production issues from cryptic logs
- ποΈ Generates full-stack blueprints for AI agents
- β‘ Runs 5 parallel AI specialists simultaneously
- π Uses custom MCP servers for intelligent tooling
- πΌοΈ Processes multimodal inputs (text, images, logs, voice)
Developers face two daily productivity killers:
-
Production Debugging Hell
Cryptic error logs and stack traces waste hours of investigation time -
Idea-to-Implementation Gap
Turning concepts into structured AI agent architectures is slow and error-prone
ForgeFlow's Solution:
Deploy a 5-specialist AI fleet that works in parallel using the Vercel AI SDK, delivering comprehensive solutions in real-time.
Five specialized AI agents working in parallel:
| Agent | Role | Output |
|---|---|---|
| π Analyzer | Root cause analysis & idea refinement | Incident summary, severity assessment, technical context |
| π¨ UI Architect | Interface design & v0 generation | 2-3 production-ready v0.dev prompts |
| βοΈ Backend Engineer | System architecture & tooling | Architecture blueprint, 3-5 custom MCP tools |
| βοΈ Judge | Solution quality evaluation | Usefulness, execution, creativity scores (1-10) |
| π¬ Scriptwriter | Demo creation & storytelling | 45-60 second pitch-perfect demo script |
Five specialized agents run simultaneously using Promise.all(), not sequentially. Watch results stream in real-time as each agent completes.
- v0.dev: UI components designed with AI-generated prompts
- Vercel AI SDK: Structured outputs with
streamObjectand Zod schemas - Custom MCP Server: Production-ready tools (log parser, error analyzer, fix generator)
- Paste error logs from production
- Upload screenshots of broken UIs (vision analysis)
- Type natural language ideas
- Voice input support (coming soon)
Live streaming results powered by Vercel AI SDK's readStreamableValue for instant feedback.
| Layer | Technology | Purpose |
|---|---|---|
| Frontend | Next.js 15 (App Router) | Edge-optimized, streaming-ready dashboard |
| Styling | Tailwind CSS + Framer Motion | Responsive design with smooth animations |
| AI Orchestration | Vercel AI SDK | 5 parallel agent streams via Server Actions |
| AI Models | Claude 3.5 Sonnet (Anthropic) | Deep reasoning and dynamic prompt generation |
| Persistence | Vercel KV | Incident history and prompt versioning |
| Deployment | Vercel | Global edge deployment |
| Language | TypeScript | Type-safe development |
- Node.js 18+ installed
- Anthropic API key (get one here)
# Clone the repository
git clone https://github.com/AbhishekGupta0164/ForgeFlow-Multi-Agentic-AI-System
cd ForgeFlow-Multi-Agentic-AI-System
# Install dependencies
npm install
# Set up environment variables
cp .env.local.example .env.localEdit .env.local and add your API key:
ANTHROPIC_API_KEY=sk-ant-...Alternative: You can add your API key directly from the UI in Settings β API Keys tab.
npm run dev- Landing Page: http://localhost:3000
- Main Dashboard: http://localhost:3000/dashboard
-
User Input
Enter text, logs, screenshots, or voice commands into the Input Card -
Command Processing
Special commands (like/evolve) trigger advanced workflows -
Server Action
launchFleetActionorchestrates 5 parallelstreamObjectcalls -
AI Execution
Each agent generates structured JSON outputs simultaneously -
Real-Time Streaming
Client consumes streams viareadStreamableValue -
Dynamic UI Updates
Results appear in real-time with rich, typedAgentPreviewcomponents -
Autonomous Mode (Optional)
Auto-launches next evolutionary step in a continuous loop
flowchart TD
A["User Input<br/>Text, Logs, Screenshots, Voice"] --> B["/api/forgeflow"]
B --> C1["runAnalyzer()"]
B --> C2["runUIArchitect()"]
B --> C3["runBackendEng()"]
B --> C4["runJudge()"]
B --> C5["runScriptwriter()"]
C1 --> D["MCP Server (/api/mcp)"]
C2 --> D
C3 --> D
C4 --> D
C5 --> D
D --> E["parse_log"]
D --> F["analyze_error"]
D --> G["generate_fix"]
D --> H["suggest_v0_prompt"]
forgeflow/
βββ app/
β βββ layout.tsx # Root layout with fonts & metadata
β βββ page.tsx # Animated landing page
β βββ dashboard/ # Main ForgeFlow application
β βββ analytics/ # Session analytics dashboard
β βββ profile/ # User profile & settings
β βββ settings/ # Configuration & API keys
β βββ globals.css # Global styles & animations
β βββ api/
β βββ forgeflow/
β β βββ route.ts # Fleet orchestration (5 parallel agents)
β βββ mcp/
β βββ route.ts # MCP server (4 custom tools)
β
βββ components/
β βββ AgentCard.tsx # Animated agent status cards
β βββ BlueprintPanel.tsx # Tabbed results viewer
β
βββ lib/
β βββ schemas.ts # Zod schemas for type safety
β βββ prompts.ts # System prompts for agents
β
βββ package.json
βββ next.config.js
βββ tailwind.config.ts # Custom theme configuration
βββ tsconfig.json
Input:
Redis connection refused at port 6379
Error: ECONNREFUSED 127.0.0.1:6379
Output:
- Root cause analysis with severity score
- Monitoring dashboard (v0 prompt)
- Retry logic implementation
- Custom MCP troubleshooting tool
- Quality scores from Judge agent
- 60-second demo script
Input:
Build a commit message AI agent that generates semantic commits from git diffs
Output:
- Complete system architecture blueprint
- VS Code-style UI design (v0 prompts)
- Git diff parser MCP tools
- Agent pipeline configuration
- Quality evaluation scores
- Demo walkthrough script
-
π MCP Observability & Tracing
Live waterfall TracePanel tracking tool invocation latency and status -
π¬ Slack ChatSDK Integration
Native/forgeflowslash-command integration with rich insights -
π» WebContainer Sandbox
In-browser Node.js execution for safe MCP tool testing -
π₯ Agentic Self-Testing
HealthScore validation for JSON completeness, security, and code quality -
π§ Smart Context AI
Real-time tech stack detection with auto-suggested input modes -
π One-Click GitHub Export
Auto-generates complete repositories with MCP code, README, and architecture -
π Session Analytics
Full history and error trending powered by Vercel KV
ForgeFlow implements enterprise-grade security measures:
Security Headers (via next.config.mjs):
- HSTS: Enforces SSL/TLS for 2 years including subdomains
- CSP: Prevents XSS by restricting script/style sources
- X-Frame-Options: Prevents clickjacking (
SAMEORIGIN) - X-Content-Type-Options: Prevents MIME-type sniffing
- Referrer-Policy: Protects user privacy
- Local-First Storage: API keys stored in browser
localStorage - Encrypted Transit: TLS 1.3 encryption for all AI communications
- Visual Alerts: Blinking notifications for insecure configurations
- Never Logged: Keys never touch our servers except during active requests
- MCP Sandboxing: Restricted environment prevents unauthorized access
- WebContainer Isolation: Browser-based micro-VM completely isolated from host
- β‘ Parallel agent execution with streaming
- π§ Multimodal input (text, images, logs)
- π Custom MCP server integration
- π GitHub repository export
- π Live preview with WebContainers
- π€ Agent self-validation
- π Session analytics
- π Self-evolving agent prompts
- π€ Voice input support
- π Multi-language support
- π Team collaboration features
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
v0 β Agent Hackathon
Transform chaos into clarity.
Turn ideas into shippable AI agents.
Made with β€οΈ by the ForgeFlow Team
Live Demo β’ Report Bug β’ Request Feature
