Trace: capture Pi subagent evidence from a pinned result format
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #3760 来自 @waveywaves —— 已关闭，未合并
评估
调研方向
Start by reading the Pi support shipped in #3704 and the accounting contract in #3706; the issue does not name specific files or tests. Then inspect the pinned official Pi subagent extension format and trace how provider, parser, and action regressions cover single, parallel, chained, failed, and abandoned results. Done means the stated acceptance criteria pass, a live Pi E2E scenario is added, and the compatibility cell reflects measured support.
由索引模型根据 Issue 内容生成。
描述
Problem
Pi support records only the selected root session. The compatibility matrix marks Pi subagents as No, so child conversations, tool activity, and usage are absent from CHAINLOOP_AI_CODING_SESSION evidence.
Scope
Support the commit-pinned result format of Pi's official subagent example extension. Map identifiable child messages and usage into deterministic subagent evidence and raw-session streams.
Acceptance criteria
- Pin the supported official Pi subagent extension commit and supporting files.
- Parse single, parallel, and chained child results with deterministic child IDs and raw streams.
- Preserve child conversation content and tool results, not only aggregate token counts.
- Count child input, output, cache, and cost exactly once under the normalized accounting contract from #3706.
- Handle failed children and malformed optional result details without blocking push.
- Exclude abandoned root branches and unrelated extension records.
- Add provider/parser/action regressions and a live Pi E2E scenario.
- Update the Pi compatibility cell from measured results, using
Partialif only the pinned official format is supported.
Non-goals
- Inferring subagents from
parentSessionalone. - Supporting arbitrary third-party Pi extensions.
- Changing Pi's root session-tree selection contract.
Dependencies
- #3706 must define Pi cache and total-token semantics before child usage is aggregated.
- Baseline Pi support shipped in #3704.
- 主要语言
- Go
- 星标
- 582
- 派生
- 61
- 平均合并
- 12 小时 47 分钟
- 30 天内合并 PR
- 137
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
chainloop-dev/chainloop 的其他 Issue
-
feature-parity trace-provider
难度 2/5 1-3 小时 新手友好度 70/100
chainloop-dev/chainloop#3802 ·
维护者通常 1 天内回复
-
bug trace-provider
难度 4/5 3-5 天 新手友好度 48/100
chainloop-dev/chainloop#3803 ·
维护者通常 1 天内回复
-
feat(trace): support GitHub Copilot (CLI and VS Code) in Chainloop Trace可能已有人在做 @migmartri 今天认领。 未关闭Feature spec trace-provider
chainloop-dev/chainloop#3800 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Allow enabling policy enforcement at the workflow contract level可能已有人在做 @migmartri 于 10 天前认领。 未关闭component/backend new-policy spec
chainloop-dev/chainloop#3762 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
chainloop component/CLI performance trace-provider
难度 4/5 3-5 天 新手友好度 62/100
chainloop-dev/chainloop#3756 ·
维护者通常 1 天内回复
查看 chainloop-dev/chainloop 的全部 Issue
相似的 Issue
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
维护者通常 1 天内回复
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
model:sonnet runtime:claude security size:S
难度 2/5 1-3 小时 新手友好度 78/100
FootprintAI/Containarium#3624 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复