forgeOS is an AI-native workforce platform that lets companies assemble virtual departments staffed by specialized AI agents.
Instead of asking one generic chatbot to handle everything, forgeOS gives each business function its own AI workforce — with dedicated agents for content, SEO, design, advertising, HR, finance, sales, and more.
For complex goals, the built-in Project Manager agent automatically determines which departments are needed, explains why, and coordinates the work across them.
Built for the AI Factory — native.builder Hackathon · August 2026
Most AI applications work like this:
User → Chatbot → Answer
But real business work looks more like this:
Business Goal
│
▼
Project Manager
│
├── Marketing
│ ├── Content Writer
│ ├── SEO Expert
│ ├── Designer
│ ├── Ads Manager
│ └── Analytics Agent
│
├── Sales
│ ├── Lead Finder
│ ├── CRM Agent
│ └── Proposal Writer
│
└── Finance
├── Accountant
├── Auditor
└── Expense Agent
forgeOS turns AI from a single assistant into an AI workforce.
Users can simply describe a business goal without selecting a department.
For example:
"Launch our product in the UAE."
The Project Manager analyzes the goal and determines which departments are actually required.
It can:
- Analyze the business objective
- Select relevant departments
- Determine the execution order
- Explain its reasoning
- Create department-level tasks
- Route work to specialized AI agents
- Track the resulting outputs
forgeOS provides multiple AI-powered business departments.
| Department | Specialized Agents |
|---|---|
| 📣 Marketing | Content Writer, SEO Expert, Designer, Ads Manager, Analytics Agent |
| 👥 HR | Recruiter, Interviewer, Payroll, Policy Assistant |
| 💰 Finance | Accountant, Auditor, Expense Agent |
| 🤝 Sales | Lead Finder, CRM Agent, Proposal Writer |
Each agent has a dedicated role and system prompt.
This prevents every agent from producing the same generic response.
Every agent is designed for a specific business function.
For example:
Content Writer
Produces:
- Blog drafts
- Social media captions
- Marketing copy
- Content ideas
SEO Expert
Produces:
- Keyword strategies
- Search intent analysis
- Content optimization recommendations
- SEO plans
Designer
Produces:
- Visual direction
- Color palettes
- Creative concepts
- Design recommendations
Ads Manager
Produces:
- Ad copy
- Audience targeting
- Campaign structures
- Advertising strategies
The same principle applies across HR, Finance, and Sales.
When a task is submitted, users can watch the workforce execute it.
Agent states move through:
IDLE
↓
WORKING
↓
COMPLETED
Outputs appear in the interface as agents finish their work.
The frontend uses Supabase Realtime with polling as a fallback to keep the UI synchronized with backend execution.
forgeOS doesn't rely on temporary chat history.
Tasks and outputs are persisted in PostgreSQL.
This means users can:
- Refresh the page
- Return later
- Review previous projects
- Access completed agent outputs
- Continue working from task history
Every completed agent output can be:
- 📋 Copied to clipboard
- 📄 Downloaded as a PDF
This turns AI responses into reusable business deliverables.
forgeOS uses:
- Supabase Authentication
- PostgreSQL
- Row Level Security (RLS)
Each user can only access their own tasks and outputs.
┌─────────────────────────────────────────────────────────────┐
│ FRONTEND │
│ React + TypeScript │
│ │
│ Dashboard → Departments → Project Manager → Agent Outputs │
└──────────────────────────────┬──────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ SUPABASE │
│ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────┐ │
│ │ Auth │ │ PostgreSQL │ │ Edge Functions │ │
│ │ │ │ │ │ │ │
│ │ User Login │ │ Tasks │ │ forge-ai │ │
│ │ │ │ Agents │ │ project-manager │ │
│ │ │ │ Outputs │ │ │ │
│ └─────────────┘ └──────────────┘ └────────┬────────┘ │
└─────────────────────────────────────────────────┼───────────┘
│
▼
┌───────────────────────┐
│ AI / LLM API │
│ │
│ OpenAI-compatible │
│ BYOK endpoint │
└───────────────────────┘
The AI-native workflow starts with a single business goal.
User
│
│ "Launch our product in the UAE"
▼
Project Manager
│
├── Analyzes goal
│
├── Selects relevant departments
│
└── Explains reasoning
│
▼
┌─────────────────────────────┐
│ Selected Departments │
│ │
│ Marketing │
│ Sales │
│ Finance │
└──────────────┬──────────────┘
│
▼
Department Tasks
│
▼
Specialized Agents
│
▼
LLM Generation
│
▼
Persistent Outputs
│
▼
Live Dashboard
Users can also directly select a department.
User
│
▼
Select Department
│
▼
Enter Goal
│
▼
Create Task
│
▼
Department Agents
│
├── Agent 1
├── Agent 2
├── Agent 3
└── Agent 4...
│
▼
LLM Generation
│
▼
Saved Outputs
│
▼
Live Agent Cards
Each agent has its own:
- Name
- Role
- Description
- Avatar
- Department
- Dedicated system prompt
Conceptually:
Agent
├── Department
├── Role
├── Description
└── System Prompt
│
▼
LLM API
│
▼
Role-specific output
This is important because forgeOS doesn't simply send the same prompt to multiple AI models.
Instead:
Marketing Goal
│
├── Content Writer → Content deliverable
│
├── SEO Expert → SEO strategy
│
├── Designer → Visual direction
│
├── Ads Manager → Ad campaign
│
└── Analytics → Measurement strategy
Each agent approaches the same business goal from a different professional perspective.
forgeOS uses Supabase PostgreSQL.
Stores available AI departments.
id
slug
name
description
icon
color
Stores specialized AI workforce members.
id
department_id
name
role
description
avatar_letter
system_prompt
Stores department-level work.
id
user_id
department_id
goal
status
created_at
completed_at
project_manager_task_id
Stores individual agent deliverables.
id
task_id
agent_id
agent_name
agent_role
content
status
created_at
completed_at
Stores Project Manager executions.
id
user_id
goal
departments
reasoning
department_task_ids
status
final_report
created_at
completed_at
Row Level Security is enabled throughout the application.
The security model ensures:
User A
│
└── Can access User A's data
User B
│
└── Can access User B's data
Users cannot access another user's tasks or generated outputs.
| Layer | Technology |
|---|---|
| Frontend | React + TypeScript |
| Styling | Tailwind CSS |
| Routing | React Router |
| Icons | Lucide React |
| Markdown | react-markdown + remark-gfm |
| PDF Export | jsPDF |
| Backend | Supabase |
| Database | PostgreSQL |
| Authentication | Supabase Auth |
| Security | Row Level Security |
| Serverless Functions | Supabase Edge Functions |
| AI | OpenAI-compatible AI/ML API |
| Realtime | Supabase Realtime |
| Deployment | native.builder |
| Version Control | GitHub |
forgeOS uses two main Supabase Edge Functions.
Responsible for executing department-level AI work.
Goal
│
▼
Department
│
▼
Agents
│
▼
Role-specific prompts
│
▼
LLM API
│
▼
Agent outputs
│
▼
Supabase
Responsible for AI-native orchestration.
Business Goal
│
▼
Project Manager LLM
│
├── Relevant departments
│
└── Reasoning
│
▼
Department Tasks
│
▼
forge-ai
A user enters:
"Launch our new SaaS product in the UAE."
The Project Manager may determine that the goal requires:
- UAE-focused content strategy
- SEO opportunities
- Visual campaign direction
- Advertising strategy
- Ideal customer profile
- Lead generation strategy
- Sales proposal
- Launch budget
- Advertising allocation
- Expense planning
The user doesn't need to manually decide which departments are required.
forgeOS makes that decision.
Traditional AI:
Ask → Answer
AI tools:
Choose Tool → Enter Prompt → Get Output
forgeOS:
Business Goal
↓
AI Project Manager
↓
Understands the goal
↓
Selects departments
↓
Coordinates specialized agents
↓
Generates real deliverables
↓
Stores everything
↓
Tracks execution
The core idea is simple:
Don't build another chatbot. Build an AI workforce.
| Capability | forgeOS |
|---|---|
| Specialized AI agents | ✅ |
| AI departments | ✅ |
| Automatic department routing | ✅ |
| Project Manager agent | ✅ |
| Visible routing reasoning | ✅ |
| Persistent outputs | ✅ |
| Live agent status | ✅ |
| Task history | ✅ |
| PDF export | ✅ |
| Markdown rendering | ✅ |
| Authentication | ✅ |
| Row Level Security | ✅ |
| Realtime updates | ✅ |
| BYOK AI API | ✅ |
You'll need:
- Node.js
- A Supabase project
- An AI/LLM API key
- A configured frontend environment
git clone <https://github.com/anhaalishba/ForgeOS>
cd forgeOSnpm installCreate a .env file:
VITE_SUPABASE_URL=your_supabase_url
VITE_SUPABASE_ANON_KEY=your_supabase_anon_keyConfigure the required AI API credentials in your Supabase Edge Function secrets.
Never expose private API keys in frontend code.
Create your Supabase project and configure:
- Authentication
- PostgreSQL tables
- Row Level Security
- Realtime
- Edge Functions
Seed the departments and agents with their dedicated system prompts.
npm run devThen open the local development URL shown by Vite.
forgeOS was built and deployed using native.builder.
The repository is synchronized with GitHub for version control and development.
The production architecture consists of:
React Frontend
│
▼
native.builder
│
▼
Supabase
├── Authentication
├── PostgreSQL
├── Realtime
└── Edge Functions
│
▼
AI / LLM API