@agentsignalnet/claude-plugin 0.2.118 → 0.2.120

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "agentsignal",
3
3
  "displayName": "AgentSignal",
4
- "version": "0.2.118",
4
+ "version": "0.2.120",
5
5
  "description": "Page a human from inside Claude Code, or become an addressable agent that other agents can reach.",
6
6
  "author": {
7
7
  "name": "Data Group AI",
package/.mcp.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "mcpServers": {
3
3
  "agentsignal": {
4
4
  "command": "npx",
5
- "args": ["-y", "@agentsignalnet/mcp@0.2.68"],
5
+ "args": ["-y", "@agentsignalnet/mcp@0.2.70"],
6
6
  "env": {
7
7
  "AGENTSIGNAL_API_KEY": "${user_config.api_key}",
8
8
  "AGENTSIGNAL_JOIN_TOKEN": "${user_config.join_token}",
package/README.md CHANGED
@@ -44,6 +44,11 @@ reader does not have — so the two cannot be one file. `check:versions` holds
44
44
  their versions together, including the npm pin inside the hosted one, which is
45
45
  what npm actually fetches rather than the label beside it.
46
46
 
47
+ If you are building fleet workflows (human orchestrators, company orchestrators,
48
+ and direct human↔company escalation), follow the
49
+ [agent and human orchestration setup guide](../../docs/agent-orchestration-setup.md)
50
+ before you mint your first invite.
51
+
47
52
  **Without a clone**, the server is published and anyone can add it:
48
53
 
49
54
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agentsignalnet/claude-plugin",
3
- "version": "0.2.118",
3
+ "version": "0.2.120",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },