@maind-dev/mcp-bridge 0.102.0 → 0.104.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 +33 -0
- package/build/index.js +326 -296
- package/build/meta.json +1 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -96,6 +96,7 @@ again unless you re-pair).
|
|
|
96
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
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
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) |
|
|
99
|
+
| `maind-mcp-bridge activity [on\|off\|status]` | Opt-in: Claude Code sessions report their agent activity to the work object they are bound to (see "Agent activity from Claude Code sessions") |
|
|
99
100
|
| `npx -y @maind-dev/mcp-bridge --reauth` | Drop the cached key and re-run the device flow |
|
|
100
101
|
| `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) |
|
|
101
102
|
| `npx -y @maind-dev/mcp-bridge --version` | Print the bridge version |
|
|
@@ -532,6 +533,37 @@ What `doctor` reports (`claude-plugin`), and how to clean it up:
|
|
|
532
533
|
| 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
534
|
| 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. |
|
|
534
535
|
|
|
536
|
+
## Agent activity from Claude Code sessions (since 0.104.0)
|
|
537
|
+
|
|
538
|
+
Opt-in. With `maind-mcp-bridge activity on`, a Claude Code session that is bound
|
|
539
|
+
to exactly one work object reports what its agent does to that object's activity
|
|
540
|
+
panel in MAIND — the same view a `maind run` shows:
|
|
541
|
+
|
|
542
|
+
- the todo list as the plan (step status; step text only with the text opt-in),
|
|
543
|
+
- actions as counts per category (`read`, `edit`, `run`, `test`, `search`, `git`,
|
|
544
|
+
`web`, `other`) — never paths, commands, file contents or tool output,
|
|
545
|
+
- questions to you (`AskUserQuestion`), shown as "waiting for you",
|
|
546
|
+
- the answer at the end of each turn — only when your organization stores agent
|
|
547
|
+
text (`agent_activity_text = on`); without it, the agent's words never leave
|
|
548
|
+
the machine.
|
|
549
|
+
|
|
550
|
+
**Which object.** The object of the session's branch (`branch.<name>.maindObject`,
|
|
551
|
+
set by `maind object bind`) when the session is bound to it; otherwise the
|
|
552
|
+
session's only bound object (a take binds too); otherwise nothing is reported.
|
|
553
|
+
`maind-mcp-bridge activity status` shows the switch and, per live session in the
|
|
554
|
+
current repository, the object it reports to.
|
|
555
|
+
|
|
556
|
+
**How.** The bridge reads the session's transcript
|
|
557
|
+
(`~/.claude/projects/…/<session>.jsonl`) from the moment reporting starts — no
|
|
558
|
+
history — and sends batches every few seconds over the session's own MCP
|
|
559
|
+
connection. Everything is fail-open: a slow or unreachable server never delays
|
|
560
|
+
the session. Claude Code's permission prompts are not in the transcript, so they
|
|
561
|
+
are not reported.
|
|
562
|
+
|
|
563
|
+
Switch it off with `maind-mcp-bridge activity off`, per session with
|
|
564
|
+
`MAIND_AGENT_ACTIVITY=off`. `install` asks once (default No); `--agent-activity`
|
|
565
|
+
enables it without asking.
|
|
566
|
+
|
|
535
567
|
## Where things live
|
|
536
568
|
|
|
537
569
|
| Path | Purpose |
|
|
@@ -584,6 +616,7 @@ Rarely useful outside maind's own development environments:
|
|
|
584
616
|
| `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
617
|
| `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
618
|
| `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) |
|
|
619
|
+
| `MAIND_AGENT_ACTIVITY` | unset | `on`/`off` overrides `activity on\|off` for one session (see "Agent activity from Claude Code sessions") |
|
|
587
620
|
| `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") |
|
|
588
621
|
| `XDG_CONFIG_HOME` | `~/.config` (Linux/BSD) | Parent of the `maind/` config dir |
|
|
589
622
|
|