Support directed me here after a formal complaint received no human review — defect details available on request
Preflight Checklist
- [x] I have searched existing issues for similar behavior reports
- [x] This report does NOT contain sensitive information (API keys, passwords, etc.)
Type of Behavior Issue
Other unexpected behavior
What You Asked Claude to Do
I am opening this issue because Anthropic Support directed me to GitHub Issues, three separate times in writing, as the appropriate channel for a reproducible defect in Claude Code.
Context, stated only as far as necessary:
On 13 August 2026 I submitted a formal complaint concerning Claude Code, supported by a nine-page document containing dated incidents, session identifiers, an hours calculation and figures verified on disk. One of the three items in that complaint was a reproducible technical defect, submitted with a request that it be escalated to the product team.
The complaint was handled entirely by an automated agent, across four exchanges between 09:28 and 11:46 of that same morning. No person reviewed it. The automated agent stated on each occasion that it could not escalate the report internally, and on each occasion asked me to describe the issue again. I complied once, in tabular form. It then asked a fourth time.
Why this issue contains no reproduction steps:
The defect, its reproduction, the affected component, the session identifiers and the verified figures were already submitted in full through the channel Anthropic itself designated. Documenting them for a fifth time, in a fifth format, is not a reasonable thing to ask of a customer, and I decline to do it.
I am complying with the instruction by opening this issue. The complete technical report is available immediately to any Anthropic employee who contacts me directly at [therosomni@gmail.com](mailto:therosomni@gmail.com).
If the defect matters, the information is one email away.
What Claude Actually Did
I am opening this issue because Anthropic Support directed me to GitHub Issues, three separate times in writing, as the appropriate channel for a reproducible defect in Claude Code.
Context, stated only as far as necessary:
On 13 August 2026 I submitted a formal complaint concerning Claude Code, supported by a nine-page document containing dated incidents, session identifiers, an hours calculation and figures verified on disk. One of the three items in that complaint was a reproducible technical defect, submitted with a request that it be escalated to the product team.
The complaint was handled entirely by an automated agent, across four exchanges between 09:28 and 11:46 of that same morning. No person reviewed it. The automated agent stated on each occasion that it could not escalate the report internally, and on each occasion asked me to describe the issue again. I complied once, in tabular form. It then asked a fourth time.
Why this issue contains no reproduction steps:
The defect, its reproduction, the affected component, the session identifiers and the verified figures were already submitted in full through the channel Anthropic itself designated. Documenting them for a fifth time, in a fifth format, is not a reasonable thing to ask of a customer, and I decline to do it.
I am complying with the instruction by opening this issue. The complete technical report is available immediately to any Anthropic employee who contacts me directly at [therosomni@gmail.com](mailto:therosomni@gmail.com).
If the defect matters, the information is one email away.
Expected Behavior
I am opening this issue because Anthropic Support directed me to GitHub Issues, three separate times in writing, as the appropriate channel for a reproducible defect in Claude Code.
Context, stated only as far as necessary:
On 13 August 2026 I submitted a formal complaint concerning Claude Code, supported by a nine-page document containing dated incidents, session identifiers, an hours calculation and figures verified on disk. One of the three items in that complaint was a reproducible technical defect, submitted with a request that it be escalated to the product team.
The complaint was handled entirely by an automated agent, across four exchanges between 09:28 and 11:46 of that same morning. No person reviewed it. The automated agent stated on each occasion that it could not escalate the report internally, and on each occasion asked me to describe the issue again. I complied once, in tabular form. It then asked a fourth time.
Why this issue contains no reproduction steps:
The defect, its reproduction, the affected component, the session identifiers and the verified figures were already submitted in full through the channel Anthropic itself designated. Documenting them for a fifth time, in a fifth format, is not a reasonable thing to ask of a customer, and I decline to do it.
I am complying with the instruction by opening this issue. The complete technical report is available immediately to any Anthropic employee who contacts me directly at [therosomni@gmail.com](mailto:therosomni@gmail.com).
If the defect matters, the information is one email away.
Files Affected
Permission Mode
Accept Edits was OFF (manual approval required)
Can You Reproduce This?
Yes, every time with the same prompt
Steps to Reproduce
_No response_
Claude Model
Opus
Relevant Conversation
Impact
Critical - Data loss or corrupted project
Claude Code Version
Versão 1.28929.0 (d1a6bc)
Platform
Anthropic API
Additional Context
_No response_