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
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!
Happy to hear your feedbacks!
I'm disappointed in your justification that AI slop mistakes are acceptable because "thankfully" you can use other people to find them for you.
"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."
What is the "strongest plausible interpretation" of that comment? Because I interpreted it in the exact same way, and don't really see any other possible interpretation.
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.
A one char ID on a web app is all very well but is the extra hassle worth it?