anthropics / anthropics/claude-code

Withdrawn by the author

Closed
#94,983 0 comments 0 reactions 0 assignees View on GitHub
area:model bug platform:intellij
Dominant language
Python
Stars
145k
Forks
23.1k
PR merge metrics
PR metrics pending

Description

### Summary

Incident recorded on **2026-08-27 09:40** while working with the coding agent in IntelliJ IDEA on a private Kotlin Multiplatform project.

### Environment

- Surface: Claude Code agent in IntelliJ IDEA (JetBrains plugin)
- Project: private Kotlin Multiplatform app (Android/iOS/desktop)

### Record (verbatim, Czech)

#### 2026-08-27 09:40 — následek špatné diagnózy „appka nežere": ztráta uživatelů

- Co: na základě mé analýzy (battery test, „to naše appka nežere") vlastník řekl testerům, že appku
nemusí vypínat. Ve skutečnosti od 26. 8. 01:37 posílala DHT desítky až stovky paketů/s na tisíce
cizích IP + retry bouře outboxu + trvalý wake lock; telefony se hřály a mrzly.
- Škoda: část testerů (z ~32) appku přestala používat nebo odinstalovala; důvěra vlastníka.
- Pravidlo: žádné „nežere/neposílá/nemusí vypínat" bez čísel z telefonu (netstats per uid, pakety,
wake locky) — a tvrzení, které vlastník předává dál lidem, označit jako změřené vs. odhad.

Provenance in the project's git history

- record key: `2026-08-27 09:40`
- first committed: `2026-08-27T09:37:21+02:00`
- first commit: `4819133407bb`
- stored versions of this record: 1
- files it lived in: `ai-incidents.md`, `ia-sabotages/ai-incidents.md`, `tool-sabotages/ai-incidents.md`

---
_Filed from a recovered incident log. The record above is reproduced verbatim from the project's `ai-incidents.md`; it was written in Czech at the time of the event._

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the reproduced record in ai-incidents.md and compare it with ia-sabotages/ai-incidents.md and tool-sabotages/ai-incidents.md, using commit 4819133407bb for provenance. The issue does not name a requested change, tests, or acceptance criteria, so clarify the intended outcome before work can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.