@maind-dev/mcp-bridge 0.99.0 → 0.101.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 +195 -76
- package/build/index.js +440 -377
- package/build/meta.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -92,10 +92,12 @@ again unless you re-pair).
|
|
|
92
92
|
| Command | Effect |
|
|
93
93
|
|---|---|
|
|
94
94
|
| `npx -y @maind-dev/mcp-bridge` | Run as MCP server (default; what your IDE invokes) |
|
|
95
|
-
| `npx -y @maind-dev/mcp-bridge install` | One-shot setup: MCP configs,
|
|
96
|
-
| `maind-mcp-bridge install --
|
|
95
|
+
| `npx -y @maind-dev/mcp-bridge install` | One-shot setup: MCP configs and, per client, the channel that brings the MAIND hint and your conventions into each session (hooks, user-level rule files) — nothing in your repository |
|
|
96
|
+
| `npx -y @maind-dev/mcp-bridge install --team` | The same, plus — deliberately — the conventions block in the repository's `AGENTS.md` and the project `.mcp.json` |
|
|
97
|
+
| `maind-mcp-bridge install --hooks-only` | Only the user-level channels — adds what an existing install is missing (no pairing, no MCP configs) |
|
|
98
|
+
| `maind-mcp-bridge refresh-rules` | Refresh the user-level rule files with the conventions of a repository (`--project-root <dir>`, `--force`, `--json`; see below) |
|
|
97
99
|
| `npx -y @maind-dev/mcp-bridge --reauth` | Drop the cached key and re-run the device flow |
|
|
98
|
-
| `npx -y @maind-dev/mcp-bridge doctor` | Offline self-diagnosis with fix commands (`--json`; `--remove-phantoms [--yes]`, see below) |
|
|
100
|
+
| `npx -y @maind-dev/mcp-bridge doctor` | Offline self-diagnosis with fix commands (`--json`; `--remove-phantoms`, `--migrate-repo-blocks`, `--remove-duplicate-hooks`, `--remove-duplicate-mcp`, each `[--yes]`, see below) |
|
|
99
101
|
| `npx -y @maind-dev/mcp-bridge --version` | Print the bridge version |
|
|
100
102
|
| `npx -y @maind-dev/mcp-bridge --help` | Show usage |
|
|
101
103
|
|
|
@@ -103,7 +105,7 @@ again unless you re-pair).
|
|
|
103
105
|
|
|
104
106
|
| Client | File | Written when |
|
|
105
107
|
|---|---|---|
|
|
106
|
-
| Claude Code (project) | `<project>/.mcp.json` |
|
|
108
|
+
| Claude Code (project) | `<project>/.mcp.json` | only with `--team` (since **0.100.0**, ADR-364) |
|
|
107
109
|
| Claude Code (user) | `~/.claude.json` | always |
|
|
108
110
|
| Claude Desktop | `claude_desktop_config.json` (per-OS path) | Claude Desktop is installed, or `--client claude-desktop` |
|
|
109
111
|
| Cursor | `~/.cursor/mcp.json` | Cursor is installed, or `--client cursor` |
|
|
@@ -114,7 +116,7 @@ again unless you re-pair).
|
|
|
114
116
|
| Continue | `~/.continue/mcpServers/maind.json` — a file of its own; `config.yaml` is never touched | Continue is installed, or `--client continue` |
|
|
115
117
|
| Codex CLI | `config.toml` in Codex's home — `~/.codex/`, or `$CODEX_HOME` when set (absolute paths only); the Codex IDE extension and the ChatGPT desktop app share it | Codex is installed, or `--client codex`; `--skip-codex` leaves an installed Codex out |
|
|
116
118
|
|
|
117
|
-
Only Claude Code's
|
|
119
|
+
Only Claude Code's user file is written on every machine. A client that is not
|
|
118
120
|
installed gets no file of ours (since **0.85.0** for Cursor and Windsurf,
|
|
119
121
|
**0.83.0** for VS Code, **0.87.0** for Cline and Continue, **0.95.0** for Claude
|
|
120
122
|
Desktop and Codex). Windsurf became Devin Desktop on 2026-06-02; since
|
|
@@ -152,6 +154,36 @@ probe. `CLINE_DIR`, `CLINE_DATA_DIR`, `CLINE_MCP_SETTINGS_PATH`,
|
|
|
152
154
|
`CONTINUE_GLOBAL_DIR` and `CODEX_HOME` move the Cline, Continue and Codex files
|
|
153
155
|
the way the clients resolve them (absolute paths only).
|
|
154
156
|
|
|
157
|
+
### Nothing in your repository — the channel per client (since 0.100.0)
|
|
158
|
+
|
|
159
|
+
Until 0.99.0 `install` appended a MAIND hint block ("preamble") to `CLAUDE.md`,
|
|
160
|
+
`AGENTS.md`, `.github/copilot-instructions.md`, `.cursorrules` and
|
|
161
|
+
`.windsurfrules` in your repository, and kept a conventions block in
|
|
162
|
+
`AGENTS.md`. Since **0.100.0** (ADR-364) the default writes nothing into the
|
|
163
|
+
repository. The hint and the project conventions reach each client through a
|
|
164
|
+
channel on user level — each with its own consent (a prompt; `--full` consents;
|
|
165
|
+
non-interactive without `--full` skips with `consent-required`; `--dry-run`
|
|
166
|
+
shows the plan), appended, never overwriting, idempotent, and only for a client
|
|
167
|
+
that is installed (the same evidence as its MCP target) unless `--client`
|
|
168
|
+
names it:
|
|
169
|
+
|
|
170
|
+
| Client | Channel | Where |
|
|
171
|
+
|---|---|---|
|
|
172
|
+
| Claude Code | hooks: session briefing with the full convention set, prompt and read context (see below); no `CLAUDE.md` block | `~/.claude/settings.json` — or the Claude Code plugin `maind` (`maind@maind`): with the plugin enabled, `install` writes no hooks there and no server into `~/.claude.json` |
|
|
173
|
+
| Codex | `SessionStart` hook, its output as `additionalContext` | `config.toml` in Codex's home (`~/.codex/`, or `$CODEX_HOME`) |
|
|
174
|
+
| Devin Desktop | Claude Code's hooks (it loads `~/.claude/settings.json`) | — no own entry |
|
|
175
|
+
| Cursor | `sessionStart` hook (a race Cursor confirms can drop its context — see "The team option") | `~/.cursor/hooks.json` |
|
|
176
|
+
| GitHub Copilot (VS Code) | user instructions, `applyTo: "**"` | `~/.copilot/instructions/maind.instructions.md` |
|
|
177
|
+
| Cline | global rule (always active without frontmatter) | `<Documents>/Cline/Rules/maind.md` |
|
|
178
|
+
| Continue | global rule, `alwaysApply: true` | `~/.continue/rules/maind.md` (or `$CONTINUE_GLOBAL_DIR/rules/`) |
|
|
179
|
+
| Claude Desktop | the MCP `instructions` only | — |
|
|
180
|
+
|
|
181
|
+
`--no-hook` leaves out every hook (Claude Code's, Cursor's, Codex's),
|
|
182
|
+
`--no-rules` every rule file. `--no-preamble` is accepted for old scripts and
|
|
183
|
+
does nothing. `install --hooks-only` sets up the channels an existing install is
|
|
184
|
+
missing. Blocks an earlier install wrote into a repository stay effective until
|
|
185
|
+
you remove them — see "Migrating the repository blocks".
|
|
186
|
+
|
|
155
187
|
### Leftover configs: `doctor --remove-phantoms`
|
|
156
188
|
|
|
157
189
|
`doctor` reports a config that names maind for a client that is not installed
|
|
@@ -312,9 +344,11 @@ conversation's initial system context" (cursor.com/docs/hooks). Since
|
|
|
312
344
|
`transcript_path` in `~/.maind/cursor/deliveries.jsonl` (local only), and
|
|
313
345
|
`maind sessions scan-conventions --client cursor` checks the transcripts
|
|
314
346
|
against it. Cursor staff confirm a race in which `additional_context` can be
|
|
315
|
-
dropped, and `sessionStart` does not run again on resume —
|
|
316
|
-
|
|
317
|
-
|
|
347
|
+
dropped, and `sessionStart` does not run again on resume — for teams that
|
|
348
|
+
work mostly in Cursor, the team option below (`install --team`, the
|
|
349
|
+
conventions in the repository's `AGENTS.md`) is the reliable channel; the
|
|
350
|
+
install report and `doctor` say so. We claim nothing for Cursor until the
|
|
351
|
+
scan says `measured_*`.
|
|
318
352
|
|
|
319
353
|
## Other hosts: Cursor and Devin Local run these hooks too
|
|
320
354
|
|
|
@@ -332,8 +366,9 @@ prints what that host can take:
|
|
|
332
366
|
| Host | What it gets |
|
|
333
367
|
|---|---|
|
|
334
368
|
| Claude Code (or a host we cannot identify) | Exactly what it got before — plain text at session start, `hookSpecificOutput` JSON elsewhere |
|
|
335
|
-
| Cursor | One JSON object in Cursor's own shape, or nothing — never plain text. A refused `Write` is `permission: "deny"` with the reason for you and the agent; session-start text and context stay out (Cursor's own `sessionStart` hook — see above — and `AGENTS.md`
|
|
369
|
+
| Cursor | One JSON object in Cursor's own shape, or nothing — never plain text. A refused `Write` is `permission: "deny"` with the reason for you and the agent; session-start text and context stay out (Cursor's own `sessionStart` hook — see above — carries the briefing there, and with the team option `AGENTS.md`) |
|
|
336
370
|
| Devin Local | Claude Code's JSON where Devin documents it: `additionalContext` at `SessionStart`, `UserPromptSubmit` and `PostToolUse`, `decision: "block"` for a refusal. Nothing at `PreToolUse`, never plain text |
|
|
371
|
+
| Codex (since 0.100.0) | Runs `on-session-briefing --host=codex` from its own `config.toml`; gets `{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": …}}` — never plain text, which Codex parses as JSON when it starts with `[`. Recognised by the `--host=codex` the installer writes, else by a Codex rollout transcript (`…/sessions/YYYY/MM/DD/rollout-….jsonl`) |
|
|
337
372
|
|
|
338
373
|
Whether the context reaches the model in Devin Local is **not measured**. To
|
|
339
374
|
keep every hook silent there, set `MAIND_DEVIN_HOOK_OUTPUT=off`, or
|
|
@@ -351,71 +386,151 @@ own on that file stays as it is and is named with its replacement. `doctor`
|
|
|
351
386
|
reports an old `cat` (`hook-hosts`, a warning when Cursor is installed), and
|
|
352
387
|
the session-start line names the command while Cursor is installed.
|
|
353
388
|
|
|
354
|
-
##
|
|
355
|
-
|
|
356
|
-
|
|
357
|
-
|
|
358
|
-
|
|
359
|
-
|
|
360
|
-
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
364
|
-
|
|
365
|
-
|
|
366
|
-
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
|
|
389
|
+
## Codex: conventions at session start
|
|
390
|
+
|
|
391
|
+
Codex has hooks (learn.chatgpt.com/docs/hooks). Since **0.100.0** `install`
|
|
392
|
+
adds, where Codex is installed (or with `--client codex`):
|
|
393
|
+
|
|
394
|
+
```toml
|
|
395
|
+
[features]
|
|
396
|
+
hooks = true
|
|
397
|
+
|
|
398
|
+
[[hooks.SessionStart]]
|
|
399
|
+
[[hooks.SessionStart.hooks]]
|
|
400
|
+
type = "command"
|
|
401
|
+
command = "<bridge> on-session-briefing --host=codex"
|
|
402
|
+
timeout = 10
|
|
403
|
+
additionalContextLimit = 4000
|
|
404
|
+
```
|
|
405
|
+
|
|
406
|
+
- **What.** The same block the Claude Code session-start hook prints —
|
|
407
|
+
`[maind] Session briefing …`, project conventions first —, as
|
|
408
|
+
`hookSpecificOutput.additionalContext`. `additionalContextLimit` lifts Codex's
|
|
409
|
+
default (~2,500 tokens; above it Codex replaces the text by a file and a
|
|
410
|
+
preview) for this one handler.
|
|
411
|
+
- **Trust.** Codex runs a new hook only after you trust it: open `/hooks` in
|
|
412
|
+
Codex once. The report row says so.
|
|
413
|
+
- **Append-only.** Every other key, table and hook stays; `[features] hooks =
|
|
414
|
+
false` (or the old `codex_hooks = false`) is your "no" and is reported, never
|
|
415
|
+
flipped. The file goes through the same parse/stringify as the MCP entry —
|
|
416
|
+
keys and values stay, comments do not. A handler already there, in
|
|
417
|
+
`config.toml` or `hooks.json`, counts as wired.
|
|
418
|
+
|
|
419
|
+
## User-level rule files: Copilot, Cline, Continue
|
|
420
|
+
|
|
421
|
+
Clients without a hook channel get a file of the bridge's own on user level:
|
|
422
|
+
|
|
423
|
+
- **What.** Frontmatter where the client needs one (`applyTo: "**"` for
|
|
424
|
+
Copilot, `alwaysApply: true` for Continue), a marker line
|
|
425
|
+
`<!-- maind:rules v1 … -->` that makes the file the bridge's, the MAIND hint,
|
|
426
|
+
and the project conventions — the same text the session-start hook delivers,
|
|
427
|
+
from the same cache — under the line `Conventions for <repo>, refreshed
|
|
428
|
+
<time> (mcp-bridge <version>).` A file of that name without the marker is
|
|
429
|
+
yours and is never touched.
|
|
430
|
+
- **Which repository.** A file on user level applies in every repository, so
|
|
431
|
+
it carries the conventions of the one you work in now. The bridge refreshes a
|
|
432
|
+
client's file when a session of that client starts (git root of its working
|
|
433
|
+
directory, else its MCP `roots`), and the MAIND extension runs
|
|
434
|
+
`refresh-rules` when a workspace opens or gains focus. With two windows in two
|
|
435
|
+
repositories at the same time, the last active one wins; hook clients are
|
|
436
|
+
exact per session.
|
|
437
|
+
- **`maind-mcp-bridge refresh-rules [--project-root <dir>] [--force] [--json]`**
|
|
438
|
+
refreshes the files that exist — it never creates one — with the conventions
|
|
439
|
+
of the repository at `<dir>` (default: the current directory; its git root).
|
|
440
|
+
At most once per 12 h per repository and file, and only when the content
|
|
441
|
+
changed; a file that carries another repository's conventions is rewritten at
|
|
442
|
+
once. `--force` skips the 12 h. `MAIND_NO_RULES_REFRESH=1` makes it a no-op.
|
|
443
|
+
Exit 0 for `refreshed`, `unchanged`, `throttled`, `no_channels`,
|
|
444
|
+
`opted_out`; 2 for a usage error; 1 for a real failure (not paired, no
|
|
445
|
+
conventions for that repository). `--json` prints one object: `{"outcome":
|
|
446
|
+
…, "repo": "<owner/repo>" | null, "files": [<paths written>]}`.
|
|
447
|
+
|
|
448
|
+
## The team option: conventions in the repository's AGENTS.md
|
|
449
|
+
|
|
450
|
+
`install --team` writes into the repository, deliberately, two things: the
|
|
451
|
+
conventions block in `AGENTS.md` and the project `.mcp.json`. For teams whose
|
|
452
|
+
colleagues should get the rules with the repository, maind or not — and the
|
|
453
|
+
recommended choice for teams that work mostly in Cursor. No preamble goes into
|
|
454
|
+
`CLAUDE.md`, `.github/copilot-instructions.md`, `.cursorrules` or
|
|
455
|
+
`.windsurfrules`, not even here: `AGENTS.md` is read by every relevant client.
|
|
370
456
|
|
|
371
457
|
- **What.** A managed block between `<!-- maind:conventions v1 begin -->` and
|
|
372
|
-
`<!-- maind:conventions v1 end
|
|
373
|
-
|
|
374
|
-
|
|
375
|
-
|
|
376
|
-
|
|
377
|
-
|
|
378
|
-
|
|
379
|
-
- **
|
|
380
|
-
|
|
381
|
-
|
|
382
|
-
|
|
383
|
-
|
|
384
|
-
|
|
385
|
-
|
|
386
|
-
|
|
387
|
-
|
|
388
|
-
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
|
|
392
|
-
|
|
393
|
-
|
|
394
|
-
|
|
395
|
-
|
|
396
|
-
|
|
397
|
-
|
|
398
|
-
|
|
399
|
-
|
|
400
|
-
|
|
401
|
-
|
|
402
|
-
|
|
403
|
-
|
|
404
|
-
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
|
|
408
|
-
|
|
409
|
-
|
|
410
|
-
|
|
411
|
-
|
|
412
|
-
|
|
413
|
-
|
|
414
|
-
|
|
415
|
-
|
|
416
|
-
-
|
|
417
|
-
|
|
418
|
-
|
|
458
|
+
`<!-- maind:conventions v1 end -->`; its second line,
|
|
459
|
+
`<!-- maind:conventions scope=team … -->`, records the choice — it travels
|
|
460
|
+
with every clone. Then a lead line (`Project conventions — … updated <date> by
|
|
461
|
+
mcp-bridge <version> …`) and the conventions text, capped at 6 000 characters
|
|
462
|
+
at a line boundary (`… (N more via get_conventions)`). Without `AGENTS.md`
|
|
463
|
+
the file is created; an existing block (a team one, or one an earlier default
|
|
464
|
+
install wrote) is replaced in place; otherwise the block goes to the end.
|
|
465
|
+
- **Kept current.** Every bridge session start in that repository refreshes the
|
|
466
|
+
block — any client, after the MCP handshake, off the hot path, at most once
|
|
467
|
+
per 12 hours, only when the conventions changed (a committed `AGENTS.md` does
|
|
468
|
+
not churn for a date). Only a block with the team line is refreshed; the
|
|
469
|
+
bridge never inserts one at runtime. Opt-out: `MAIND_NO_AGENTS_MD_REFRESH=1`.
|
|
470
|
+
- **Only inside the repository.** The closest `AGENTS.md` with a team block
|
|
471
|
+
between the working directory and the git root — never above it; when the
|
|
472
|
+
working directory is no repository, the client's MCP `roots` are asked.
|
|
473
|
+
|
|
474
|
+
## Migrating the repository blocks: `doctor --migrate-repo-blocks`
|
|
475
|
+
|
|
476
|
+
`doctor` finds the blocks an earlier install wrote into the repository of the
|
|
477
|
+
working directory — by their markers: the `## maind MCP integration` header of
|
|
478
|
+
a block the installer (or the dashboard snippet) shipped, and the
|
|
479
|
+
`<!-- maind:conventions v1 … -->` pair — and reports them (`repo-blocks`). The
|
|
480
|
+
SessionStart hook names the migration once per repository.
|
|
481
|
+
|
|
482
|
+
- `doctor --migrate-repo-blocks` lists the blocks and the user-level channels
|
|
483
|
+
that carry the same content, and changes nothing.
|
|
484
|
+
- `doctor --migrate-repo-blocks --yes` sets those channels up first (Claude
|
|
485
|
+
Code's reminder and briefing hooks unless the plugin carries them, Cursor's
|
|
486
|
+
and Codex's hooks, the rule files — for the clients installed here) and stops
|
|
487
|
+
without removing anything if one fails; then it removes exactly the listed
|
|
488
|
+
blocks. Only lines between maind markers go (and the blank line the installer
|
|
489
|
+
put before them); every other byte stays, with its own line endings. A file
|
|
490
|
+
that holds nothing else is deleted. A section that is not a block the
|
|
491
|
+
installer wrote — edited by hand — is listed for removal by hand and never
|
|
492
|
+
touched. A team block stays.
|
|
493
|
+
|
|
494
|
+
## Claude Code plugin `maind`
|
|
495
|
+
|
|
496
|
+
The plugin `maind@maind` brings the bridge's Claude Code hooks and its MCP
|
|
497
|
+
server (`plugin:maind:maind`); both run this bridge through the plugin's
|
|
498
|
+
launcher. The bridge counts it as enabled when:
|
|
499
|
+
|
|
500
|
+
- `~/.claude/settings.json` (or `$CLAUDE_CONFIG_DIR/settings.json`) enables it, or
|
|
501
|
+
- Claude Code's managed settings do (`managed-settings.json` and
|
|
502
|
+
`managed-settings.d/` in `/Library/Application Support/ClaudeCode/`,
|
|
503
|
+
`/etc/claude-code/`, `C:\Program Files\ClaudeCode\`), or
|
|
504
|
+
- the process was started by the plugin — its launcher sets
|
|
505
|
+
`MAIND_CLAUDE_PLUGIN=<plugin version>`. This also covers a plugin loaded
|
|
506
|
+
with `--plugin-dir`, which no settings file names.
|
|
507
|
+
|
|
508
|
+
With the plugin enabled:
|
|
509
|
+
|
|
510
|
+
- `install` and `install --hooks-only` write no hooks into
|
|
511
|
+
`~/.claude/settings.json` (row: `Claude Code hooks: provided by the maind
|
|
512
|
+
plugin`).
|
|
513
|
+
- `install` writes no `maind` server into `~/.claude.json` either (row:
|
|
514
|
+
`Claude Code MCP server: provided by the maind plugin`). A second server
|
|
515
|
+
would list every maind tool twice: Claude Code merges a plugin's server with
|
|
516
|
+
a configured one only when both run the identical command.
|
|
517
|
+
- `doctor`, the session-start setup line and `status` count the plugin's
|
|
518
|
+
hooks as wired. No more "setup gap" in a session whose hooks come from the
|
|
519
|
+
plugin.
|
|
520
|
+
- `guard-inject` (not part of the plugin) stands down for the plugin's
|
|
521
|
+
briefing. The exception is `on-session-briefing` declined at install: the
|
|
522
|
+
plugin keeps that hook off too, and the guard delivers.
|
|
523
|
+
|
|
524
|
+
The bridge never makes a hook it wired into `settings.json` stand down for the
|
|
525
|
+
plugin. The plugin's launcher already yields when a settings file wires the
|
|
526
|
+
same subcommand; if both yielded, nothing would run.
|
|
527
|
+
|
|
528
|
+
What `doctor` reports (`claude-plugin`), and how to clean it up:
|
|
529
|
+
|
|
530
|
+
| Finding | Level | Fix |
|
|
531
|
+
|---|---|---|
|
|
532
|
+
| A `maind` server still in `~/.claude.json` | warning | `doctor --remove-duplicate-mcp [--yes]` removes exactly that entry; the rest of the file stays byte for byte. Run it with Claude Code closed: Claude Code rewrites the file while it runs. |
|
|
533
|
+
| The bridge's own hooks still in `settings.json` | note | `doctor --remove-duplicate-hooks [--yes]` removes exactly those entries, so the plugin's copies, which update with it, take over. Nothing runs twice in the meantime. The guard pack and your own hooks stay. |
|
|
419
534
|
|
|
420
535
|
## Where things live
|
|
421
536
|
|
|
@@ -426,8 +541,10 @@ either.
|
|
|
426
541
|
| `%APPDATA%\maind\device-id` (Windows) | Same, on Windows |
|
|
427
542
|
| `device-id`-sibling file `api-key` | API key returned by approve flow (mode 0600) |
|
|
428
543
|
| `~/.maind/state.json` | Hook subcommand state: tracked sessions, queued Tier-3 metrics, synced thresholds (mode 0600) |
|
|
429
|
-
| `~/.maind/guard/agents-md-refresh.json` | When
|
|
430
|
-
| `~/.maind/guard/
|
|
544
|
+
| `~/.maind/guard/agents-md-refresh.json` | When a team block in `AGENTS.md` was last checked, per file (path hashed; mode 0600) |
|
|
545
|
+
| `~/.maind/guard/rules-refresh.json` | When each user-level rule file was last checked, for which repository, with which content (all hashed; mode 0600) |
|
|
546
|
+
| `~/.maind/guard/repo-blocks-notice.json` | Repositories the session-start line already told about their old maind blocks (hashed; mode 0600) |
|
|
547
|
+
| `~/.maind/guard/briefing-cache.json` | The last session briefing + conventions, for the session-start hooks, the rule files and the team block (12 h; mode 0600) |
|
|
431
548
|
| `~/.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 |
|
|
432
549
|
| `~/.maind/cursor/deliveries.jsonl` | What the Cursor sessionStart hook delivered: conversation id, transcript path, size (local, pruned; mode 0600) |
|
|
433
550
|
|
|
@@ -463,8 +580,10 @@ Rarely useful outside maind's own development environments:
|
|
|
463
580
|
| `MAIND_CLIENT_FAMILY` | unset | Forwards `X-Maind-Client-Family` (`claude-code`, `codex`, `copilot`, `cursor`, `windsurf`, `cline`, `continue`, …) so telemetry tracks the real upstream agent instead of generic `mcp-bridge` |
|
|
464
581
|
| `MAIND_CLIENT_VERSION` | unset | Forwards optional `X-Maind-Client-Version` marker (max 64 chars) |
|
|
465
582
|
| `MAIND_FUNCTIONS_ORIGIN` | maind's Supabase Edge Functions URL | Device-flow base URL |
|
|
466
|
-
| `MAIND_NO_AGENTS_MD_REFRESH` | unset | Set to `1` to stop the bridge from refreshing the conventions block in `AGENTS.md`
|
|
467
|
-
| `
|
|
583
|
+
| `MAIND_NO_AGENTS_MD_REFRESH` | unset | Set to `1` to stop the bridge from refreshing the team conventions block in `AGENTS.md` (see "The team option") |
|
|
584
|
+
| `MAIND_NO_RULES_REFRESH` | unset | Set to `1` to stop every refresh of the user-level rule files — at session start and `refresh-rules` |
|
|
585
|
+
| `MAIND_CLAUDE_PLUGIN` | unset | Set by the Claude Code plugin's launcher to the plugin's version for every bridge it starts; the bridge then counts its Claude Code hooks as the plugin's (see "Claude Code plugin `maind`"). Not for setting by hand |
|
|
586
|
+
| `MAIND_DEBUG` | unset | Set to `1` for one diagnostic stderr line on the otherwise silent team-block skip (no `AGENTS.md` with a team block inside the repository) |
|
|
468
587
|
| `MAIND_DEVIN_HOOK_OUTPUT` | `on` | `off` keeps every hook silent when Devin Local runs it (same as `"devin_hook_output": false` in `config.json`; see "Other hosts") |
|
|
469
588
|
| `XDG_CONFIG_HOME` | `~/.config` (Linux/BSD) | Parent of the `maind/` config dir |
|
|
470
589
|
|