t0saki 29ba81b53e feat(plugins): identify memory plugin traffic with a User-Agent (#3532) ...

Every harness memory plugin sent OpenViking requests under Node's default
`user-agent: node`, so server-side and gateway logs could not attribute
traffic to a harness or a plugin version.

Send `openviking-memory-<harness>/<version>` from all six harnesses
(claude-code, codex, opencode, pi, cursor, trae) on both the data plane
and the MCP proxy. Versions come from each harness's own manifest, or
from OPENVIKING_INTEGRATION_VERSION for cursor/trae; an unreadable
manifest degrades to 0.0.0 rather than throwing inside a short-lived hook.

The header is purely informational — neither the open-source server nor
the commercial gateway consumes it, and no auth or identity header
changes.

2026-07-27 15:31:21 +08:00

..

mcp-proxy.mjs

feat(plugins): identify memory plugin traffic with a User-Agent (#3532)

2026-07-27 15:31:21 +08:00

mcp-proxy.test.mjs

feat(plugins): identify memory plugin traffic with a User-Agent (#3532)

2026-07-27 15:31:21 +08:00