@mondaydotcomorg/agent-toolkit 5.18.0 → 5.20.0
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 +18 -0
- package/dist/cjs/core/index.js +311 -185
- package/dist/cjs/core/index.js.map +1 -1
- package/dist/cjs/mcp/index.js +313 -187
- package/dist/cjs/mcp/index.js.map +1 -1
- package/dist/cjs/openai/index.js +312 -186
- package/dist/cjs/openai/index.js.map +1 -1
- package/dist/esm/core/index.js +312 -186
- package/dist/esm/core/index.js.map +1 -1
- package/dist/esm/mcp/index.js +313 -187
- package/dist/esm/mcp/index.js.map +1 -1
- package/dist/esm/openai/index.js +312 -186
- package/dist/esm/openai/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 5.20.0
|
|
4
|
+
|
|
5
|
+
### Add agent management tools
|
|
6
|
+
|
|
7
|
+
Five new tools enabling agents to create and manage monday.com platform agents end-to-end:
|
|
8
|
+
|
|
9
|
+
- `manage_agent` — full lifecycle management: `create` (AI mode via prompt), `create_blank` (manual mode), `get`, `update`, `delete`, `activate`, `deactivate`, `run`
|
|
10
|
+
- `manage_agent_triggers` — manage per-agent triggers (when it runs): `list`, `add`, `remove`
|
|
11
|
+
- `manage_agent_skills` — full skill lifecycle: `create` a new skill in the catalog, `add` to agent, `remove` from agent
|
|
12
|
+
- `manage_agent_knowledge` — grant, update, or revoke an agent's access to boards and docs
|
|
13
|
+
- `agent_catalog` (READ) — browse the account-wide catalog of available trigger types and skills before wiring them to an agent
|
|
14
|
+
|
|
15
|
+
## 5.19.0
|
|
16
|
+
|
|
17
|
+
### publish_workflow — surface validation error details
|
|
18
|
+
|
|
19
|
+
- `rethrowWithContext` now includes GraphQL `extensions` data in the error message when present, so structured errors like `WORKFLOW_VALIDATION_FAILED` (with step-level issue details) are passed through to the LLM instead of being dropped
|
|
20
|
+
|
|
3
21
|
## 5.11.0
|
|
4
22
|
|
|
5
23
|
### Asset upload MCP tools
|