Trace: capture Pi subagent evidence from a pinned result format

Aberta
  • Algo errado?
#3,713 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

  • #3760 de @waveywaves — fechado sem integrar

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
backend, devtools, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Go
Estrelas
582
Forks
61
Merge médio
12h 47min
PRs com merge (30d)
137

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de chainloop-dev/chainloop

Todas as issues de chainloop-dev/chainloop

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.