Your AI can do more than talk.
Bring an app into the conversation. Make it yours with a few words.
Plan, track, explore — right where you talk to your AI.
It’s here: net 30 starts from the invoice date unless the contract says otherwise. I opened the Knowledge Cards app where we kept that answer, alongside the wording you later marked as the version to reuse.
Opening live appKnowledge Cards↳ You retitled a card to “Invoice wording — use this one” · just now
I see the edit. “Invoice wording — use this one” is now the version I’ll pull when another app needs it.
Here it is — in the original Knowledge Cards app, together with the two answers you added later. Nothing was reconstructed for this conversation.
Opening live appKnowledge CardsEight answers became one searchable App, with user, web, and AI images retaining their real provenance.
You renamed the card so the AI could tell which invoice wording to reuse.
The net-30 answer, renamed wording, and two later additions returned together.
Two clients are overdue. I used “Invoice wording — use this one” from Knowledge Cards, prepared two Gmail drafts — unsent for review — and logged both follow-ups on the correct client rows.
Opening live appClient Pipeline↳ Knowledge Cards read · 2 Gmail drafts ready · unsent · 2 follow-ups logged
Knowledge Cards supplied the wording, Gmail supplied the action, and Client Pipeline kept the result, context, and history.
The App Store is an app too: search working apps, open a live preview, add one, then reshape it by asking.
You are not moving a document between AIs. ChatGPT, Claude, and the app’s own URL all reopen client-pipeline: one App ID, four client rows, and one version history. A write in one surface becomes the starting state in the next.
client-pipelineLiveWrites to the app while you talk
Starts a fresh conversation
Opens without an AI conversation
Opening live appClient PipelineThe first use establishes the App contract and initial state. Later use reopens the same App ID, reads the current rows it needs, and can update the changed field instead of rebuilding the whole table. That can reduce repeated context and leave more of the model’s working window for the next decision.
The useful structure and initial state are created once, then persist beyond the chat.
The same schema and unchanged rows do not need to be narrated from scratch.
next_stepStop pasting the same background into each new chat.
Reuse the App instead of regenerating a table or dashboard.
Spend more of the model’s context on the current decision and result.
These are not two products with different features. App manifests, collections, and version history use the same MIT-licensed engine. The fork is operational: who runs it, where data lives, who updates it, and which MCP endpoint your AI opens.
The same engine, App manifests, collections, and version history model.
Apps, collections, and history keep the same shape on either path.
Create an account, connect your AI, and use a separate hosted store for your apps without installing a server.
Run the MIT-licensed engine on your own machine or server. You control deployment, storage, updates, and the MCP endpoint.
For several people, a private environment, or deployment requirements that need planning beyond a personal install.
Moving hosted data to self-hosting currently requires an export request; self-serve export and migration are not built yet. We will say so here when that changes.
What is available today, what depends on the AI host, and what is still plainly not built.
The operating model and current gaps, written down before you commit your work.
Hosted accounts use one store per account on our servers. Self-hosted installs keep it on your machine. When an AI opens an app, that data also passes through that AI provider under its privacy terms.
The engine is open source under the MIT license, so you can run it yourself. Data export is available by request today; a self-serve export button is not built yet.
Claude and ChatGPT web can render the apps. ChatGPT desktop can render them too, but a button inside an app cannot create new rows there yet because of a host limitation.
Apps are personal for now: there is no teammate sharing and no public app you can hand someone a link to. Both are on the roadmap, and sharing will be a hosted-account feature — a self-hosted install has no one to share with. Export is by request, and ChatGPT desktop still has the write limitation above. Every app version is kept so you can roll back a bad change.
Describe it once. Keep using the app after the conversation ends.