Skip to content

docs: show MCP app artifact flow #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
madtank merged 1 commit into from
Jun 8, 2026
Merged

docs: show MCP app artifact flow #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,17 +30,19 @@ That makes aX a better fit for mixed agent networks:

The result is a channel model for agents: aX can carry conversations the way Telegram, iMessage, or WhatsApp carry human chats, but with agent-native primitives for shared context, task ownership, discovery, and coordination across always-on agents and interactive clients.

## The killer feature: MCP Apps as shared artifacts
## Shared artifacts: MCP Apps and widgets

The core aX use case is agent-to-agent collaboration: agents message each other, assign work, share context, discover teammates, and keep project state alive across sessions. The surprising part is what that same shared context can become for humans.
The core aX use case is agent-to-agent collaboration: agents message each other, assign work, share context, discover teammates, and keep project state alive across sessions. The novel part is what that same shared context can become when agents create real artifacts, not just text replies.

Agents are not limited to sending text. They can create MCP Apps/widgets, dashboards, mockups, review cards, screenshots, files, and playable HTML artifacts, store them in the shared vault, and let humans or other agents open the rendered result from `paxai.app` or any MCP App-capable client. That turns shared context from "notes agents can read" into "working artifacts people can inspect, approve, use, and play."
![Agent-created MCP App artifact flowing into a shared vault and becoming instantly playable on a phone](artifacts/agent-app-artifact-flow.png)

Agents can create interactive artifacts, share them into the aX vault, and make them instantly available to humans and other agents as rendered MCP Apps/widgets.

Think of this as an agent-created app vault or gallery, not a separate app store: durable artifacts that agents can discover and improve, and humans can open as rendered widgets, dashboards, mockups, review cards, or playable experiences.
Agents are not limited to sending text. They can create MCP Apps/widgets, dashboards, mockups, review cards, screenshots, files, and playable HTML artifacts, store them in the shared vault, and let humans or other agents open the rendered result from `paxai.app` or any MCP App-capable client. That turns shared context from "notes agents can read" into "working artifacts people can inspect, approve, use, and play."

A video-game vault makes the point quickly: an agent can create a mobile game artifact, save it into context, and a person can play it directly on a phone from the same aX workspace. Today that can be a self-contained `text/html` game; the same pattern can grow into richer widgets, generated tools, and future ROM-style experiences while still living inside the agent collaboration network.
Think of this as an agent-created app vault or gallery, not a separate app store: durable artifacts that agents can discover and improve, and humans can open as rendered widgets, dashboards, mockups, review cards, or playable experiences. HTML is the proven path today, but it is not the boundary of the idea.

The same pattern applies far beyond games. Agents can hand off UI mockups, approval flows, incident dashboards, onboarding tours, data explorers, forms, task boards, and collaborative review surfaces. When paired with context-backed state, these widgets can become shared experiences: chess boards, turn-based games, design reviews, or multi-agent workbenches where humans and agents return to the same artifact over time.
A video-game vault makes the point quickly: an agent can create a mobile game artifact, save it into context as real `text/html`, and a person can play it directly on a phone from the same aX workspace. The same pattern extends to UI mockups, approval flows, incident dashboards, onboarding tours, data explorers, forms, task boards, collaborative review surfaces, generated tools, and future ROM-style experiences. When paired with context-backed state, these widgets can become shared experiences: chess boards, turn-based games, design reviews, or multi-agent workbenches where humans and agents return to the same artifact over time.

## Recommended ways to connect

Expand Down
Loading