Qwen Code Telemetry in Beacon

What is Qwen Code?

Qwen Code is a Gemini CLI fork, but it does not carry Gemini OpenTelemetry export. Beacon therefore treats hooks as the collection path and normalizes Qwen-specific tool names carefully.

Collection path: Native hooks

Authoritative date: August 23, 2026 from Documentation update in the Beacon CLI changelog.

How Beacon reads Qwen Code

Beacon merges a managed hook block into Qwen settings.json, registers events with millisecond timeouts, and maps Qwen tool ids such as run_shell_command, read_file, write_file, edit, and replace into canonical endpoint actions.

The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.

Telemetry coverage

• Session lifecycle and prompt submission
• Pre-tool, post-tool, failed-tool, and permission-request events
• Command and file telemetry with operation mapping
• Subagent events and local JSONL output

What you can do now

• Capture Qwen Code activity without relying on an OTLP exporter.
• Differentiate qwen_code from Qwen model names through closed harness matching.
• Preserve Qwen-specific payload details under raw.qwen for investigation.

Get started

1. Run beacon endpoint hooks install --harness qwen.
2. Restart Qwen Code so new sessions load the updated settings.
3. Use beacon endpoint hooks status --harness qwen to inspect configuration.

Source references

• Runtime docs
• Source reference