@agentsignalnet/claude-plugin 0.2.63 → 0.2.65

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.63",
4
+ "version": "0.2.65",
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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agentsignalnet/claude-plugin",
3
- "version": "0.2.63",
3
+ "version": "0.2.65",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -165,6 +165,14 @@ function isPage(pathname) {
165
165
  * predates this page. Keeping the wording inside that line is what makes this
166
166
  * an explanation rather than a weakening of the front door.
167
167
  *
168
+ * IT ASSUMES NO TERMINAL. The first version said "look in the terminal it was
169
+ * started from", which describes the rarer case: this is usually started by an
170
+ * assistant running `/agentsignal:chat` in the background, where the line is
171
+ * printed into a tool result nobody is watching and there is no terminal of
172
+ * yours to look in. Somebody hit this page and found its one instruction was a
173
+ * dead end -- technically true, useless in the case it mostly meets. So the
174
+ * assistant route is named first and the terminal second.
175
+ *
168
176
  * Styled to match the light theme rather than left as browser default, since
169
177
  * an unstyled wall of text reads as a crash page and the point is to look like
170
178
  * a considered answer.
@@ -184,11 +192,13 @@ function unlockPage() {
184
192
  '</style></head><body><main>',
185
193
  '<h1>This dashboard needs its link</h1>',
186
194
  '<p>It is running. It is refusing because this browser has not been given the ',
187
- 'one-run link, which is printed by the command that started it and only has to ',
188
- 'be opened once — after that this plain address works.</p>',
189
- '<p>Look in the terminal it was started from, for the line beginning ',
190
- '<code>Watching</code>. To print a fresh link, stop it and start it again; a new ',
191
- 'one is minted per run, so the old link is already dead.</p>',
195
+ 'one-run link, which is printed once by whatever started it and only has to be ',
196
+ 'opened once — after that this plain address works.</p>',
197
+ '<p>If an assistant started it for you, ask it for the link: the line was ',
198
+ 'printed where it can see it and you cannot. If you started it yourself, look ',
199
+ 'in that terminal for the line beginning <code>Watching</code>.</p>',
200
+ '<p>Either way, stopping it and starting it again prints a fresh link. A new ',
201
+ 'one is minted per run, so any older link is already dead.</p>',
192
202
  '</main></body></html>',
193
203
  ].join('');
194
204
  }
@@ -3555,6 +3565,36 @@ async function nameChannels() {
3555
3565
  );
3556
3566
  }
3557
3567
 
3568
+ /**
3569
+ * A PORT ALREADY IN USE IS ALMOST ALWAYS THIS SAME PROGRAM.
3570
+ *
3571
+ * Without a handler, node throws the raw listen error: an "Unhandled 'error'
3572
+ * event" and a stack through `node:net`, which says nothing about what to do
3573
+ * and buries the one useful word, the port. Worse, the usual cause is that a
3574
+ * dashboard is ALREADY RUNNING and working -- so the reader is looking at a
3575
+ * crash while the thing they wanted is up, needing only the link the running
3576
+ * one printed. That is the same shape as the 404 this page-and-note work has
3577
+ * been about: a healthy system presenting as a broken one.
3578
+ *
3579
+ * Nothing is retried and no other port is chosen. Silently landing on 8900
3580
+ * would print a link nobody expects and leave two dashboards running, which is
3581
+ * how you end up reading a stale one and wondering why it never updates.
3582
+ */
3583
+ server.on('error', (error) => {
3584
+ if (error.code === 'EADDRINUSE') {
3585
+ console.error(`Port ${port} is already in use, so this did not start.`);
3586
+ console.error('That is usually a dashboard already running — find the link it');
3587
+ console.error('printed when it started, or stop it and start this again.');
3588
+ console.error(`To run a second one alongside it, set PORT: PORT=${port + 1} …`);
3589
+ } else if (error.code === 'EACCES') {
3590
+ console.error(`Not allowed to listen on port ${port}. Ports below 1024 need root;`);
3591
+ console.error('pick a higher one with PORT.');
3592
+ } else {
3593
+ console.error(`Could not listen on port ${port}: ${error.message}`);
3594
+ }
3595
+ process.exit(1);
3596
+ });
3597
+
3558
3598
  server.listen(port, '127.0.0.1', () => {
3559
3599
  // The port the OS actually gave us, not the one asked for. They differ
3560
3600
  // whenever PORT is 0 -- which is how anything automated starts a server