Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Semi-Structured Agentic Framework. Workflows build themselves as agents discover what needs to be done, not what you predicted upfront.
| Date | Stars |
|---|---|
| 2026-07-31 | 1177 |
| 2026-08-01 | 1177 |
| 2026-08-06 | 1177 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# 🔥 Hephaestus: A Semi-Structured Agentic Framework <div align="center">     **What if AI workflows could write their own instructions as agents discover what needs to be done?** [Quick Start](https://ido-levi.github.io/Hephaestus/docs/getting-started/quick-start) • [Documentation](https://ido-levi.github.io/Hephaestus/) • [Examples](example_workflows/) • [Join our discord](https://discord.gg/FMCJeKG3dU) • [Hephaestus Dev](https://ido-levi.github.io/Hephaestus/docs/getting-started/hephaestus-dev) </div> --- ## 🎥 See Hephaestus in Action <div align="center"> https://github.com/user-attachments/assets/7b021611-2c09-494b-9da1-2ce05176dc51 *Watch how Hephaestus coordinates multiple AI agents, monitors their trajectories, and builds workflows dynamically* </div> --- ## NEW: Hephaestus Dev **Ready to use Hephaestus as a development tool?** We've built **Hephaestus Dev** - a pre-configured setup with 5 production-ready workflows for software development: | Workflow | What it does | |----------|--------------| | **PRD to Software Builder** | Build complete software from a Product Requirements Document | | **Bug Fix** | Analyze, fix, and verify bugs systematically | | **Index Repository** | Scan and index a codebase to build knowledge in memory | | **Feature Development** | Add features to existing codebases following patterns | | **Documentation Generation** | Generate comprehensive docs for existing codebases | ```bash python run_hephaestus_dev.py --path /path/to/project ``` **[Get started with Hephaestus Dev →](https://ido-levi.github.io/Hephaestus/docs/getting-started/hephaestus-dev)** --- ## The Problem I Kept Running Into I was trying to build a system where AI agents could handle complex software projects. You know the kind: "Build me an authentication system with OAuth, JWT, rate limiting, and comprehensive tests." Traditional agentic frameworks can branch and loop, but they have a limitation: **every branch needs predefined instructions.** You must write the task descriptions upfront for every scenario you anticipate. But what about discoveries you didn't anticipate? When a testing agent finds an optimization opportunity, a security issue, or a better architectural pattern? Here's what I tried instead: **Define logical phase types that are needed to solve problems - like "Plan → Implement → Test" - and let agents create tasks in ANY phase based on what they discover.** ## What Actually Happened: A Branching Tree That Builds Itself Instead of a rigid sequence, I set up phase types: - **Phase 1 (Analysis)**: Understanding, planning, investigation - **Phase 2 (Implementation)**: Building, fixing, optimizing - **Phase 3 (Validation)**: Testing, verification, quality checks The key insight: **Agents can spawn tasks in any phase they want.** A validation agent testing your auth system might discover an elegant caching pattern. Instead of being stuck (or following predefined branching logic you wrote), the agent: 1. **Creates a Phase 1 investigation task**: "Analyze auth caching pattern - could apply to 12 other API routes for 40% speedup" 2. **Keeps working** on their validation task 3. Another agent picks up the investigation task and explores it The workflow just branched itself. Not because you predicted "if optimization found, spawn investigation task" - but because the agent discovered something worth exploring and had the freedom to create work for it. This creates a **branching tree of tasks** that grows based on actual discoveries, not anticipated scenarios. Let me show you what this looks like in practice: ### Example: Building from a PRD I give Hephaestus a product requirements document: "Build a web application with authentication, REST API, and a Re
Excerpt of 11,947 characters
Read on GitHub
38
18
Claude · @anthropics
2
2
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:403b00f27e4d5ec6, topic:ai-agents, topic:autonomous-agents, desc:agentic