Repository navigation
Releases: GuanceCloud/codex-otel-plugin
Releases · GuanceCloud/codex-otel-plugin
Release list
v0.1.19
Changelog
- Enabled
gzipcompression by default for OTLP HTTP/protobuf Trace and Metrics uploads. - Added
compression: "none"as a compatibility fallback for receivers that do not accept compressed request bodies. - Logged both raw and compressed request sizes in hook upload results to simplify
413 Request Entity Too Largediagnosis. - Added helper-backed local uninstall cleanup and shipped
uninstall.shin release assets.
v0.1.18
Changelog
- Aligned
install.shCodex binary discovery with theagent-meterlookup order on macOS and Linux. - Preferred explicit and app-bundled Codex paths before PATH scanning, while keeping legacy fallbacks for compatibility.
- Logged the resolved Codex CLI path and whether the installer had to fall back to a legacy discovery path.
v0.1.17
Changelog
- Downgraded installer failures when the Codex CLI command exists but the Codex runtime itself cannot start.
- Improved installer next-step guidance for broken Codex CLI, already running Codex sessions, and post-install first launch.
- Added a shell-installer hint for root-owned Codex homes such as
/var/root/.codex.
v0.1.16
Changelog
- Fixed macOS
install.shfailure caused by iterating an emptyHEADERSarray underset -u. - Promoted the Go-prebuilt Codex hook packaging and installer flow to the stable
v0.1.16release.
v0.1.15-rc2
Changelog
- Fixed macOS
install.shfailure caused by iterating an emptyHEADERSarray underset -u. - Preserved the Go-prebuilt release packaging and installer flow introduced in
v0.1.15-rc.
v0.1.15-rc
Changelog
- Reimplemented the Codex Stop hook, rollout parser, span and metric collectors, OTLP codecs, ingest server, installer helper, and tests in Go.
- Removed the Node.js runtime requirement and all runtime npm dependencies.
- Added prebuilt Go binaries for Linux, macOS, and Windows on amd64 and arm64.
- Preserved terminal-turn deduplication, non-blocking telemetry failures, Codex hook trust, OTLP Trace and Metrics protobuf transport, and existing trace and metric semantics.
- Added tag-driven GitHub Actions that run Go quality checks, build release assets from the tagged commit, validate versions and checksums, and publish the GitHub Release.
- Fixed discovery of prebuilt hooks under platform-specific
bin/<os>-<arch>directories. - Published generic and versioned tar/ZIP archives, per-archive checksums, local installers, remote installers, and a complete
SHA256SUMS.
v0.1.15
Changelog
- Fix macOS installer entrypoint resolution when scripts run from temporary directories or symlinked paths under /var/folders and /private/var/folders
- Keep installer config writes, hook trust, and runtime CLI entrypoint detection aligned under the same realpath-based path resolution
- Publish the finalized macOS installer fix as v0.1.15
v0.1.14-rc
Changelog
- Fix the macOS installer config entrypoint so installs from temporary release directories under /var/folders and /private/var/folders update the target gtrace.json reliably
- Add regression coverage for installer config writes when the script path is reached through a symlinked or normalized temporary directory
- Keep the v0.1.14 installer behavior unchanged on Linux and Windows while applying the macOS-specific path resolution fix
v0.1.14
Changelog
- Move
gtrace.jsonwrite-back to aftercodex plugin addso macOS installs keep the latestX-Token,agent_id, andagent_name - Keep Linux and Windows installer behavior aligned with the same final config write order
- Add a regression test for installer-managed auth and agent tag overwrite behavior
v0.1.13
Changelog
- Add native Windows installation support with local and remote PowerShell installers
- Publish both tar.gz and ZIP plugin archives with checksums
- Make
gtrace.json.enabledstop hook processing before stdin/transcript parsing and OTLP construction - Preserve the existing enabled state during upgrades unless explicitly changed with installer switches
- Fix Windows ESM entry-point, execution-policy, Codex CLI discovery, and filesystem path handling
- Install the Stop hook through the supported global
~/.codex/hooks.jsonmechanism while preserving unrelated hooks - Remove the duplicate legacy plugin hook so each completed turn is handled once
- Automatically trust the exact GTrace Stop hook on Windows and Linux through Codex
hooks/listandconfig/batchWrite
Automatic hook trust
The Windows and Linux installers ask the local Codex app-server for the discovered GTrace user hook key and current hash, then persist that hash in hooks.state. This makes fresh installs and reinstalls work without a separate hook-review prompt. Only the user hook whose command contains codex-hook-wrapper.js is selected; unrelated hooks are not trusted or modified. If the hook command changes later, Codex treats it as modified and the previous trust no longer applies.