Keep the context.
Capture the source, command output, and failure details together. Give the next person more than a stack trace.
Reproduce bugs.
Anywhere.
From “it works on my machine” to a bug your team can actually investigate. Capture the failure. Share the context. Verify the fix.
Your project. Your bug. A shared starting point.
One bug. The whole picture.
capture.log
$ reprolane capture command "npm test"
Collecting project files…
Recording command output…
TypeError: Cannot read properties of undefined
Capture complete. Ready to investigate.
TerminalExample output
Failure captured
Source, evidence, and replay. One place.
The failure. And everything behind it.
Capture the source, command output, and failure details together. Give the next person more than a stack trace.
Goodbye, setup.
Hello, understanding.
A bug report should be a starting point, not a scavenger hunt. Bring the code, the failure, and the tools to investigate into one shared workflow.
Get straight to the bug.
Open the files, inspect the evidence, and run commands in a live workspace. Spend your time investigating the issue.
Know what changed.
Replay the captured failure after a change. Compare the result with the original evidence before you merge.
It starts with
one command.
Open your project. Capture a command failure or browser issue. Give your team a reproduction they can work with.
Your terminal
npx @reprolane/cli captureChoose a capture workflow in your project terminal.
A little more
context.
Your questions, reproduced here.
What is a reproduction?
A reproduction brings the source files and evidence behind a bug together. Your team can inspect the captured failure, open a workspace, and request a replay to compare the behavior.
What can I capture?
You can capture a failing command, a local browser session, or an authored browser scenario. Run the CLI in your project and choose the workflow that fits the issue.
Does a capture automatically verify the bug?
Capture records what happened on your machine. Verification is a separate action that replays the captured issue in an isolated environment and compares the result with the original evidence.
Can I share a reproduction with my team?
Yes. Share the reproduction URL with people who have access. Reproduction visibility and organization access determine who can open it.
Can I investigate without setting up the project locally?
Open a live reproduction workspace to inspect source files, use the terminal, and explore the captured evidence. The workspace gives your team a shared place to investigate.
Less back and forth.
More moving forward.
Your next bug deserves a better starting point.
Start reproducing