Files
OpenViking/examples/trae-memory-hooks
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
..

OpenViking Memory Hooks for TRAE

This package provides dedicated TRAE and TRAE CN lifecycle adapters. It does not reuse Claude Code transcript parsing: TRAE capture reads prompt, text_content, and last_assistant_message from the Stop event and stores sessions with tr- or trcn- prefixes.

Its PreToolUse guard prevents viking:// virtual paths from being passed to local file or shell tools and points the Agent back to OpenViking MCP tools.

Use the shared installer:

bash examples/memory-plugin-shared/install.sh --harness trae,trae-cn

See the TRAE integration guide.