A distributed app store for projects built with AI coding agents. Each store is an apps.json in a GitHub repo. A build script aggregates them into a unified catalog on GitHub Pages. No backend or database needed. just JSON.
Adding your apps: create an apps.json, open a PR. Or tell your AI agent to do it the spec is designed for that.
Built on Appétit (https://github.com/f/appetit), a standalone App Store UI in vanilla HTML/CSS/JS you can deploy as your own store. WVW federates multiple Appétit instances into one catalog.
I built Agentlytics because I use multiple AI coding editors and had no way to see how I actually use them.
It's a single-command local dashboard that reads chat history from Cursor, Windsurf, Claude Code, VS Code Copilot, Zed, Antigravity, and OpenCode. (contribution needed for more support)
Technically it's a Node.js CLI that reads from local SQLite databases, state.vscdb files, JSONL logs, and (for Windsurf) a local ConnectRPC API exposed by the running language server. Everything gets normalized into a local SQLite cache and served via Express to a React frontend with Chart.js.
I'm Fatih, maintainer of prompts.chat. I've built a new NPM package called "typed prompts" which is a new approach to write chat, image, audio, video prompts using types and methods. It's actually an opinionated string builder, but it works!
honestly, I used to like writing README files before the AI (see my other repos), but I don’t like writing them anymore. GPT does it really well, it may have some mistakes but thankfully, you guys highlight them :)
totally agree. in principle, commit histories should be treated as immutable, especially on shared or production branches.
this tool is not meant to rewrite public history or alter real project timelines. it's more of a utility for personal or experimental repos (or branches), the kind of messy ones full of "update again" commits that never had a proper history. that's exactly why I built it.
Agreed! I've already added several warnings and disclaimers to the README :)
It's really meant to be a "use it once or twice in your lifetime" kind of tool, not something to run on every project. Actually, mostly shouldn't.
Good point. The purpose of git-rewrite-commits isn’t to "polish" history or rewrite meaning, it’s more of a rescue tool for those chaotic early stages of side projects (like mine) where commits are basically "update again" for months.
In those cases, the "intent" was never recorded in the first place, so the AI is just giving some structure and readability to what’s already lost context.
It’s not about pretending the repo was well maintained, it’s about making messy histories a bit more understandable for humans (and future me) without rewriting the actual code or meaning.
Just like any 3rd party server, it needs its own auth i think. like Sentry MCP. You want to track your own, authenticated servers on Sentry. So you need to auth with your own creds.
MCP has announced "elicitations" as part of the protocol (as draft) which made me excited. I wrote about how it standardizes interactive AI workflows - basically formalizing the AI-generated UI concept I was exploring already.
Adding your apps: create an apps.json, open a PR. Or tell your AI agent to do it the spec is designed for that.
Built on Appétit (https://github.com/f/appetit), a standalone App Store UI in vanilla HTML/CSS/JS you can deploy as your own store. WVW federates multiple Appétit instances into one catalog.
Source: https://github.com/f/wvw.dev