Blog
Reproduce an SDK Bug From the Stack You Kept
A reproduction is the command, the version, the error code, and the intent sentence. A stack without those four is a screenshot. Collect them when the process exits.
2026-09-22 · 6 min read · AethelLayer
The minimal repro is usually the command
For a CLI, argv with secrets stripped, plus the version, is the repro. Asking the developer to rewrite 'steps to reproduce' the next day fails because the scrollback is gone.
For an SDK call, the method name, the error code, and a redacted stack are the repro. The full request body is rarely required and often unsafe.
Intent picks the fixture
The same stack on auth login means a different fixture for 'staging' than for 'I ran the sample'. The sentence is how you choose which one to run.
Quote it in the draft. Do not let a template smooth it into 'user experienced an issue'.
Version before you bisect
Reproduce on the version they ran, not on main. A fix you cannot point at their version is a fix they will not believe.
If you cannot reproduce, the missing field is the bug in the probe. Add it. Do not ask the next developer for a screenshare to supply it.
Close the loop in the sample
A reproduction that only lives in a ticket will be hit again. Change the sample or the default, and put the error code in the changelog so search finds the fix.
Humans still send the issue. The reproduction is what makes that send worth it.
Keep reading
Capture the failure before they leave
Capture the failure before they leave. Book early access or talk to sales, then install @aethellayer/sdk when you are onboarded.