@volcengine/tls-observer-trae-install

Installs @volcengine/tls-observer-trae locally and writes the TLS env file used by the Trae hook runtime.

npm exec -y --package=@volcengine/tls-observer-trae-install -- tls-observer-trae-install

For local development:

TRAE_TLS_PLUGIN_SOURCE="$PWD/packages/trae" \
node packages/trae-install/bin/tls-observer-trae-install.mjs --force --skip-tls-config

API Key mode requires an existing trace topic ID:

npm exec -y --package=@volcengine/tls-observer-trae-install -- tls-observer-trae-install \
  --trace-topic-id <trace-topic-id> \
  --api-key <api-key>

AK/SK mode can prepare the TLS Project and LogApp automatically, then write the discovered trace topic ID into the generated env file:

npm exec -y --package=@volcengine/tls-observer-trae-install -- tls-observer-trae-install \
  --ak <ak> \
  --sk <sk> \
  --project-name trae_observability \
  --app-name trae-observability

The installer writes:

• runtime package: ~/.trae-cn/plugins/tls-observer-trae
• env file: ~/.trae-cn/tls-observer-trae.env
• data root: ~/.trae-cn/plugins/data/tls-observer-trae
• hook config reference: ~/.trae-cn/hooks.json

Trae hook/plugin config locations differ across builds, so the hook reference file is intentionally explicit. It uses Trae's version: 1 hook format and registers UserPromptSubmit, PreToolUse, PostToolUse, and Stop; wire the generated config into the confirmed Trae hook config path.

The runtime does not require ContextFS credentials. It relies on Trae hook payloads from UserPromptSubmit, PreToolUse, PostToolUse, and Stop.