@maind-dev/mcp-bridge 0.92.0 → 0.93.0
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 +37 -0
- package/build/index.js +242 -231
- package/build/meta.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -243,6 +243,42 @@ path and a 2,000-character preview.
|
|
|
243
243
|
(`declined_hooks` in the bridge config) and not nagged about;
|
|
244
244
|
`install --hooks-only` asks again.
|
|
245
245
|
|
|
246
|
+
## Cursor: conventions at session start
|
|
247
|
+
|
|
248
|
+
Cursor documents hooks in `~/.cursor/hooks.json`, and its `sessionStart` hook
|
|
249
|
+
may return `additional_context` — "Additional context to add to the
|
|
250
|
+
conversation's initial system context" (cursor.com/docs/hooks). Since
|
|
251
|
+
**0.93.0**:
|
|
252
|
+
|
|
253
|
+
- **What.** `on-cursor-session-start` returns the same block the Claude Code
|
|
254
|
+
session-start delivery prints — project conventions first, then lessons,
|
|
255
|
+
skills and memory titles, under a 9,000-byte budget — as
|
|
256
|
+
`{"additional_context": …}`. Its stdout is always one JSON object (`{}` when
|
|
257
|
+
there is nothing to say), because Cursor parses it. The repository comes from
|
|
258
|
+
`CURSOR_PROJECT_DIR` or the payload's `workspace_roots` (user hooks run with
|
|
259
|
+
cwd `~/.cursor/`).
|
|
260
|
+
- **Where.** `install` appends one entry under `hooks.sessionStart` in
|
|
261
|
+
`~/.cursor/hooks.json` (creating the file with `version: 1` if needed): own
|
|
262
|
+
consent, append-only — foreign hooks, events and keys are left as they are,
|
|
263
|
+
and a file in another shape is reported, never rewritten —, idempotent,
|
|
264
|
+
`--dry-run` aware.
|
|
265
|
+
- **Only where Cursor is installed** — the same evidence the Cursor MCP target
|
|
266
|
+
uses (`cursorInstalled`, since 0.87.0): Cursor's app-data directory holding
|
|
267
|
+
more than `User`, or a `~/.cursor` holding anything besides the files the
|
|
268
|
+
bridge writes there (`mcp.json`, `hooks.json`). A `~/.cursor/mcp.json` alone
|
|
269
|
+
does not count — older bridges created it on machines without Cursor.
|
|
270
|
+
`--client cursor` overrides the probe.
|
|
271
|
+
- **Existing installs.** `install --hooks-only` offers the Cursor hook too,
|
|
272
|
+
where Cursor is installed — no full install needed. Cursor reloads
|
|
273
|
+
`~/.cursor/hooks.json` by itself.
|
|
274
|
+
- **Measured, not assumed.** Each delivery is noted with its
|
|
275
|
+
`transcript_path` in `~/.maind/cursor/deliveries.jsonl` (local only), and
|
|
276
|
+
`maind sessions scan-conventions --client cursor` checks the transcripts
|
|
277
|
+
against it. Cursor staff confirm a race in which `additional_context` can be
|
|
278
|
+
dropped, and `sessionStart` does not run again on resume — the `AGENTS.md`
|
|
279
|
+
block below is the reliable channel in Cursor. We claim nothing for Cursor
|
|
280
|
+
until the scan says `measured_*`.
|
|
281
|
+
|
|
246
282
|
## AGENTS.md readers: conventions via AGENTS.md
|
|
247
283
|
|
|
248
284
|
Measured on 2026-09-30 over 76 Codex rollouts: the MCP `instructions` never
|
|
@@ -321,6 +357,7 @@ either.
|
|
|
321
357
|
| `~/.maind/guard/agents-md-refresh.json` | When the `AGENTS.md` conventions block was last checked, per project (path hashed; mode 0600) |
|
|
322
358
|
| `~/.maind/guard/briefing-cache.json` | The last session briefing + conventions, for the session-start hook and the `AGENTS.md` block (12 h; mode 0600) |
|
|
323
359
|
| `~/.maind/context/<session>/` | Once-per-session markers of the context hooks: one empty file per delivered item, named by a hash; swept after 7 days |
|
|
360
|
+
| `~/.maind/cursor/deliveries.jsonl` | What the Cursor sessionStart hook delivered: conversation id, transcript path, size (local, pruned; mode 0600) |
|
|
324
361
|
|
|
325
362
|
To rebind the bridge to a different account: delete the directory above (or run
|
|
326
363
|
`--reauth`) and restart the bridge.
|