@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.
- package/CHANGELOG.md +10 -0
- package/README.md +134 -21
- package/dist/browser/entrypoint.d.ts +1426 -1464
- package/dist/browser/meshagent-client.js +7 -2
- package/dist/browser/package.json +1 -0
- package/dist/esm/agent-client.js +18 -12
- package/dist/esm/agent.js +26 -18
- package/dist/esm/api_keys.js +21 -11
- package/dist/esm/client.js +13 -7
- package/dist/esm/completer.js +5 -1
- package/dist/esm/containers-client.js +85 -80
- package/dist/esm/datasets-client.js +105 -95
- package/dist/esm/developer-client.js +15 -11
- package/dist/esm/document.js +20 -11
- package/dist/esm/entrypoint.d.ts +1426 -1464
- package/dist/esm/entrypoint.js +12 -1
- package/dist/esm/event-emitter.js +5 -1
- package/dist/esm/helpers.js +23 -15
- package/dist/esm/index.js +49 -33
- package/dist/esm/lk-client.js +12 -7
- package/dist/esm/lk-protocol.js +8 -4
- package/dist/esm/memory-client.js +11 -7
- package/dist/esm/meshagent-client.js +88 -79
- package/dist/esm/messaging-client.js +37 -33
- package/dist/esm/package.json +1 -0
- package/dist/esm/participant-token.js +62 -34
- package/dist/esm/participant.js +9 -3
- package/dist/esm/protocol.js +43 -29
- package/dist/esm/queues-client.js +17 -12
- package/dist/esm/requirement.js +11 -4
- package/dist/esm/response.js +34 -22
- package/dist/esm/room-client.js +134 -129
- package/dist/esm/room-event.js +21 -9
- package/dist/esm/room-server-client.js +18 -13
- package/dist/esm/runtime.js +10 -1
- package/dist/esm/schema.js +18 -9
- package/dist/esm/secrets-client.js +35 -31
- package/dist/esm/services-client.js +13 -9
- package/dist/esm/storage-client.js +38 -32
- package/dist/esm/stream-controller.js +5 -1
- package/dist/esm/sync-client.js +42 -38
- package/dist/esm/tool-content-type.js +5 -1
- package/dist/esm/utils.js +20 -10
- package/dist/esm/version.js +4 -1
- package/dist/node/entrypoint.d.ts +1426 -1464
- package/dist/node/meshagent-client.js +7 -2
- package/dist/node/package.json +1 -0
- 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
|
-
##
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
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
|