@maind-dev/mcp-bridge 0.106.0 → 0.108.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 CHANGED
@@ -241,6 +241,22 @@ false}` in the bridge config switches it off. Without an answer it stays off —
241
241
  0.90.0–0.97.0 kept the file without asking, and declining at the prompt removes
242
242
  it.
243
243
 
244
+ **Codex session analytics (since 0.108.0, opt-in, asked by `install` and
245
+ `install --hooks-only` where Codex's Stop hook is wired).** With your consent
246
+ the Stop hook in Codex also reads the session's rollout
247
+ (`<Codex home>/sessions/…/rollout-….jsonl`) and sends what it sends for a
248
+ Claude Code session: turn and tool-call counts, token usage per model, which
249
+ maind tools were called, and the cost slices per work object — the edited
250
+ paths are matched against the attribution context on this machine and never
251
+ leave it. The row carries `client: codex` and no behaviour signals (Codex
252
+ writes no corrections, interrupts or denials, so the server records them as
253
+ not measured). Its connection verdict is `connected` only on proof — a maind
254
+ call in the rollout, or a fresh presence snapshot found by process tree or
255
+ naming this session — and otherwise `unknown`, never `not_connected`. The
256
+ server stores it only with your Tier-3 consent. Without an answer it stays off,
257
+ and Codex sessions reach MAIND through `maind sessions backfill` as before;
258
+ `{"codex_session_analytics": false}` in the bridge config switches it off.
259
+
244
260
  ### Context at the moment (since 0.89.0)
245
261
 
246
262
  Two hooks deliver context when it matters instead of only at session start
@@ -474,7 +490,7 @@ row, and `doctor` lists it:
474
490
  | `on-prompt-context` | yes | VS Code yes; the Copilot CLI documents command-hook output on a prompt as dropped |
475
491
  | `on-file-write`, `on-file-edit`, `on-repo-health`, `on-write-health` | edits through `apply_patch`; a file a shell command writes passes no file hook | yes |
476
492
  | `on-tool-use` | counts calls; the token advisory reads Claude Code transcripts only | the same |
477
- | `on-session-end` | closes the turn's counters, sends the Tier-3 metrics; analytics and cost slices come from `maind sessions backfill`, not from the hook | closes the counters, sends the metrics; Copilot's transcripts are not analysed |
493
+ | `on-session-end` | closes the turn's counters, sends the Tier-3 metrics; since 0.108.0 also the session analytics and cost slices from the rollout — only with the separate `codex_session_analytics` answer (see above), and without behaviour signals, which Codex does not write | closes the counters, sends the metrics; Copilot's transcripts are not analysed |
478
494
  | The guard pack | stands down outside Claude Code | the same |
479
495
 
480
496
  `doctor --remove-phantoms` takes out of `config.toml` exactly what `install`