@agent-native/core 0.22.0 → 0.22.2

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 (40) hide show
  1. package/dist/action-change-marker.d.ts +11 -0
  2. package/dist/action-change-marker.d.ts.map +1 -0
  3. package/dist/action-change-marker.js +52 -0
  4. package/dist/action-change-marker.js.map +1 -0
  5. package/dist/action.d.ts +2 -2
  6. package/dist/action.js +1 -1
  7. package/dist/action.js.map +1 -1
  8. package/dist/agent/production-agent.d.ts +1 -1
  9. package/dist/agent/production-agent.d.ts.map +1 -1
  10. package/dist/agent/production-agent.js +4 -6
  11. package/dist/agent/production-agent.js.map +1 -1
  12. package/dist/cli/mcp.d.ts.map +1 -1
  13. package/dist/cli/mcp.js +18 -4
  14. package/dist/cli/mcp.js.map +1 -1
  15. package/dist/client/agent-sidebar-state.d.ts.map +1 -1
  16. package/dist/client/agent-sidebar-state.js +0 -7
  17. package/dist/client/agent-sidebar-state.js.map +1 -1
  18. package/dist/scripts/runner.d.ts.map +1 -1
  19. package/dist/scripts/runner.js +7 -0
  20. package/dist/scripts/runner.js.map +1 -1
  21. package/dist/server/action-change.d.ts +8 -0
  22. package/dist/server/action-change.d.ts.map +1 -0
  23. package/dist/server/action-change.js +38 -0
  24. package/dist/server/action-change.js.map +1 -0
  25. package/dist/server/action-discovery.d.ts.map +1 -1
  26. package/dist/server/action-discovery.js +5 -0
  27. package/dist/server/action-discovery.js.map +1 -1
  28. package/dist/server/action-routes.d.ts.map +1 -1
  29. package/dist/server/action-routes.js +4 -6
  30. package/dist/server/action-routes.js.map +1 -1
  31. package/dist/server/poll.d.ts.map +1 -1
  32. package/dist/server/poll.js +55 -3
  33. package/dist/server/poll.js.map +1 -1
  34. package/dist/templates/default/.agents/skills/actions/SKILL.md +1 -1
  35. package/dist/templates/workspace-core/.agents/skills/actions/SKILL.md +1 -1
  36. package/docs/content/external-agents.md +1 -1
  37. package/docs/content/what-is-agent-native.md +1 -1
  38. package/package.json +1 -1
  39. package/src/templates/default/.agents/skills/actions/SKILL.md +1 -1
  40. package/src/templates/workspace-core/.agents/skills/actions/SKILL.md +1 -1
@@ -247,7 +247,7 @@ export default defineAction({
247
247
  });
248
248
  ```
249
249
 
250
- `GET` + `readOnly` keeps the action side-effect-free and out of the screen-refresh poll. `publicAgent` is the **explicit opt-in** — a public web route never implies public MCP/A2A exposure; see [Actions](/docs/actions). Design/content ingest actions MUST read **live** state (the Yjs collaborative document, not the stale DB snapshot column) so the external agent sees what the user actually has on screen. Content's `pull-document` flushes any open live collab session to SQL first; design's `get-design-snapshot` returns the live Yjs file contents plus the user's resolved tweak values.
250
+ `GET` + `readOnly` keeps the action side-effect-free and out of the screen-refresh change event. `publicAgent` is the **explicit opt-in** — a public web route never implies public MCP/A2A exposure; see [Actions](/docs/actions). Design/content ingest actions MUST read **live** state (the Yjs collaborative document, not the stale DB snapshot column) so the external agent sees what the user actually has on screen. Content's `pull-document` flushes any open live collab session to SQL first; design's `get-design-snapshot` returns the live Yjs file contents plus the user's resolved tweak values.
251
251
 
252
252
  ## Advanced: local development & manual setup {#advanced}
253
253
 
@@ -53,7 +53,7 @@ It also explains why agent-native can support so many protocols without making e
53
53
 
54
54
  ## Why every agent needs a UI {#why-every-agent-needs-a-ui}
55
55
 
56
- The hot take in 2026 is "apps are dead, agents will replace UIs, everyone will just text an agent in Telegram." That's wrong.
56
+ The hot take in 2026 is "apps are dead, agents will replace UIs, everyone will just text an agent in Telegram." Eh.
57
57
 
58
58
  Even when the agent does all the heavy lifting, humans still need to:
59
59
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agent-native/core",
3
- "version": "0.22.0",
3
+ "version": "0.22.2",
4
4
  "type": "module",
5
5
  "description": "Framework for agent-native application development — where AI agents and UI share state via files",
6
6
  "license": "MIT",
@@ -68,7 +68,7 @@ Controls how the action is exposed as an HTTP endpoint:
68
68
 
69
69
  ### Screen Refresh (automatic)
70
70
 
71
- The framework auto-refreshes the UI after any successful mutating action. On completion of a non-`GET` action, the server emits a poll event that the client's `useDbSync` picks up and uses to invalidate `["action"]` React Query keys — so `list-*` / `get-*` hooks refetch without a full page reload.
71
+ The framework auto-refreshes the UI after any successful mutating action. On completion of a non-`GET` action, the framework emits a change event with `source: "action"` that the client's `useDbSync` picks up and uses to invalidate `["action"]` React Query keys — so `list-*` / `get-*` hooks refetch without a full page reload. In-process calls emit directly; dev-mode `pnpm action ...` calls also write a durable marker so the web server sees child-process action changes.
72
72
 
73
73
  Rules:
74
74
 
@@ -68,7 +68,7 @@ Controls how the action is exposed as an HTTP endpoint:
68
68
 
69
69
  ### Screen Refresh (automatic)
70
70
 
71
- The framework auto-refreshes the UI after any successful mutating action. On completion of a non-`GET` action, the server emits a poll event that the client's `useDbSync` picks up and uses to invalidate `["action"]` React Query keys — so `list-*` / `get-*` hooks refetch without a full page reload.
71
+ The framework auto-refreshes the UI after any successful mutating action. On completion of a non-`GET` action, the framework emits a change event with `source: "action"` that the client's `useDbSync` picks up and uses to invalidate `["action"]` React Query keys — so `list-*` / `get-*` hooks refetch without a full page reload. In-process calls emit directly; dev-mode `pnpm action ...` calls also write a durable marker so the web server sees child-process action changes.
72
72
 
73
73
  Rules:
74
74