mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-07-18 20:26:53 +00:00
3ffd622de0
Production telemetry showed 1,437 installs on the external-agent surface but only 2 on the Pulse MCP adapter. Live verification proved the pulse_mcp telemetry surface attribution is honest (adapter tools/call records surface=pulse_mcp; header-less calls record agent_api), so the gap is real - but the funnel comparison is also misleading: agent_api counts any scoped API-token REST consumer (scripts, dashboards polling /api/config/nodes or /api/ai/patrol/findings), not BYO AI agents. Recorded that interpretation constraint on PulseIntelligenceExternalAgentEvidence. The genuine product gap: the in-app connector setup (Settings -> Pulse Intelligence -> Assistant -> External agents) was invisible to sidebar search. Searching 'mcp', 'claude', 'opencode', or 'connector' returned 'No settings found' because search matched only nav labels and header descriptions. - Add search-only keywords to SettingsNavItem and match them in filteredTabGroups; the Assistant item now carries mcp / model context protocol / external agent(s) / claude / opencode / connector / pulse-mcp. - Name external agent (MCP) connectors in the Assistant header description (EN/DE/ES kept in sync), so the page header states what the page contains. - Pin the search behavior with parameterized useSettingsAccess tests plus a settingsArchitecture source proof; record the keyword channel in the frontend-primitives contract (obligation 41) and the product-copy allowance in the security-privacy i18n extension point. |
||
|---|---|---|
| .. | ||
| pulse_intelligence_evidence.go | ||
| telemetry.go | ||
| telemetry_test.go | ||