@gethmy/mcp 3.3.0 → 3.4.1
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 +39 -0
- package/dist/cli.js +1012 -178
- package/dist/index.js +630 -63
- package/dist/run-hook-cli.js +742 -0
- package/package.json +2 -2
- package/src/api-client.ts +26 -1
- package/src/auto-session.ts +33 -0
- package/src/cli.ts +104 -0
- package/src/hook-install.ts +388 -0
- package/src/plan-task-link.ts +3 -1
- package/src/run-event-forwarder.ts +363 -0
- package/src/run-hook-cli.ts +55 -0
- package/src/run-hook-main.ts +159 -0
- package/src/run-hook.ts +203 -0
- package/src/run-redaction.ts +461 -0
- package/src/run-state.ts +679 -0
- package/src/server.ts +85 -5
package/README.md
CHANGED
|
@@ -122,8 +122,47 @@ npx @gethmy/mcp reset # Clear all configuration
|
|
|
122
122
|
|
|
123
123
|
# Server (called by agents automatically)
|
|
124
124
|
npx @gethmy/mcp serve # Start MCP server
|
|
125
|
+
|
|
126
|
+
# Run timeline hook (opt-in) — see below
|
|
127
|
+
npx @gethmy/mcp hook install # Stream this session's tool calls to the card
|
|
128
|
+
npx @gethmy/mcp hook status # Is it installed? Which sessions are live?
|
|
129
|
+
npx @gethmy/mcp hook uninstall # Remove it
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
### Run Timeline Hook
|
|
133
|
+
|
|
134
|
+
By default a card's run timeline shows only what the MCP tools report: the
|
|
135
|
+
session starting, each progress checkpoint, the session ending. Your editor's
|
|
136
|
+
own `Read`, `Edit`, `Bash` and `Grep` calls never reach the MCP server, so they
|
|
137
|
+
cannot appear there.
|
|
138
|
+
|
|
139
|
+
`hook install` closes that gap. It adds one `PostToolUse` entry to
|
|
140
|
+
`~/.claude/settings.json`, and from then on the tool calls of a session that
|
|
141
|
+
holds a card stream to that card's timeline with their input and output, live —
|
|
142
|
+
the same view a Harmony agent daemon run gets, without you reporting anything.
|
|
143
|
+
|
|
144
|
+
```bash
|
|
145
|
+
npx @gethmy/mcp hook install
|
|
125
146
|
```
|
|
126
147
|
|
|
148
|
+
Four things worth knowing:
|
|
149
|
+
|
|
150
|
+
- **It writes only the user layer.** `~/.claude/settings.json`, never a
|
|
151
|
+
project's `.claude/settings.json`. A project-layer `hooks` key would break
|
|
152
|
+
contained agent runs in that repo, and the user layer is also what keeps a
|
|
153
|
+
daemon run from reporting its stream twice.
|
|
154
|
+
- **Re-run it after upgrading.** The entry pins the exact install that wrote
|
|
155
|
+
it, and an upgrade or a cleared `npx`/`bunx` cache moves that path. The
|
|
156
|
+
command guards its own paths, so nothing breaks in the meantime — the hook
|
|
157
|
+
just goes quiet, and `hook status` says so.
|
|
158
|
+
- **Tool inputs and outputs are redacted before they leave your machine.**
|
|
159
|
+
Credential paths, tokens, and the usual secret-shaped values are withheld;
|
|
160
|
+
large payloads are truncated. The full rule is in
|
|
161
|
+
[`docs/agent-run-events.md`](https://github.com/Way/getharmony/blob/main/docs/agent-run-events.md).
|
|
162
|
+
- **It is off unless you install it, and `HARMONY_DISABLE_RUN_HOOK=1` turns the
|
|
163
|
+
stream off without uninstalling** — for when a team decides tool inputs do
|
|
164
|
+
not belong on a shared board.
|
|
165
|
+
|
|
127
166
|
### Setup Options
|
|
128
167
|
|
|
129
168
|
| Flag | Description |
|