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.
Project memory and workflows for Claude Code and Codex. Keep stories, plans, handovers, and review evidence in your repo. Resume across sessions and follow progress in the Mac app.
| Date | Stars |
|---|---|
| 2026-07-31 | 682 |
| 2026-08-06 | 684 |
| 2026-08-15 | 694 |
| 2026-08-20 | 693 |
| 2026-08-24 | 695 |
| 2026-08-26 | 696 |
| 2026-08-27 | 697 |
| 2026-08-29 | 697 |
| 2026-08-30 | 698 |
| 2026-09-01 | 697 |
| 2026-09-02 | 699 |
| 2026-09-04 | 705 |
| 2026-09-05 | 714 |
| 2026-09-06 | 721 |
| 2026-09-07 | 726 |
| 2026-09-08 | 728 |
| 2026-09-09 | 730 |
| 2026-09-10 | 731 |
| 2026-09-11 | 733 |
| 2026-09-12 | 735 |
| 2026-09-14 | 736 |
| 2026-09-16 | 738 |
| 2026-09-17 | 739 |
| 2026-09-18 | 744 |
| 2026-09-19 | 751 |
| 2026-09-20 | 753 |
| 2026-09-21 | 754 |
| 2026-09-22 | 755 |
| 2026-09-24 | 756 |
| 2026-09-25 | 756 |
| 2026-09-26 | 757 |
| 2026-09-27 | 759 |
| 2026-09-28 | 760 |
| 2026-10-02 | 762 |
| 2026-10-03 | 763 |
| 2026-10-06 | 765 |
| 2026-10-07 | 768 |
| 2026-10-08 | 769 |
| 2026-10-10 | 770 |
| 2026-10-11 | 771 |
| 2026-10-13 | 772 |
| 2026-10-15 | 772 |
| 2026-10-17 | 772 |
| 2026-10-18 | 774 |
| 2026-10-19 | 777 |
| 2026-10-20 | 778 |
| 2026-10-21 | 781 |
| 2026-10-24 | 781 |
| 2026-10-25 | 781 |
| 2026-10-26 | 782 |
| 2026-10-30 | 783 |
| 2026-10-31 | 785 |
| 2026-11-01 | 787 |
| 2026-11-02 | 788 |
| 2026-11-04 | 788 |
Today
— stars today
This week
+6 stars this week
This month
+25 stars this month
Momentum
21.0
growth rate 0.77%/day
<p align="center"> <img src="https://raw.githubusercontent.com/Storybloq/storybloq/main/assets/logo.png" width="120" alt="Storybloq logo" /> </p> <h1 align="center">Storybloq</h1> <p align="center"> <strong>Your project’s memory. Your agents’ workflow.</strong><br /> Project memory and workflows for Claude Code and Codex. Keep stories, plans, handovers, and review evidence beside your code. Pick up work across sessions and follow progress in the optional Mac app. </p> <p align="center"> <a href="https://www.npmjs.com/package/@storybloq/storybloq"><img src="https://img.shields.io/npm/v/@storybloq/storybloq?color=333&label=npm" alt="npm version" /></a> <a href="https://github.com/Storybloq/storybloq/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-PolyForm--Shield%201.0-blue" alt="License" /></a> <img src="https://img.shields.io/badge/node-%E2%89%A520-brightgreen" alt="Node" /> <img src="https://img.shields.io/badge/claude%20code-compatible-orange" alt="Claude Code compatible" /> <img src="https://img.shields.io/badge/codex-compatible-111" alt="Codex compatible" /> </p> <p align="center"> <a href="https://storybloq.com">storybloq.com</a> · <a href="https://storybloq.com/mac">Mac app</a> · <a href="https://github.com/Storybloq/lenses">Review lenses</a> · <a href="https://storybloq.com/privacy">Privacy</a> </p> --- ## The problem A new coding session may be missing the decisions and unfinished work from the last. Project instructions describe how to work; handovers, stories, and review records capture what happened and where to continue. The real cost isn't wasted setup time. It's repeated mistakes, relitigated design decisions, hallucinated context, and linear instead of compounding work. ## The idea Every project gets a `.story/` directory of JSON and markdown files. Stories, issues, roadmap phases, session handovers, and lessons learned live there as readable files you can track with Git. Stories use ticket records in the CLI and file format. - **CLI:** `storybloq` - inspect and mutate `.story/` from the terminal. - **MCP server:** structured tools Claude Code and Codex can call directly to read and update the project and guide supported workflows. - **Skill:** invoke `/story` in Claude Code or `$story` in Codex to load project state at the start of a session. - **Mac app:** native sidebar that watches `.story/` and updates live while your AI client works (separate product, free on the App Store). ## From choosing work to the next session - **Choose the next useful story.** Recommendations account for blockers, unfinished work, and what completing a story would unblock. Recorded decisions and a ranked digest of lessons give the agent context for the choice. - **Build against a reviewed plan.** Autonomous mode guides planning, configured independent reviews, tests, and finalization. Approved plan snapshots preserve the approach that advanced to implementation. Confirmed review findings can become durable issues. - **See what was approved. Know what was checked.** Gate acknowledgments in duet workflows can pin acceptance to a plan or staged code state. These records help you inspect the work; they do not guarantee correct code or replace tests, CI, and release checks. - **Continue with the record intact.** Handovers preserve decisions and next steps. Persisted session state supports guarded continuation; automatic recovery depends on the client and the interruption. A **lesson** is a recorded pattern or mistake, with reinforcement to help useful guidance surface again. An **approval** records acceptance of particular work, within the workflow that requested it. **Coordination** records participants and assignments; the client or configured transport supplies dispatch and messages. **Recovery** uses saved state and checks before continuing, rather than assuming an interrupted action finished. Start with one story and a handover. Add [autonomous mode](https://www.storybloq.com
Excerpt of 59,765 characters
Read on GitHub
532
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:efed408a288a319e, topic:mcp, topic:mcp-server, readme:mcp server
matched fp:efed408a288a319e, topic:developer-tools
matched fp:efed408a288a319e, topic:workflow