Pupa

Where agentic experiences are crystallised into real apps.

Download on the App Store

Coming soon. Pupa isn’t on the App Store just yet — email pupa-app-help@proton.me to request a TestFlight invite and try it early.

Set up the backendView on GitHubBrowse the marketplace

Why Pupa

Your agentic experience, made to last

So much of what you do with an agent is lost the moment the conversation ends — trapped in unstructured text, or scattered across the dozen services you stitch together. We keep pushing agents toward more structure, yet the results stay fragile and fragmented.

Pupa changes that. Whatever your setup — a single plain ChatGPT thread or an elaborate custom agentic pipeline — your same agent now can, by default, use and build a real app alongside you. And that app stays with you: Pupa gives it a standard to persist, travel, and stay robust long after the chat is gone and the harness changes.

It fits either way: add a Pupa app on top of the agentic setup you already have, or make it the main app you use — with the agent just helping out.

And a Pupa app is just a JSON file that Pupa connects to your backend agent. Nothing is locked in, so it’s fully portable and works with any harness.

The app surface has been evolving — step through it:

  • A laptop where Claude, with tools/MCP/skills, reads and modifies OS apps and the filesystem directly.
  • A chat app on a phone reporting OS and chat data one way to a generic backend, which runs Claude over raw OS data.
  • A Pupa MyApp of components and memories on a phone, read and modified both ways through pupa-backend, which runs Claude over OS data.

1 · Just your agent — Claude works straight on your OS — reading and modifying raw files and apps. Nothing persists as an app of its own.