Trace: capture Pi subagent evidence from a pinned result format

Abierto
  • ¿Algo no está bien?
#3,713 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #3760 de @waveywaves — cerrado sin fusionar

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend, devtools, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

trace-provider

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 Partial if only the pinned official format is supported.

Non-goals

  • Inferring subagents from parentSession alone.
  • 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.
Lenguaje dominante
Go
Estrellas
582
Forks
61
Merge medio
12 h 47 min
PR fusionados (30 d)
137

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de chainloop-dev/chainloop

Todos los issues de chainloop-dev/chainloop

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.