@agent-native/core 0.28.3 → 0.28.5

package/docs/content/external-agents.md

@@ -214,7 +214,7 @@ only when it truly needs to stay visible in chat-host discovery.
 
 That makes the same app surface available to every compatible host rather than building per-client shims. The current official MCP Apps client list includes Claude, Claude Desktop, VS Code GitHub Copilot, Goose, Postman, MCPJam, ChatGPT, and Cursor; host support still varies by plan, release channel, and client version, so check the [MCP extension support matrix](https://modelcontextprotocol.io/extensions/client-matrix). ChatGPT custom MCP apps are available through developer mode for Business and Enterprise/Edu workspaces on ChatGPT web; see OpenAI's [developer mode and MCP apps](https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-apps-in-chatgpt-beta) notes.
 
-Claude Code and other CLI-first clients still receive the same resources and metadata when they support MCP Apps, but the deep link remains the reliable fallback when a host chooses not to render an iframe. In practice, every agent-native app should be authored with both: MCP Apps for inline review/edit in capable hosts, and `link` for universal round-tripping back to the full app.
+Claude Code and other CLI-first clients still receive the same resources and metadata when they support MCP Apps, but the deep link remains the reliable fallback when a host chooses not to render an iframe. In practice, every agent-native app should be authored with both: MCP Apps for inline review/edit in capable hosts, and `link` for universal round-tripping back to the full app. Human-selection tools can add a paste-back step to that fallback: for example, the Assets picker opens from the fallback link, lets the user choose media in the browser, then copies a handoff summary that the user pastes back into the chat.
 
 Claude and ChatGPT can cache tool and resource metadata for an existing custom
 connector. After changing MCP App metadata, verify with a fresh tool call; if

package/docs/content/template-assets.md

@@ -94,7 +94,11 @@ External MCP hosts should call `open-asset-picker` instead of constructing this
 iframe by hand. The action returns a browser fallback link and MCP App metadata
 for inline hosts. When a user selects an asset, the picker emits `chooseAsset`,
 the legacy `chooseImage` alias for image assets, and updates MCP App model
-context where the host supports it.
+context where the host supports it. When a host opens the fallback link in a
+normal browser tab instead of rendering the MCP App inline, selecting an asset
+copies a handoff summary and shows a copyable context block; paste that summary
+back into the chat so the external agent can use the selected media URL and
+asset metadata.
 
 For generate-and-choose flows, call `open-asset-picker` with `prompt`,
 `autoGenerate: true`, and `count: 3` (customizable from 1-6). The picker opens

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.28.3",
+  "version": "0.28.5",
   "type": "module",
   "engines": {
     "node": ">=22"