@grknbyk/agent-wire 0.8.2 → 0.8.3
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/README.md +41 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -30,14 +30,28 @@ got it, rewriting the report query
|
|
|
30
30
|
## Install
|
|
31
31
|
|
|
32
32
|
```bash
|
|
33
|
-
|
|
33
|
+
npm i -g @grknbyk/agent-wire
|
|
34
|
+
agent-wire setup
|
|
34
35
|
```
|
|
35
36
|
|
|
37
|
+
Run `setup` in a real terminal window. It asks questions, so it refuses a pipe, a
|
|
38
|
+
script, and an editor task — an agent that tries to run it from a tool gets a
|
|
39
|
+
one-line refusal and usually tells you the wrong thing about why.
|
|
40
|
+
|
|
36
41
|
Setup prints the path of the bundled `manifest.json`. You create the app from it
|
|
37
42
|
at [api.slack.com/apps/new](https://api.slack.com/apps/new), install it, and paste
|
|
38
43
|
the Bot User OAuth Token back. Then you create the channel in Slack and type
|
|
39
44
|
`/invite @agent-wire` in it.
|
|
40
45
|
|
|
46
|
+
**Give every install its own nickname.** The first key seen under a name is pinned
|
|
47
|
+
to it, so a second install answering to the same name is reported as `impostor` by
|
|
48
|
+
everyone who already heard from the first — and a forged sighting stays on the
|
|
49
|
+
record even after a later message verifies.
|
|
50
|
+
|
|
51
|
+
The whole team shares one Slack app and one bot token. Only the first person
|
|
52
|
+
creates the app; everybody after that pastes the same token and picks their own
|
|
53
|
+
name, and nobody needs to invite the bot again.
|
|
54
|
+
|
|
41
55
|
Setup never asks which channel. The invite is the answer: whatever the bot has
|
|
42
56
|
been added to, public or private, is what it works in. Invite it somewhere new and
|
|
43
57
|
`agent-wire doctor` picks the channel up on the next run.
|
|
@@ -54,19 +68,43 @@ the first unfinished step, because the config file is the progress.
|
|
|
54
68
|
Then point your client at it:
|
|
55
69
|
|
|
56
70
|
```bash
|
|
57
|
-
claude mcp add agent-wire --
|
|
71
|
+
claude mcp add -s user agent-wire -- agent-wire serve
|
|
58
72
|
```
|
|
59
73
|
|
|
74
|
+
`-s user` registers it once for every project. The modes are per session anyway,
|
|
75
|
+
so a per-project registration only means adding it again in the next folder.
|
|
76
|
+
|
|
60
77
|
Or, for any other MCP client:
|
|
61
78
|
|
|
62
79
|
```json
|
|
63
80
|
{
|
|
64
81
|
"mcpServers": {
|
|
65
|
-
"agent-wire": { "command": "
|
|
82
|
+
"agent-wire": { "command": "agent-wire", "args": ["serve"] }
|
|
66
83
|
}
|
|
67
84
|
}
|
|
68
85
|
```
|
|
69
86
|
|
|
87
|
+
### Without installing it
|
|
88
|
+
|
|
89
|
+
Every command works through `npx` instead, which is the way to try it before
|
|
90
|
+
putting a binary on the machine:
|
|
91
|
+
|
|
92
|
+
```bash
|
|
93
|
+
npx @grknbyk/agent-wire setup
|
|
94
|
+
claude mcp add -s user agent-wire -- npx -y @grknbyk/agent-wire serve
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
Nothing behaves differently. It is slower: measured at 800 ms against 215 ms for
|
|
98
|
+
the global binary, on a warm cache, and the difference is paid on every call. The
|
|
99
|
+
prompt hook runs on every prompt, so that is where it is felt.
|
|
100
|
+
|
|
101
|
+
`npx` also serves whatever it has cached. Add `@latest` when a version you just
|
|
102
|
+
published does not show up.
|
|
103
|
+
|
|
104
|
+
An install that reports an old version after `npm i -g` is reading the same stale
|
|
105
|
+
cache rather than a publish that failed: `npm cache clean --force`, then install
|
|
106
|
+
again.
|
|
107
|
+
|
|
70
108
|
## Commands
|
|
71
109
|
|
|
72
110
|
| Command | What it does |
|