@meshagent/meshagent 0.39.2 → 0.39.4

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 (48) hide show
  1. package/CHANGELOG.md +10 -0
  2. package/README.md +134 -21
  3. package/dist/browser/entrypoint.d.ts +1426 -1464
  4. package/dist/browser/meshagent-client.js +7 -2
  5. package/dist/browser/package.json +1 -0
  6. package/dist/esm/agent-client.js +18 -12
  7. package/dist/esm/agent.js +26 -18
  8. package/dist/esm/api_keys.js +21 -11
  9. package/dist/esm/client.js +13 -7
  10. package/dist/esm/completer.js +5 -1
  11. package/dist/esm/containers-client.js +85 -80
  12. package/dist/esm/datasets-client.js +105 -95
  13. package/dist/esm/developer-client.js +15 -11
  14. package/dist/esm/document.js +20 -11
  15. package/dist/esm/entrypoint.d.ts +1426 -1464
  16. package/dist/esm/entrypoint.js +12 -1
  17. package/dist/esm/event-emitter.js +5 -1
  18. package/dist/esm/helpers.js +23 -15
  19. package/dist/esm/index.js +49 -33
  20. package/dist/esm/lk-client.js +12 -7
  21. package/dist/esm/lk-protocol.js +8 -4
  22. package/dist/esm/memory-client.js +11 -7
  23. package/dist/esm/meshagent-client.js +88 -79
  24. package/dist/esm/messaging-client.js +37 -33
  25. package/dist/esm/package.json +1 -0
  26. package/dist/esm/participant-token.js +62 -34
  27. package/dist/esm/participant.js +9 -3
  28. package/dist/esm/protocol.js +43 -29
  29. package/dist/esm/queues-client.js +17 -12
  30. package/dist/esm/requirement.js +11 -4
  31. package/dist/esm/response.js +34 -22
  32. package/dist/esm/room-client.js +134 -129
  33. package/dist/esm/room-event.js +21 -9
  34. package/dist/esm/room-server-client.js +18 -13
  35. package/dist/esm/runtime.js +10 -1
  36. package/dist/esm/schema.js +18 -9
  37. package/dist/esm/secrets-client.js +35 -31
  38. package/dist/esm/services-client.js +13 -9
  39. package/dist/esm/storage-client.js +38 -32
  40. package/dist/esm/stream-controller.js +5 -1
  41. package/dist/esm/sync-client.js +42 -38
  42. package/dist/esm/tool-content-type.js +5 -1
  43. package/dist/esm/utils.js +20 -10
  44. package/dist/esm/version.js +4 -1
  45. package/dist/node/entrypoint.d.ts +1426 -1464
  46. package/dist/node/meshagent-client.js +7 -2
  47. package/dist/node/package.json +1 -0
  48. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,3 +1,13 @@
1
+ ## [0.39.4]
2
+ - Updated the Node/TS React dev package dependency graph to the newer `@meshagent/meshagent` and `@meshagent/meshagent-react` versions (`^0.38.4`) and upgraded supporting UI dependencies (including `shadcn` `^4.5.0`, `radix-ui` `^1.4.3`, and `lucide-react` `^0.525.0`).
3
+ - Updated build tooling in the React dev package (new `build:js` / `build:types` scripts using TS configs) to match the updated packaging workflow.
4
+ - Added a new shadcn/radix-based Tabs component for the developer console UI.
5
+ - Added/updated React hooks for terminal/developer-console functionality, including a WASM web terminal integration hook.
6
+ - ESM/CJS compatibility improvements in the TS SDK bundle/entrypoint, and updated TypeScript client service-spec serialization to omit `id` when creating services.
7
+
8
+ ## [0.39.3]
9
+ - Stability
10
+
1
11
  ## [0.39.2]
2
12
  - Aligned NodeJS/TypeScript SDK package versions and intra-SDK dependency references to `0.39.1` (from `0.39.0`), including updates to the `meshagent-docs` TypeScript example package.
3
13
 
package/README.md CHANGED
@@ -2,12 +2,11 @@
2
2
 
3
3
  ## MeshAgent Typescript SDK
4
4
 
5
- See an example: https://github.com/meshagent/meshagent-tailwind/tree/main/example
6
-
7
5
  MeshAgent is your platform to create, deploy, and manage AI agents collaboratively and at scale, securely and in real time.
8
6
 
9
7
  MeshAgent removes the infrastructure headaches of building and shipping AI Agents. It spins up secure, real-time "Rooms" that connect humans, agents, and shared context -- letting you launch, share, and refine agents in hours instead of weeks.
10
8
 
9
+
11
10
  ---
12
11
 
13
12
  **Documentation**: [docs.meshagent.com](https://docs.meshagent.com/)
@@ -18,26 +17,140 @@ MeshAgent removes the infrastructure headaches of building and shipping AI Agent
18
17
 
19
18
  ---
20
19
 
21
- ## Why MeshAgent?
22
-
23
- - **Real-time multi-user "Rooms" for true human-AI teamwork**: Secure workspaces, "Rooms", automatically spin-up when someone joins, tracking presence, chat, documents, and agent activity, and disappear when everyone leaves -- so people and agents stay in sync.
24
-
25
- - **Accelerated feedback loop and shortened development cycle**: Invite a colleague or stakeholder into the MeshAgent Studio Room so they can see, hear, and interact with your agent immediately -- letting you demo, gather feedback, and iterate on the agent on the same day.
26
-
27
- - **Shareable links that showcase your agent**: After you deploy an agent, MeshAgent provides you a URL so colleagues or customers can jump straight into the Room, try the agent, and give feedback -- no code checkout, IDE, or GPU required.
28
-
29
- - **Reusable and extensibly agent tools**: MeshAgent ships prebuilt, reusable toolkits for common Room interactions (e.g., file and document handling, media generation, dynamic UI interactions) and high-demand tasks (e.g., web search or document-to-Markdown conversion). Support for custom tools and the Model Context Protocol (MCP) enables you to seamlessly integrate any MCP-compatible service into a Room without changes to your applications. Tools are centrally managed like agents, allowing you to deploy them once and reuse them effortlessly.
30
-
31
- - **Built-in Observability**: Streaming logs and traces give you real-time insight into every message, agent action, and error.
32
-
33
- - **Secure and elastic by default**: Project-scoped keys, on-demand provisioning, and auto-scaling infrastructure keep Rooms private, secure, and ready for your usage needs.
34
-
35
- - **Support across languages**: The same feature set (Rooms, Agents, Tools, Messaging, Queues, Storage, Documents, etc.) is exposed through official Python, Javascript, Typescript, and Dart SDKs, so every team member can work in their preferred language.
36
-
37
- ## Getting Setup
38
-
39
- Follow our [Getting Started Documentation](https://docs.meshagent.com/introduction/get_started) to setup your MeshAgent account, create your first project, and start building agents!
20
+ ## Get Started
21
+
22
+ Install the MeshAgent CLI, connect it to your account, then run a minimal toolkit locally with the TypeScript SDK.
23
+
24
+ ### 1. Install the MeshAgent CLI
25
+
26
+ Use the install path that matches your environment:
27
+
28
+ ```bash
29
+ # macOS
30
+ brew tap meshagent/homebrew-meshagent
31
+ brew install meshagent
32
+
33
+ # Windows
34
+ choco install meshagent
35
+
36
+ # Other platforms
37
+ pipx install "meshagent[cli]" --include-deps
38
+ pipx ensurepath
39
+ ```
40
+
41
+ Then sign in and activate a project:
42
+
43
+ ```bash
44
+ meshagent setup
45
+ ```
46
+
47
+ ### 2. Install the TypeScript SDK
48
+
49
+ ```bash
50
+ npm install @meshagent/meshagent
51
+ ```
52
+
53
+ ### 3. Create `example.js`
54
+
55
+ ```js
56
+ const process = require("node:process");
57
+
58
+ const {
59
+ JsonContent,
60
+ RoomClient,
61
+ Tool,
62
+ Toolkit,
63
+ startHostedToolkit,
64
+ } = require("@meshagent/meshagent");
65
+
66
+ const inputSchema = {
67
+ type: "object",
68
+ required: ["message"],
69
+ additionalProperties: false,
70
+ properties: {
71
+ message: {
72
+ type: "string",
73
+ description: "Message to echo back.",
74
+ },
75
+ },
76
+ };
77
+
78
+ class EchoTool extends Tool {
79
+ constructor() {
80
+ super({
81
+ name: "echo",
82
+ title: "Echo",
83
+ description: "Echoes a message and adds the hosting participant name.",
84
+ inputSchema,
85
+ });
86
+ }
87
+
88
+ async execute({ message }) {
89
+ return new JsonContent({
90
+ json: {
91
+ message,
92
+ hostedBy: process.env.MESHAGENT_PARTICIPANT_NAME ?? "toolkit-host",
93
+ },
94
+ });
95
+ }
96
+ }
97
+
98
+ async function main() {
99
+ let room;
100
+ let hostedToolkit;
101
+
102
+ try {
103
+ room = new RoomClient();
104
+ await room.start();
105
+
106
+ const toolkit = new Toolkit({
107
+ name: "simple-echo",
108
+ title: "Simple Echo Toolkit",
109
+ description: "A minimal toolkit hosted from a Node process.",
110
+ tools: [new EchoTool()],
111
+ });
112
+
113
+ hostedToolkit = await startHostedToolkit({
114
+ room,
115
+ toolkit,
116
+ public_: true,
117
+ });
118
+
119
+ const result = await room.agents.invokeTool({
120
+ toolkit: "simple-echo",
121
+ tool: "echo",
122
+ arguments: {
123
+ message: "hello from startHostedToolkit",
124
+ },
125
+ });
126
+
127
+ if (!(result instanceof JsonContent)) {
128
+ throw new Error(`Expected JsonContent, got ${result.constructor.name}.`);
129
+ }
130
+
131
+ process.stdout.write(`${JSON.stringify(result.json, null, 2)}\n`);
132
+ } finally {
133
+ await hostedToolkit?.stop();
134
+ room?.dispose();
135
+ }
136
+ }
137
+
138
+ main().catch((error) => {
139
+ console.error(error);
140
+ process.exit(1);
141
+ });
142
+ ```
143
+
144
+ ### 4. Run the example
145
+
146
+ ```bash
147
+ meshagent room connect --project-id <project-id> --room <room-name> -- node example.js
148
+ ```
149
+
150
+ `meshagent room connect` starts the local Node process with the MeshAgent room environment already configured, so `RoomClient()` can connect without any extra setup in your code. If you already activated a project with `meshagent setup`, you can omit `--project-id`.
40
151
 
41
152
  ## Next Steps and Examples
42
153
 
43
154
  To see examples of agents in action and to start building your own agents check out the MeshAgent docs at [docs.meshagent.com](https://docs.meshagent.com/)
155
+
156
+ See an example: https://github.com/meshagent/meshagent-tailwind/tree/main/example