@agent-native/core 0.101.10 → 0.101.11

package/dist/server/agent-engine-api-key-route.d.ts

@@ -27,11 +27,11 @@ export declare function resolveAgentEngineApiKeyWriteTarget(event: H3Event, scop
 export declare function createAgentEngineApiKeyHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
     error: any;
 } | {
+    error?: undefined;
     ok: boolean;
     key: string;
     baseUrlKey?: string;
     scope: AgentEngineApiKeyScope;
-    error?: undefined;
 }>>;
 export {};
 //# sourceMappingURL=agent-engine-api-key-route.d.ts.map

package/dist/templates/workspace-core/.agents/skills/a2a-protocol/SKILL.md

@@ -147,6 +147,31 @@ for await (const update of client.stream({
 }
 ```
 
+### Carrying explicit chat authorization
+
+When the authenticated caller has an exact consequential action that the user
+explicitly authorized in the originating chat, pass the tool name and complete
+input as `approvedActions`. The receiver accepts these grants only from a
+JWT-verified user identity, converts each one to the same content-addressed key
+as its local approval gate, and consumes it once:
+
+```ts
+await client.send(message, {
+  async: true,
+  approvedActions: [
+    {
+      tool: "send-email",
+      input: { to, subject, body, attachments },
+    },
+  ],
+});
+```
+
+Never infer authorization from request prose or broaden the input. A changed
+recipient, body, attachment, or tool produces a different key and follows the
+receiver's normal approval-required path. Static API keys and unsigned callers
+cannot carry these grants.
+
 ## JSON-RPC Methods
 
 | Method           | Purpose                          | Auth required |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.101.10",
+  "version": "0.101.11",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/src/templates/workspace-core/.agents/skills/a2a-protocol/SKILL.md

@@ -147,6 +147,31 @@ for await (const update of client.stream({
 }
 ```
 
+### Carrying explicit chat authorization
+
+When the authenticated caller has an exact consequential action that the user
+explicitly authorized in the originating chat, pass the tool name and complete
+input as `approvedActions`. The receiver accepts these grants only from a
+JWT-verified user identity, converts each one to the same content-addressed key
+as its local approval gate, and consumes it once:
+
+```ts
+await client.send(message, {
+  async: true,
+  approvedActions: [
+    {
+      tool: "send-email",
+      input: { to, subject, body, attachments },
+    },
+  ],
+});
+```
+
+Never infer authorization from request prose or broaden the input. A changed
+recipient, body, attachment, or tool produces a different key and follows the
+receiver's normal approval-required path. Static API keys and unsigned callers
+cannot carry these grants.
+
 ## JSON-RPC Methods
 
 | Method           | Purpose                          | Auth required |