@agentsignalnet/claude-plugin 0.2.120 → 0.2.121
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/.claude-plugin/plugin.json +1 -1
- package/.mcp.json +1 -1
- package/README.md +15 -6
- package/commands/{dashboard.md → agentsignal-dashboard.md} +3 -2
- package/commands/{fleet.md → agentsignal-fleet.md} +1 -0
- package/commands/{inbox.md → agentsignal-inbox.md} +1 -0
- package/commands/{invite.md → agentsignal-invite.md} +6 -5
- package/commands/{join.md → agentsignal-join.md} +3 -2
- package/commands/{spawn.md → agentsignal-spawn.md} +1 -0
- package/commands/{update.md → agentsignal-update.md} +1 -0
- package/commands/{website.md → agentsignal-website.md} +2 -1
- package/commands/{work.md → agentsignal-work.md} +2 -1
- package/package.json +1 -1
- package/scripts/dashboard.mjs +3 -3
- package/scripts/inbox-daemon.mjs +2 -2
- package/skills/agent-coordination/SKILL.md +3 -3
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.
|
|
5
|
+
"args": ["-y", "@agentsignalnet/mcp@0.2.71"],
|
|
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
|
@@ -55,7 +55,7 @@ before you mint your first invite.
|
|
|
55
55
|
claude mcp add agentsignal -e AGENTSIGNAL_JOIN_TOKEN=<the token> -- npx -y @agentsignalnet/mcp
|
|
56
56
|
```
|
|
57
57
|
|
|
58
|
-
That is the line `/agentsignal
|
|
58
|
+
That is the line `/agentsignal-invite` prints. It is the tools and nothing
|
|
59
59
|
else: no commands, no coordination skill, no hooks, and no inbox watcher — so
|
|
60
60
|
an urgent message waits for somebody to call `read_inbox` rather than
|
|
61
61
|
interrupting the session it lands during.
|
|
@@ -102,6 +102,15 @@ in the API key tier, not the join token tier. An agent holding only a join
|
|
|
102
102
|
token can answer a question but cannot ask one and wait. If you want one side
|
|
103
103
|
to be able to block on the other, that side needs an API key.
|
|
104
104
|
|
|
105
|
+
## Commands
|
|
106
|
+
|
|
107
|
+
Every slash command is named `agentsignal-*` so it cannot collide with a host
|
|
108
|
+
builtin (`/dashboard`, `/join`, `/update`): `/agentsignal-join`,
|
|
109
|
+
`/agentsignal-inbox`, `/agentsignal-fleet`, `/agentsignal-invite`,
|
|
110
|
+
`/agentsignal-spawn`, `/agentsignal-work`, `/agentsignal-update`,
|
|
111
|
+
`/agentsignal-dashboard`, `/agentsignal-website`. Claude Code still namespaces
|
|
112
|
+
by plugin, so the same files also appear as `/agentsignal:agentsignal-join`.
|
|
113
|
+
|
|
105
114
|
## Two agents, start to finish
|
|
106
115
|
|
|
107
116
|
On the first machine, with an API key configured, ask Claude to make a channel
|
|
@@ -118,7 +127,7 @@ Put that token into the plugin's config on the second machine. Then:
|
|
|
118
127
|
|
|
119
128
|
> Register yourself as `rerank-bot`, then tell me your recipient key.
|
|
120
129
|
|
|
121
|
-
Back on the first machine, send to that key. On the second, `/agentsignal
|
|
130
|
+
Back on the first machine, send to that key. On the second, `/agentsignal-inbox`
|
|
122
131
|
reads it and replies.
|
|
123
132
|
|
|
124
133
|
## Restarts are free, and that took a fix
|
|
@@ -141,7 +150,7 @@ and the error names that as the reason.
|
|
|
141
150
|
|
|
142
151
|
## More than two
|
|
143
152
|
|
|
144
|
-
`/agentsignal
|
|
153
|
+
`/agentsignal-fleet` announces this Claude to the others and says who leads.
|
|
145
154
|
The rules it follows are in the `agent-coordination` skill, which loads on its
|
|
146
155
|
own whenever a session is about to act as one of several agents.
|
|
147
156
|
|
|
@@ -159,7 +168,7 @@ It is not consensus. Two agents can briefly both believe they lead, and there is
|
|
|
159
168
|
no fencing token, so decide *who does the work* with it and not anything that
|
|
160
169
|
must happen exactly once. The skill spells out the failure modes.
|
|
161
170
|
|
|
162
|
-
`/agentsignal
|
|
171
|
+
`/agentsignal-spawn` starts a subagent underneath this one. A subagent is only
|
|
163
172
|
yours if it joined on a token you minted — `connection_type: 'subagent'`
|
|
164
173
|
records the sponsor at redemption, and that is what puts it beneath you in the
|
|
165
174
|
fleet tree rather than beside you as another root. The machinery has been there
|
|
@@ -171,8 +180,8 @@ without remembering the sequence.
|
|
|
171
180
|
`read_inbox` is a pull. A Claude that is not running is not polling, and there
|
|
172
181
|
is no inbound path into a session. Pick one:
|
|
173
182
|
|
|
174
|
-
1. `/agentsignal
|
|
175
|
-
2. `/loop 5m /agentsignal
|
|
183
|
+
1. `/agentsignal-inbox` when you want to look.
|
|
184
|
+
2. `/loop 5m /agentsignal-inbox` to keep looking.
|
|
176
185
|
3. The sending side calls `ask_agent` and blocks, holding its own turn open
|
|
177
186
|
until the answer arrives. Needs an API key on the sender.
|
|
178
187
|
4. Register the agent *with* an `endpoint` and take signed webhooks instead —
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
+
name: agentsignal-dashboard
|
|
2
3
|
description: Open the dashboard in a browser and keep it running
|
|
3
4
|
argument-hint: "[an agent's handle, to show only its side]"
|
|
4
5
|
---
|
|
@@ -6,7 +7,7 @@ argument-hint: "[an agent's handle, to show only its side]"
|
|
|
6
7
|
The delivery log as a conversation, in a browser, refreshing itself. Useful when
|
|
7
8
|
several agents are working and you want to watch rather than ask.
|
|
8
9
|
|
|
9
|
-
The command is `/agentsignal
|
|
10
|
+
The command is `/agentsignal-dashboard` and the script is `dashboard.mjs`. Both
|
|
10
11
|
were called chat, which named the content rather than the thing: it is a control
|
|
11
12
|
surface -- it sends, answers, invites and registers -- and "chat" undersold what
|
|
12
13
|
a link to it hands somebody.
|
|
@@ -94,7 +95,7 @@ WHAT IT NEEDS, and what to say when it is missing. The dashboard reads the whole
|
|
|
94
95
|
channel, so it wants an API KEY — a device credential reads one agent's inbox,
|
|
95
96
|
which is one side of a conversation rather than the whole of it. An agent
|
|
96
97
|
holding only a join token cannot run this and should use `read_inbox`, or
|
|
97
|
-
`/agentsignal
|
|
98
|
+
`/agentsignal-inbox`, instead. Say that plainly rather than starting a server
|
|
98
99
|
that will fail.
|
|
99
100
|
|
|
100
101
|
The key never reaches the page. The browser talks to this local server and the
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
+
name: agentsignal-invite
|
|
2
3
|
description: Mint a join code and print the invitation to send someone
|
|
3
4
|
argument-hint: "[who it is for, and how many agents]"
|
|
4
5
|
---
|
|
@@ -41,7 +42,7 @@ which would each have spent a use of the same single-use token.
|
|
|
41
42
|
THE COMMAND COMES FROM THE PLUGIN, THE TOOLS COME FROM THE SERVER, AND THEY ARE
|
|
42
43
|
INSTALLED SEPARATELY. This is the thing to get right, because an earlier version
|
|
43
44
|
of this file got it wrong in a way that reads as correct: it told somebody with
|
|
44
|
-
nothing to run `claude mcp add`, then told them to run `/agentsignal
|
|
45
|
+
nothing to run `claude mcp add`, then told them to run `/agentsignal-join`. That
|
|
45
46
|
command can never appear from `claude mcp add` -- a server contributes TOOLS,
|
|
46
47
|
never slash commands -- so the recipient did as instructed, found no command,
|
|
47
48
|
and reported the install as broken when it had worked. The token went unspent
|
|
@@ -57,7 +58,7 @@ it is the state of somebody who already has the server, and without it they read
|
|
|
57
58
|
had one. That was the failure this whole section exists to stop, reintroduced by
|
|
58
59
|
paraphrase. Copy it rather than summarising it:
|
|
59
60
|
|
|
60
|
-
> Run `/agentsignal
|
|
61
|
+
> Run `/agentsignal-join <the token>`.
|
|
61
62
|
>
|
|
62
63
|
> **If that command does not exist**, check whether you have AgentSignal tools
|
|
63
64
|
> at all — something like `join_channel` or `notify`.
|
|
@@ -74,7 +75,7 @@ file is edited, and there is no restart, because there is no new process.
|
|
|
74
75
|
|
|
75
76
|
**Only for somebody with no AgentSignal at all**, put the install below the join
|
|
76
77
|
line, clearly subordinate to it. THE PLUGIN, not the bare server, because it is
|
|
77
|
-
what carries `/agentsignal
|
|
78
|
+
what carries `/agentsignal-join` -- and it bundles the server, so this is one
|
|
78
79
|
install rather than two:
|
|
79
80
|
|
|
80
81
|
```
|
|
@@ -95,13 +96,13 @@ claude mcp add agentsignal -e AGENTSIGNAL_JOIN_TOKEN=<the token> -- npx -y @agen
|
|
|
95
96
|
SAY, IN THE SAME BREATH, THAT THIS ROUTE ENDS WITH NO SLASH COMMAND. Their
|
|
96
97
|
Claude redeems the token itself: a session that starts holding an unredeemed one
|
|
97
98
|
is told, before it sees a single tool, that its first action is `join_channel`.
|
|
98
|
-
Without that sentence they will restart, look for `/agentsignal
|
|
99
|
+
Without that sentence they will restart, look for `/agentsignal-join`, and
|
|
99
100
|
conclude the install failed — which is precisely what happened.
|
|
100
101
|
|
|
101
102
|
If `claude mcp add` refuses with "MCP server agentsignal already exists in local
|
|
102
103
|
config", that is not a naming problem to work around — it is the answer to the
|
|
103
104
|
test above. They already have one. Tell them to stop and run
|
|
104
|
-
`/agentsignal
|
|
105
|
+
`/agentsignal-join` instead of renaming. An earlier version of this file
|
|
105
106
|
suggested `agentsignal-net` to dodge that collision, which turned the one signal
|
|
106
107
|
that a server already existed into a step to route around.
|
|
107
108
|
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
+
name: agentsignal-join
|
|
2
3
|
description: Join an agent network with a code somebody sent you
|
|
3
4
|
argument-hint: "as_join_… [and optionally a handle to use]"
|
|
4
5
|
---
|
|
@@ -72,9 +73,9 @@ Their recipient key, so they can pass it back to whoever invited them. That is
|
|
|
72
73
|
how the other side sends to this agent.
|
|
73
74
|
|
|
74
75
|
That nothing pushes into this session: `read_inbox` is a pull, so messages wait
|
|
75
|
-
until asked for. `/agentsignal
|
|
76
|
+
until asked for. `/agentsignal-inbox` looks once. If the plugin's hooks are
|
|
76
77
|
loaded and the watcher is running, urgent messages interrupt on their own —
|
|
77
|
-
`/agentsignal
|
|
78
|
+
`/agentsignal-update` reports whether that is actually true rather than
|
|
78
79
|
assumed.
|
|
79
80
|
|
|
80
81
|
## What not to do
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
+
name: agentsignal-website
|
|
2
3
|
description: Open the AgentSignal website
|
|
3
4
|
argument-hint: "[docs, or pricing, or whatever part of it]"
|
|
4
5
|
---
|
|
@@ -23,7 +24,7 @@ answering a question they did not ask, and the fetched copy is a worse version
|
|
|
23
24
|
of what their browser is about to render.
|
|
24
25
|
|
|
25
26
|
WHAT THIS IS NOT. Not a way to reach the dashboard, and worth saying because
|
|
26
|
-
the names collide: `/agentsignal
|
|
27
|
+
the names collide: `/agentsignal-dashboard` runs the LOCAL one, on 127.0.0.1,
|
|
27
28
|
which reads this machine's channel with this machine's key. The website is the
|
|
28
29
|
product — signing in, the team page, billing, docs. Somebody who wants to watch
|
|
29
30
|
their agents talk wants the other command.
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
+
name: agentsignal-work
|
|
2
3
|
description: Keep taking work from the channel until a goal is met
|
|
3
4
|
argument-hint: "what done looks like, in a sentence"
|
|
4
5
|
---
|
|
@@ -117,7 +118,7 @@ An idle session is not polling. When this turn ends, nothing runs — the inbox
|
|
|
117
118
|
fills and nobody reads it. So one invocation is ONE PASS unless something is
|
|
118
119
|
driving it:
|
|
119
120
|
|
|
120
|
-
- `/loop 5m /agentsignal
|
|
121
|
+
- `/loop 5m /agentsignal-work <goal>` — a pass every five minutes.
|
|
121
122
|
- A `/goal` Stop hook, which blocks the turn from ending until the condition
|
|
122
123
|
holds, and is the better fit when the goal is testable from here.
|
|
123
124
|
- The plugin's interrupt hooks, which surface a priority ≥ 1 message mid-turn
|
package/package.json
CHANGED
package/scripts/dashboard.mjs
CHANGED
|
@@ -1552,7 +1552,7 @@ const PAGE = `<!doctype html>
|
|
|
1552
1552
|
// survives a laptop being shut, so reachable stays true for an agent that
|
|
1553
1553
|
// has not run since last week -- and an interface that shows that one as
|
|
1554
1554
|
// available is worse than one that shows nothing. Fifteen minutes matches
|
|
1555
|
-
// the window /agentsignal
|
|
1555
|
+
// the window /agentsignal-fleet uses, so the two cannot disagree.
|
|
1556
1556
|
const LIVE_MS = 15 * 60 * 1000;
|
|
1557
1557
|
const now = Date.now();
|
|
1558
1558
|
|
|
@@ -2565,7 +2565,7 @@ const PAGE = `<!doctype html>
|
|
|
2565
2565
|
msg.innerHTML =
|
|
2566
2566
|
'Send them this — single use' +
|
|
2567
2567
|
(result.expires_at ? ', expires ' + esc(new Date(result.expires_at).toLocaleString()) : '') +
|
|
2568
|
-
':<br><code>/agentsignal
|
|
2568
|
+
':<br><code>/agentsignal-join ' +
|
|
2569
2569
|
esc(result.code) +
|
|
2570
2570
|
'</code>';
|
|
2571
2571
|
};
|
|
@@ -3876,7 +3876,7 @@ const server = createServer(async (req, res) => {
|
|
|
3876
3876
|
|
|
3877
3877
|
// Two routes mint these and they disagree about the field name -- the
|
|
3878
3878
|
// admin one returns `secret`, this one returns `token` -- and reading the
|
|
3879
|
-
// wrong one printed "/agentsignal
|
|
3879
|
+
// wrong one printed "/agentsignal-join undefined" to somebody once. Take
|
|
3880
3880
|
// whichever is there and say so plainly if neither is.
|
|
3881
3881
|
const t = minted.token ?? {};
|
|
3882
3882
|
const code = t.token ?? t.secret ?? null;
|
package/scripts/inbox-daemon.mjs
CHANGED
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
* WHY A DAEMON AND NOT A LOOP
|
|
8
8
|
*
|
|
9
9
|
* Polling was never the problem; polling WITH A MODEL was. `/loop 5m
|
|
10
|
-
* /agentsignal
|
|
10
|
+
* /agentsignal-inbox` spends a turn on every check, so the interval is set by
|
|
11
11
|
* what you are willing to pay rather than by how fast you want to hear, and a
|
|
12
12
|
* quiet channel bills you for silence. Nothing here runs a model, so two
|
|
13
13
|
* seconds costs the same as five minutes: nothing.
|
|
@@ -1014,7 +1014,7 @@ async function pollOne(identity) {
|
|
|
1014
1014
|
* plugins/data/agentsignal-inline, and neither could see the other's file.
|
|
1015
1015
|
* Both kept polling. A lock that relocates is not a lock.
|
|
1016
1016
|
*
|
|
1017
|
-
* It also puts the pidfile back where `/agentsignal
|
|
1017
|
+
* It also puts the pidfile back where `/agentsignal-update` says it is. That
|
|
1018
1018
|
* command has always documented ~/.agentsignal/inbox-daemon.pid, and somebody
|
|
1019
1019
|
* reported it missing on their machine -- correctly, because their agent had
|
|
1020
1020
|
* joined and taken the lock with it.
|
|
@@ -197,7 +197,7 @@ as a root — a peer of yours, owned by nobody in particular, indistinguishable
|
|
|
197
197
|
from an agent somebody else started. Nothing errors. The tree is simply flat
|
|
198
198
|
and wrong.
|
|
199
199
|
|
|
200
|
-
`/agentsignal
|
|
200
|
+
`/agentsignal-spawn` does the whole sequence. By hand it is: mint the token for
|
|
201
201
|
the channel you are in, put it in the subagent's prompt with the instruction to
|
|
202
202
|
`join_channel` FIRST, then the work.
|
|
203
203
|
|
|
@@ -256,8 +256,8 @@ waits for a person.
|
|
|
256
256
|
|
|
257
257
|
## Following
|
|
258
258
|
|
|
259
|
-
- Check your inbox on a stated cadence and handle what is there. `/agentsignal
|
|
260
|
-
does one pass; `/loop 5m /agentsignal
|
|
259
|
+
- Check your inbox on a stated cadence and handle what is there. `/agentsignal-inbox`
|
|
260
|
+
does one pass; `/loop 5m /agentsignal-inbox` keeps doing it.
|
|
261
261
|
- A message carrying options is a question. `respond_to_message` answers it with
|
|
262
262
|
one of those options and carries no text of its own, so send anything else
|
|
263
263
|
separately.
|