EXAMPLE — parser refactor interrupted by provider error (synthetic demo)

session ses_demoprovider-error agent build model test-provider/test-model/default export v1.18.31

Started 2026-06-15 05:06:40 UTC · last update 2026-06-15 05:36:40 UTC

messages

tool calls

completed

failed

unfinished

repeated ops

recovered

unresolved

Findings

APIError message #2

Error from provider: rate limit exceeded; retry after 30s

Tool	Calls	Completed	Failed	Avg	Max
read	1	1	0	90 ms	90 ms
write	1	1	0	60 ms	60 ms

Tool	Call	Status	Duration
read	#0	completed	90 ms
write	#1	completed	60 ms

Tool	Call	Status	Output size
read	#0	completed	26 chars
write	#1	completed	12 chars

Reported by OpenCode in the export; not an invoice.

input 200 · output 100 · reasoning 20 · cache read 0 · cache write 0 · cost 0.02

user · 2026-06-15 05:06:40 UTC · #0

Refactor the parser module: extract the tokenizer into its own file.

assistant · 2026-06-15 05:06:40 UTC · finish: tool-calls · #1

read completed call #0 · 90 ms

input

{
 "path": "src/parser.py"
}

(600 lines of parser code)

write completed call #1 · 60 ms

input

{
 "content": "…extracted tokenizer…",
 "path": "src/tokenizer.py"
}

file written

assistant · 2026-06-15 05:07:40 UTC · finish: stop · #2

APIError — this message ended with an error:

Error from provider: rate limit exceeded; retry after 30s

done

This report describes what the exported data shows. It does not prove that a run was correct, complete, or caused any particular outcome.
"Identical" means canonical-JSON-equal tool input. Calls that differ only in volatile values (timestamps, random ids) are not grouped.
An identical call repeated after a success is not necessarily a bug; it may be polling, verification, or a re-read.
Missing completion evidence is reported as unknown, not as failure.
Token counts and cost come from the export as reported by OpenCode; they are not an invoice.
One export file covers one session. Subagent/child sessions appear as separate exports and need their own run.
Attached files and patches are summarized (names, sizes, paths); embedded file content is not expanded into the report.
The tool reads a local JSON file only: no network requests, and the input file is never modified.