@agentproto/app-kit 0.6.0 → 0.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +16 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -142,6 +142,22 @@ The four surfaces form the app's public contract:
142
142
  | `artifact` | Cowork artifact | `.agentproto/artifact/index.html` | `app_artifact_get` | `create_artifact` (Cowork) |
143
143
  | `artifacts`| Decl types | inline in APP.md frontmatter | — | Discovery |
144
144
 
145
+ ### UI bridge API
146
+
147
+ A `ui` panel runs inside an MCP Apps host (or standalone via `agentproto app
148
+ serve`) and receives a `window.McpApp` bridge:
149
+
150
+ - `callTool(name, args)` — invoke an MCP tool exposed by the host.
151
+ - `sendMessage(content)` — push a user message up to the chat host.
152
+ - `updateModelContext({ content?, structuredContent? })` — replace the model
153
+ context the host sees for this panel.
154
+ - `openLink(url)` — ask the host to open a URL.
155
+ - `onTeardown(cb)` — register a cleanup callback fired when the host tears down
156
+ the panel.
157
+
158
+ In a standalone browser tab, `callTool` proxies to the daemon's `/mcp` endpoint,
159
+ while `sendMessage` and `updateModelContext` reject (there is no chat host).
160
+
145
161
  ### Skill surface flow
146
162
 
147
163
  1. The app declares `skill: { path: "/abs/path/to/skill-dir", title?, description? }`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agentproto/app-kit",
3
- "version": "0.6.0",
3
+ "version": "0.6.1",
4
4
  "description": "@agentproto/app-kit — declare an agent (with its system prompt) and its workflows in one TypeScript module and import them anywhere. A thin umbrella over AIP-42 defineAgent + AIP-15 defineWorkflow: defineApp cross-links the two (every workflow agent-step must target the app's agent, every agent workflow ref must resolve), toMastraAgent turns the AGENT.md body into a real Mastra `instructions` field, and emit writes the .agents/<id>/AGENT.md + WORKFLOW.md(+entry) pair that runs through the agentproto-run lane unchanged.",
5
5
  "keywords": [
6
6
  "agentproto",