---
title: "Describe a bug without losing the reproduction steps"
description: "A spoken bug report is most useful when it preserves the trigger, observed behavior, expected behavior and a repeatable example."
slug: "bug-report-by-voice"
category: "scenarios"
language: en
editorial_status: published
capability_status: guide
reviewed_at: 2026-10-13
keywords: ["voice bug report","AI coding prompt","Codex debugging request"]
---

# Describe a bug without losing the reproduction steps

A spoken bug report is most useful when it preserves the trigger, observed behavior, expected behavior and a repeatable example. Use typing for exact identifiers and attach visual evidence after checking it.

## A compact spoken structure
Say what you did, what happened and what should have happened. Then add one reproduction condition. For example: “After I switch tasks, the reply draft shows the previous title. It should belong to the new task. This happens after recording and before sending.”

Transcription can alter file paths, build numbers and error messages. Type or paste those details into the reviewed draft instead of trusting phonetic spelling. If you paste a screenshot, inspect it for private material and verify that the intended file is attached.

## Make the request explicit
Tell the agent whether you want diagnosis, a proposed fix or implementation. “Investigate first; do not edit yet” is materially different from “Reproduce and fix it.” Read the resulting prompt for that distinction before delivery.

CueSpec’s available Mac workflow supports local spoken drafts and in-context replies. It does not guarantee that the coding agent can reproduce every environment. A confirmed send only establishes delivery; an eventual explanation, change or test result must be assessed in the task itself.

## Related reading

- [Turn a long spoken idea into a bounded request](/long-idea-short-request/)
- [Mix speech with typed technical identifiers](/dictate-technical-identifiers/)
- [An example: spoken explanation to a clear AI request](/voice-to-prompt-example/)
- [SPECS 01 hardware specification reference](/specs-01-specification/)