Make any AI can build it
Build it with any AI you like.
Bring it to WispOS.
WispOS is Active AI for your computer, and a whole OS built around making things you can use: for you, for your friends, for anyone who needs one. Build a game, a tool or an agent with the AI you already like, or just tell Wisper what you want and she builds it. WispOS carries its own building guide, so whichever AI you pick knows exactly how it's done. It runs from your Apps page the moment it's made, and it packs into one plain .wapp file: hand it to a friend, or put it in the App Store for everyone. It isn't tied to the AI that made it.
How it plays from an idea to the store
Ask for the app.
She builds it.
- 01
Say it
Describe it. In a sentence.
"Vibe code a game where you dodge asteroids." "Build me a tracker for my runs." Tell Wisper, using any AI you like. No template to find and no setup.
- 02
It's built
Wisper builds it, or your AI does.
A new game or app is a new project from the first minute, and its own agent builds it with WispOS's building guide. Or use the AI tool you already trust: the guide is built into WispOS, so it comes out the same shape either way.
- 03
Try it
It's in your Apps. Press Open.
WispOS runs the checks the App Store runs, and the app is in Apps → Local, on this computer, with nothing to install. The button under her reply opens it on its own page. Ask for a change and the next Open has it; while you're playing, the new build waits for Load new build.
- 04
Share it
Give it to a friend, or to everyone.
Share privately makes a .wapp only the friends you name can install. Or send it to the App Store from Apps → ··· → Submit to App Store, or ask Wisper to. Nothing is sent until you press Allow.
Open not locked to anyone's chat
Your AI builds it.
No AI owns it.
Chat companies let you build small things inside their chat. They run there, on that company's terms, and nowhere else. A WispOS creation is the opposite: one plain file on your own computer, made by whatever AI you like.
The building guide ships inside WispOS. Hand it to the AI you use, or ask Wisper to hand it to one. It lays out the folder, the manifest and every rule the store checks, so what comes back passes the first time.
A .wapp is a plain package: your files and a short manifest. A game or a tool carries no mark of the AI that made it. Switch tools next month and nothing breaks.
Run it yourself from Apps, give the file to a friend, or send it to the App Store. Same package, same checks, whichever AI made it.
Crafting what you can make
Games, apps, cards and agents.
Something to play, full screen on a phone. Games from Unity, Unreal and Godot come in as web builds.
A screen to work in: a tracker, a calculator, a dashboard, an editor. It opens on its own page with the sidebar beside it, or in a window of its own.
Wisper answers with something to look at and act on: a card per restaurant nearby, a recipe, a live checklist.
Give her your game's rulebook, your campaign notes or a folder of recipes, and she makes an agent that answers from them and names the page.
An app or card that comes to you every day, at the time and on the days the person picks.
Every app gets its own storage and runs in its own sandbox. It can't see your projects, her memory or other apps.
App Store for other people
Put it in the App Store.
Sell inside it.
Submit apps and agents
Made something good? Everyone can have it.
Submit a game, an app or an agent to the App Store, straight from WispOS: in Apps, open its ··· menu and press Submit to App Store, or press it in the bar at the top of the open app, or ask Wisper to send it. The Submit sheet signs you up as a developer for free, asks the content questions, then sends it for review. You see exactly what's sent, and nothing leaves until you press Allow. We review every app, and once it passes it's listed for everyone using WispOS.
In-app purchases
Sell unlocks, extras and subscriptions.
Declare what you sell (a one-time unlock, a pack of 10 Undos, a monthly subscription) and call wispos.purchases.buy(). WispOS slides up its own purchase sheet, asks for Touch ID or the computer's password, and keeps the record. The App Store keeps 15%; you keep the rest.
Selling inside your app is where WispOS is going: real payments are being built now, and they open with paid apps. In-app purchases in the guide
Party who it's for
Make something useful.
Keep making it better.
Build an app, share it through the App Store, and learn from the people who use it. Their feedback helps you decide what to improve next, and your next version reaches them as an update.
The app you wish existed, made the afternoon you thought of it. Ask for a change and she makes the next version.
The game you made on a weekend, the trip planner, the chore chart: one file they install into their own WispOS.
Put it in the App Store. We review it, and once it passes it's listed for everyone using WispOS.
Docs start building
Everything an app needs, in one guide.
What's in a package, the manifest, screens and safe areas, light and dark, chat cards, routines, in-app purchases, porting a game, and packing a .wapp yourself. Wisper reads the same rules, and so can any AI you point at them, so what she makes and what your own tools make come out the same shape.
FAQ building with your AI
Questions.
Can I build with Claude, Codex or Cursor?
Yes, and with anything else that writes code. WispOS carries a building guide written for any coding tool: give it to Claude Code, Codex, Cursor or whatever you use, and it knows the folder, the manifest and the rules. Print the guide with wispos --app-guide, then check and pack what it made with wispos --pack-app <folder>, with nothing else to install. A folder it packs shows up in Apps → Local by itself, ready to open, share or send to the App Store.
How is this different from GPTs, Claude artifacts and Gemini Gems?
Those live inside one company's chat. A GPT runs in ChatGPT, a Gem runs in Gemini, a Claude artifact lives in Claude, and each is made, shared and judged on that company's terms. A WispOS creation is a plain .wapp file. It runs on your own computer, opens as an app of its own in WispOS, and reaches your phone through the phone link, whichever AI built it. Build it with one, change it with another. The only thing it needs is WispOS.
If I build it with one AI, am I stuck with that AI?
No. A .wapp holds your files and a manifest, and the manifest has no place for the AI that made it. Next month, open the folder with a different AI and ask for a change: the next Open in Apps → Local runs it, and it keeps its storage. Raise the build number before it goes to anyone else.
Do I have to be a developer?
No. Tell Wisper what you want and it's built, WispOS checks it, and an Open button lands under her reply. Nothing to install. Or hand the same building guide to the AI you already use.
Where is the building guide?
Inside WispOS, so the copy on your computer always matches the WispOS that will run what you build. Wisper reads it for you. For another AI, print it with wispos --app-guide, or read the same rules in the knowledge base under Building apps for WispOS.