RAPP Store — A Catalog of Single-File Agents
Public catalog of "rapplications" — single-file Python agents that drop into your local brainstem and run. Like an app store, but every app is one file.
Built with:
HTMLJavaScriptJSONPython
Why this exists
If RAPP is the runtime, RAPP Store is the catalog. Every entry points at
a single .py file you can drop into your local brainstem and run. The
whole store is a JSON file plus a static viewer.
What it actually does
- Browses a catalog of "rapplications" pulled from
kody-w/RAPP - Each entry: name, purpose, capabilities, link to source
- One-click copy of the agent file into your local install
- Zero backend — the catalog is JSON, the viewer is HTML
Why this pattern matters
When the unit of distribution is one file, you eliminate the entire class of "but does it work in my environment" problems. The agent and the package are the same thing.
Prompt
Build me an "app store" for AI agents where every app is a single Python
file. The store is just a static site reading a JSON catalog. Each entry
shows the agent's purpose, its capabilities, and a one-click way to copy
the file content into the user's local agent directory. No installs, no
package managers, no dependencies beyond the Python file itself. I want
to be able to add a new agent to the store by editing one JSON file and
pushing.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- An 'app store' doesn't have to be a marketplace with billing — it can be a static page that points at fork-able files.
- When the unit of distribution is one file, you skip dependency hell entirely. The agent IS the package.
- JSON-as-database scales surprisingly far when reads dominate writes and the file is under a few MB.