Browse by type
AI Agents, ready to use. Open source. Community-built. Bring your own key.
A quick side-by-side look at the platform's core features:
| Feature | Purpose | Requires API Key | Requires Supabase | Supports Multiple Providers |
|---|---|---|---|---|
| Individual Agents | Run a single AI agent | ✅ | ❌ | ✅ |
| Battle Mode | Compare responses from multiple AI providers | ✅ | ❌ | ✅ |
| Workflow Builder | Chain multiple AI agents together | ✅ | ✅ | ✅ |
iloveAgents is a clean, open source web platform where you can run AI agents directly in your browser.
No sign-up. No backend. No data collection. Just paste your API key and go.
Each agent is a focused tool that does one thing really well — summarize meeting notes, review code, generate SQL, write cold emails, and a lot more. The whole platform is config-driven, which means adding a new agent is as simple as adding one JavaScript object to a single file. No deep React knowledge needed.
.env files, no backend, no database. Clone and run in under a minute.The complete list of agents has been moved to AGENTS.md for better organization and scalability.
The repository contains AI agents for a wide variety of real-world use cases. The table below highlights the major categories available, helping new users quickly discover the project's capabilities.
| Category | Description |
|---|---|
| 🛠️ Engineering | Code generation, debugging, API documentation, testing, DevOps, and software architecture |
| 📚 Education | Study planning, quizzes, flashcards, DSA explanations, and learning resources |
| 📈 Productivity | Meeting notes, email writing, planning, workflows, and personal productivity |
| 📢 Marketing | SEO, blog writing, LinkedIn posts, social media, and content creation |
| 💼 Sales & Business | Lead qualification, proposals, competitive analysis, outreach, and business planning |
| 🎨 Design | UI/UX support, color palettes, typography, image prompts, and creative assets |
| 🏥 Healthcare | Wellness planning, medical summaries, patient documentation, and healthcare assistance |
| 🔬 Research & Data | Research, data science, dataset analysis, and machine learning support |
| 🔐 Security | Cybersecurity analysis, phishing detection, password reviews, and threat intelligence |
| 🌐 Specialized Domains | HR, Finance, Legal, Real Estate, Gaming, Product, Web3, and many more |
Note: The repository currently contains 130+ AI agents spanning Engineering, Education, Marketing, Healthcare, Web3, Cybersecurity, and many other domains. For the complete list of agents and detailed descriptions, see AGENTS.md.
| Provider | Logo | Models | Get Your Key |
|---|---|---|---|
| OpenAI | GPT-4o, GPT-4o-mini | platform.openai.com | |
| Anthropic | Claude Opus, Claude Sonnet | console.anthropic.com | |
| Google Gemini | Gemini 2.5 Flash | aistudio.google.com |
You can switch providers on any agent at runtime from the dropdown. No restart needed.
Pit three AI providers against each other head-to-head.
Battle Mode has its own dark, dramatic UI with color-coded provider columns (gold for OpenAI, purple for Anthropic, blue for Gemini). Each provider loads independently — if one fails, the other two still work. Access it from the "Enter Battle Mode" button on the homepage or navigate directly to /battle.
Chain multiple agents together and automate your entire process in one run.
Workflows let you connect agents in sequence — the output of each agent automatically becomes the input for the next. Build once, run with any input.
Your Input
│
▼
┌─────────────┐
│ Agent 1 │ e.g. Research Agent
└──────┬──────┘
│ output
▼
┌─────────────┐
│ Agent 2 │ e.g. PDF Summarizer
└──────┬──────┘
│ output
▼
┌─────────────┐
│ Agent 3 │ e.g. LinkedIn Post Writer
└─────────────┘
│
Final Output
If any step fails, the workflow stops at that step and shows you exactly what went wrong — with a Retry button. On success, you can copy all outputs at once.
| Route | What it does |
|---|---|
/workflows |
Browse community workflow library |
/workflows/build |
Create and save a new workflow |
/workflows/:id |
View full details of a workflow |
/workflows/:id/run |
Run a workflow step-by-step |
Get the project running quickly with the following commands:
git clone https://github.com/AditthyaSS/iloveAgents.git
cd iloveAgents
npm install
npm run dev
For complete setup instructions, environment variables, and troubleshooting, see the Getting Started section below.
# Clone the repository
git clone https://github.com/AditthyaSS/iloveAgents.git
cd iloveAgents
# Install dependencies
npm install
# Start the dev server
npm run dev
Open http://localhost:5173 in your browser.
No API provider keys are required in a .env file because
they are entered at runtime and never stored anywhere.
However, local development requires a .env.local file
for Supabase features like Workflows.
Create a .env.local file in the root directory:
VITE_SUPABASE_URL=your_supabase_url
VITE_SUPABASE_ANON_KEY=your_supabase_anon_key
Note: AI provider API keys are still entered at runtime and are never stored anywhere.
VITE_SUPABASE_URLIf you encounter connection errors, verify that the VITE_SUPABASE_URL in your .env.local file matches your Supabase project URL.
VITE_SUPABASE_ANON_KEYMake sure the VITE_SUPABASE_ANON_KEY is copied correctly from your Supabase project's API settings.
.env.local.If you recently created or updated .env.local, restart the development server:
Stop the development server and start it again:
npm run dev
Before opening an issue, verify that:
.env.local is in the project root.VITE_.The included vercel.json handles SPA routing automatically.
src/
├── agents/
│ ├── definitions/ # Each agent in its own file (auto-collected)
│ │ ├── pdf-summarizer.js
│ │ ├── code-reviewer.js
│ │ └── ... more agent definitions
│ ├── categories.js # CATEGORIES constant
│ └── registry.js # Auto-collects all definitions via import.meta.glob
├── components/
│ ├── AgentRunner.jsx # Generic agent execution UI
│ ├── AgentCard.jsx # Agent card for the homepage grid
│ ├── ApiKeyBar.jsx # Provider and API key input
│ ├── OutputRenderer.jsx # Renders markdown/text/JSON output
│ ├── ScorecardOutput.jsx # Visual scorecard for JSON output
│ ├── BattleNavbar.jsx # Battle Mode navigation bar
│ ├── Navbar.jsx # Top navigation
│ ├── Sidebar.jsx # Agent sidebar
│ └── ...
├── hooks/
│ └── useWorkflows.js # Workflow data operations (fetch, save, realtime)
├── lib/
│ ├── llmAdapter.js # Unified API adapter for all providers
│ ├── supabase.js # Realtime data client
│ └── useApiKey.js # API key state management
├── pages/
│ ├── HomePage.jsx # Landing page with agent grid
│ ├── AgentPage.jsx # Individual agent page
│ ├── WorkflowLibrary.jsx # 🆕 Public workflow library with live counters
│ ├── WorkflowBuilder.jsx # 🆕 Drag-and-drop agent chain builder
│ ├── WorkflowDetail.jsx # 🆕 Single workflow view with realtime stats
│ ├── WorkflowRunner.jsx # 🆕 Sequential agent execution engine
│ ├── BattleModeLanding.jsx # Battle Mode entry page
│ ├── BattleModeSetup.jsx # Battle configuration
│ ├── BattleModeArena.jsx # Three-column battle arena
│ └── BattleModeWinner.jsx # Winner announcement
└── main.jsx
src/agents/definitions/. The registry auto-collects them via import.meta.glob — just drop a file in and it appears.runAgent() function in llmAdapter.js handles all three providers through one unified interface.AgentRunner.jsx builds the input form from the config, constructs the prompt, and renders the response.BattleModeArena.jsx fires the same prompt to GPT-4o, Claude Sonnet, and Gemini Flash simultaneously and lets you pick the winner.WorkflowRunner.jsx chains agents sequentially using the same runAgent() adapter — output of step N becomes input of step N+1, with per-step status cards and real-time usage counters.$ claude mcp add iloveAgents \
-- python -m otcore.mcp_server <graph>