English | 简体中文
Quick Start | Documentation | Agent Onboarding | License
LoongSuite Pilot is a local telemetry collector for AI coding agents. It discovers supported agents on a developer machine, installs the required hooks or plugins, normalizes activity into a shared GenAI event schema, and exports logs or traces to your chosen backends.
Local dashboard — multi-agent collection status, token usage, and reporting health at a glance.
Development teams often use more than one AI coding agent, and each agent records activity in a different local format. Pilot gives teams one local collector that can discover those agents, collect their activity, normalize the data, and send it to destinations that are useful for analysis, audit, and observability.
Pilot is designed to answer practical questions:
- Which agents are being used?
- What model, session, turn, and tool activity happened?
- How much token usage is available from each agent?
- Where should the data be exported: local files, SLS, HTTP, or traces?
- How should sensitive prompts, tool arguments, and secrets be controlled before export?
| Capability | What Pilot Does |
|---|---|
| Agent discovery | Detects supported agents from local paths and commands. |
| Collection deployment | Installs hooks or plugins and reads local logs, sessions, or data files. |
| Unified event schema | Normalizes agent-native events into a shared GenAI schema. |
| Multi-destination output | Exports to JSONL, Alibaba Cloud SLS, HTTP, and OTLP trace backends. |
| Privacy controls | Supports per-agent content capture policy and secret masking before output. |
| Local operations | Provides service status, restart, rollback, and optional local dashboard commands. |
| Agent | Integration | Trace Export | Log Export | Token Usage | Conversation / Tool Calls |
|---|---|---|---|---|---|
| Claude Code | Hook | Yes | Yes | Yes | Yes |
| Codex | Hook | Yes | Yes | Yes | Yes |
| Cursor | Hook | Yes | Yes | Yes | Yes |
| Kiro CLI | Hook / session polling | Yes | Yes | No | Yes |
| OpenCode | Plugin injection | Yes | Yes | Yes | Yes |
| Qoder | Hook | Yes | Yes | Yes | Yes |
| Qoder CN | Hook | Yes | Yes | Yes | Yes |
| Qoder for JetBrains | Detection-only | Yes | Yes | Yes | Yes |
| Qoder CLI | Hook / session polling | Yes | Yes | Yes | Yes |
| Qoder Work | Hook / local data polling | Yes | Yes | Yes | Yes |
| Qoder Work CN | Hook / local data polling | Yes | Yes | Yes | Yes |
| Qwen Code CLI | Hook | Yes | Yes | Yes | Yes |
| Wukong | CLI API polling | Yes | Yes | Yes | Yes |
Agent definitions live in agents.d/. You can add new agents without changing the deployment framework; see Agent Onboarding.
Prerequisites:
- Node.js 18 or later
npmcurlorwget- PowerShell 5.1 or later on Windows
Install from the public package on Linux or macOS:
curl -fsSL https://loongcollector-community-edition.oss-cn-shanghai.aliyuncs.com/loongsuite-pilot/installer.sh -o /tmp/loongsuite-pilot-installer.sh && bash /tmp/loongsuite-pilot-installer.sh installInstall from the public package on Windows:
$installer = "$env:TEMP\loongsuite-pilot-installer.ps1"
Invoke-WebRequest `
-Uri "https://loongcollector-community-edition.oss-cn-shanghai.aliyuncs.com/loongsuite-pilot/installer.ps1" `
-OutFile $installer
powershell.exe -NoProfile -ExecutionPolicy Bypass -File $installer installVerify the service:
loongsuite-pilot status
loongsuite-pilot infoLocal JSONL output is enabled by default under ~/.loongsuite-pilot/logs/output/ on Linux/macOS and %USERPROFILE%\.loongsuite-pilot\logs\output\ on Windows.
For installer options, uninstall commands, and source builds, see Installation.
Configuration is loaded in this order: environment variables, then ~/.loongsuite-pilot/config.json, then built-in defaults.
Start with the guide that matches what you want to change:
| Task | Guide |
|---|---|
| Choose agents and content capture policy | Agent Configuration |
| Write local JSONL logs | Local JSONL Output |
| Report logs to SLS | SLS Output |
| Report OTLP traces | Trace Output |
| POST events to HTTP | HTTP Output |
| Mask secrets before output | Data Masking |
| See global config loading and retention settings | Configuration Guide |
Link collected agent spans to an upstream trace so each turn's span tree reparents under the upstream span. Disabled by default, and fully fail-open (never affects normal collection/reporting).
| Setting | Values | Default |
|---|---|---|
LOONGSUITE_PILOT_UPSTREAM_LINK (env) · upstreamLink.enabled (config.json) |
true / 1 to enable; unset, false, or 0 to disable |
disabled |
LOONGSUITE_PILOT_UPSTREAM_LINK_TTL_MS (env) · upstreamLink.ttlMs (config.json) |
cleanup TTL in ms for acp-correlate files |
86400000 (24h) |
When enabled, the upstream traceparent reaches Pilot via one of two schemes and is stamped onto collected records (trace_id on the turn, parent_span_id on the user-input event):
- Correlation file (per-turn): the caller writes
{sessionId, contentHash, contentPrefix, traceparent}to~/.loongsuite-pilot/acp-correlate/<sessionId>.jsonlwhen it sends a prompt. Linking is protocol-agnostic — the only requirement is thatsessionIdmatches thegen_ai.session.idPilot collects for that turn, and the content (hash or prefix) matches the collected user text. ACP clients satisfy this naturally (thesession/newid flows into collection), so ACP is the primary case. - Environment (
TRACEPARENTon the agent process): applied to the session's first turn, via the agent's hook. Use this when the caller cannot obtain a per-turnsessionIdup front.
| Backend | Use Case |
|---|---|
| JSONL | Local backup and easy inspection. Enabled by default. |
| SLS | Alibaba Cloud Log Service reporting. Supports WebTracking and AK modes. |
| HTTP | POST batches to a custom endpoint. |
| OTLP Trace | Export GenAI activity as OpenTelemetry traces. |
LoongSuite Pilot emits a normalized GenAI event schema across all supported agents. See Output Event Schema for event names, field definitions, provider values, finish reasons, and sensitivity notes for opt-in content fields.
Use the loongsuite-pilot command after installation:
loongsuite-pilot start
loongsuite-pilot stop
loongsuite-pilot restart
loongsuite-pilot status
loongsuite-pilot info
loongsuite-pilot token-usage
loongsuite-pilot rollbackOptional local dashboard:
loongsuite-pilot monitor startThen open http://127.0.0.1:8765/.
macOS menu bar app:
On macOS, Pilot automatically runs a menu bar app after installation — no extra command needed. It shows live token, session, request, and tool counts, plus per-agent and per-provider breakdowns, so you can keep an eye on activity without opening the dashboard.
To disable it, set LOONGSUITE_PILOT_ENABLE_STATUS_BAR_APP=false or add "enableStatusBarApp": false to ~/.loongsuite-pilot/config.json.
User Manual - Complete guide to installing, configuring, operating, and extending Pilot
Installation Guide - Install from package, verify service, uninstall, and run from source
Configuration Reference - Global config loading, runtime switches, retention, and links to output and privacy setup
Output Schema - Normalized event names, fields, provider values, and finish reasons
Developer Guide - Add support for a new AI coding agentBuild From Source
git clone https://github.com/loongsuite/loongsuite-pilot.git
cd loongsuite-pilot
npm install
npm run build
node scripts/postinstall.js
node dist/index.jsFor local development:
npm install
npm run build
npm run typecheck
npm testFor packaging and service installation from a local build, see Installation.
We are looking forward to your feedback and suggestions. Scan the QR code below to join the LoongSuite Pilot DingTalk group.
| LoongSuite Pilot SIG |
|---|
 |
- LoongCollector - Universal node agent for log, metric and eBPF-based collection
- LoongSuite JS - OpenTelemetry instrumentation plugins for JS-based AI coding agents
- LoongSuite Python - Process agent for Python applications
- LoongSuite Go - Process agent for Golang with compile-time instrumentation
- LoongSuite Java - GenAI telemetry utility library for Java applications
Apache License 2.0 - see LICENSE for details.