Plugin
skill-up
An evaluation and evolution tool for Agent Skills.
3 skills1 MCP1.2k
@alibabaMonitoring
Plugin
loongsuite-pilot
Local telemetry collector for AI coding agents.
Plugin Signal62/100Solid
maintained100
capable14
documented75
adopted50
Install
$ npx -y skills add alibaba/loongsuite-pilot --agent claude-code
Stats
218
Stars
57
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
4h ago
Last commit
4mo ago
Created
33m ago
Added
What's inside
README
LoongSuite Pilot
Local telemetry collector for AI coding agents
English | 简体中文
Overview | Quick Start | Documentation | Community | Contributing
Overview
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.
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?
Highlights
| 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 a built-in local dashboard. |
Supported Agents
| 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 |
| Cursor CLI | Shared Cursor hook | Yes | Yes | Yes | Yes |
| DeepSeek Harness | YAML patch plugin + local JSONL polling | Yes | Yes | Yes | Yes |
| Grok Build | Hook + local session logs | Yes | Yes | Yes | Yes |
| Hermes Agent | Native directory plugin | Yes | Yes | Yes | Yes |
| Kiro CLI | Hook / session polling | Yes | Yes | No | Yes |
| MiMo Code | Plugin injection | Yes | Yes | Yes | Yes |
| OpenClaw | Plugin injection | Yes | Yes | Yes | Yes |
| OpenCode | Plugin injection | Yes | Yes | Yes | Yes |
| Pi Coding Agent | Extension 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 |
| Qwen Work CN | Hook / local data polling | Yes | Yes | Yes | Yes |
| Wukong | CLI API polling | Yes | Yes | Yes | Yes |
| WorkBuddy | Hook wakeup + local transcript watch/poll fallback | Yes | Yes | Yes | Yes |
OpenClaw integration supports 2026.3.8 or later with automatic version detection. Before 2026.5.12, model-call timing is inferred from legacy hooks; see compatibility details.
DeepSeek Harness (dsh) loads Pilot's observability plugin from its user-level
cordis.patch.yml. The integration captures native LLM, reasoning, tool, token,
and time-to-first-token events. See Agent Configuration
for activation, source-log, disable, and uninstall behavior.
Documented Windows Agent Support
The table above describes Pilot's general integration capabilities; it does not imply that every agent is supported on every operating system. The following agents are currently explicitly documented as supported on Windows:
| Agent | Windows Integration | Trace Export | Log Export | Token Usage | Conversation / Tool Calls | Requirement |
|---|---|---|---|---|---|---|
| Claude Code | Hook | Yes | Yes | Yes | Yes | — |
| Cursor | Hook | Yes | Yes | Yes | Yes | — |
| Qoder Work | Hook / local data source | Yes | Yes | No | Yes | User edition |
| Qoder CLI | Hook | Yes | Yes | No | Yes | — |
| Qoder IDE | Hook / local data source | Yes | Yes | Yes | Yes | Qoder 1.10.0 or later, User edition |
| OpenCode | Plugin injection | Yes | Yes | Yes | Yes | — |
| WorkBuddy | Hook wakeup + local transcript | Yes | Yes | Yes | Yes | WorkBuddy Desktop 5.3.5.0; Windows 11 installed-product E2E |
Agents omitted from this Windows table do not currently have an explicit Windows support statement; omission does not necessarily mean that the agent cannot run on Windows. See the Alibaba Cloud AI Coding Agent access guide for the source support matrix and Installation for Windows prerequisites and setup.
Agent definitions live in agents.d/. You can add new agents without changing the deployment framework; see Agent Onboarding.
Quick Start
Prerequisites:
- Node.js that can load
node:sqlite(22.13+, 23.4+, or newer). The installer downloads a managed Node.js 22.22 runtime on supported platforms; a system Node.js is accepted only whenrequire('node:sqlite')succeeds. Node.js 18/20 and 22.0–22.12 / 23.0–23.3 are not enough. 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 install
Install 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 install
Verify the service:
loongsuite-pilot status
loongsuite-pilot info
Local 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.
Configure Pilot
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 |
Upstream Trace Linking (optional)
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_PROPAGATE_TO_TOOLS (env) · upstreamLink.propagateToTools (config.json) | propagate trace context and optional resource attributes to supported CLI tool calls | disabled |
LOONGSUITE_PILOT_UPSTREAM_LINK_PROPAGATE_TO_LLM (env) · upstreamLink.propagateToLlm (config.json) | forward trace context to the LLM gateway as a traceparent request header (Claude Code) | disabled |
LOONGSUITE_PILOT_UPSTREAM_LINK_GENERATE_TRACE_WHEN_MISSING (env) · upstreamLink.generateTraceWhenMissing (config.json) | generate and propagate a per-turn local trace context when no valid upstream context is available | 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):
File tree
More plugins by @alibaba.
View @alibaba’s profileFAQ
loongsuite-pilot is a Claude Code plugin with 1 hand-picked skill, indexed on Flowy in the Monitoring category. Install it with the command on its page. It includes loongsuite-pilot-ops. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is loongsuite-pilot?
- Local telemetry collector for AI coding agents
- How do I install loongsuite-pilot?
- Run these in Claude Code: npx -y skills add alibaba/loongsuite-pilot --agent claude-code. Then prompt normally.
- Does loongsuite-pilot auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is loongsuite-pilot free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it