Capabilities
Expose the useful parts of your product as callable, renderable building blocks.
The app store era is ending.
Clientless is a new way to build software after the fixed app container. Developers publish capabilities. Users assemble personal interfaces inside hosts like ChatGPT, Claude, the web, widgets, and whatever comes next.
decomposes into
search approve compare forecast summarize configure
The client disappears as the center of gravity.
The old model packaged work into apps: install the CRM, open the dashboard, navigate the product, learn its workflows. Clientless breaks that container apart. The useful pieces become capabilities that a host can call, combine, and render when the user needs them.
Developers publish capabilities
Retrieve account history Model a budget change Approve a request Generate a scenario
User intent
"Help me decide, then make the change."
Hosts assemble personal interfaces
Personal interfaces replace one-size-fits-all apps.
A personal interface can be created in a chat, saved for later, pinned like a widget, embedded in a workspace, or recalled when the same job returns. It is not a separate destination. It is the right interface for the current intent.
01 Ask
The user states a goal inside a host.
02 Assemble
The host combines relevant capabilities.
03 Interact
The interface appears inline with real controls.
04 Save
The interface becomes reusable when useful.
05 Recall
The user calls it again without reinstalling anything.
The protocol stack supports composition, not destinations.
MCP Apps and json-render are the technical path, but they are not the headline. The headline is that software moves from completed products to callable capabilities that hosts can turn into interfaces on demand.
User intent Ask, decide, compare, approve, explore, configure, monitor.
Host ChatGPT, Claude, web, IDE, mobile widget, desktop panel.
Personal interface A generated, reusable surface assembled for the current job.
Renderer registry Maps shared interface parts to the current platform.
json-render Specs, streams, state binding, validation, and progressive UI.
MCP Apps Standard resources, host bridge, capabilities, and actions.
Every surface becomes a host for capabilities.
Native MCP hosts can render interactive UI inline. Non-native targets can become hosts with a small adapter. The important shift is not the shell; it is the death of the app as the only unit of software.
Host OpenAI ChatGPT Apps SDK brings interactive capability surfaces into ChatGPT.
Host Claude Claude and Claude Desktop are current MCP Apps targets.
Host Developer tools VS Code GitHub Copilot, Goose, Postman, MCPJam, and Cursor-class clients.
Web WebHost A browser adapter for public sites, documentation, and reusable interfaces.
Mobile iOS Personal interfaces can appear as app screens, sheets, or widgets.
Desktop macOS Capabilities can surface as command panes, menu views, or saved tools.
Desktop Windows Task panes and assistant surfaces become capability hosts.
Future Endpoint packages Local deployment can package capability endpoints when that is useful.
Developers stop shipping completed destinations.
The developer role changes from building finished apps to publishing the capabilities users can compose. The product becomes a set of trusted actions, views, models, and rules that hosts can assemble into personal interfaces.
Personal interfaces
Let users assemble, save, and recall the exact interface their work needs.
Hosts everywhere
Meet users inside chats, browsers, widgets, desktops, IDEs, and future surfaces.