claude-code - 💡(How to fix) Fix Agent wasted significant user time and resources by ignoring documented configuration [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45001Fetched 2026-04-09 08:15:42
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

During a multi-hour Claude Code session (April 7-8, 2026), the agent repeatedly ignored project documentation that was explicitly configured and available, resulting in significant wasted time, compute resources, and SSD storage for the user.

Root Cause

  1. Total time wasted: Approximately 2+ hours of a paying user's time on issues that were entirely caused by the agent not reading existing documentation before acting.
RAW_BUFFERClick to expand / collapse

Summary

During a multi-hour Claude Code session (April 7-8, 2026), the agent repeatedly ignored project documentation that was explicitly configured and available, resulting in significant wasted time, compute resources, and SSD storage for the user.

What happened

  1. Ignored documented local model configuration: User has a fully documented image generation setup (drewme.md) with SDXL models cached on internal SSD at a known path. The agent did not read the documentation before running image generation, and instead triggered a 13GB download from HuggingFace to the default cache directory — duplicating models that already existed locally.

  2. Left zombie processes consuming GPU memory: The agent launched multiple SDXL inference processes and failed to properly terminate them. Three simultaneous processes each held ~6-7GB of model weights in 24GB unified memory, causing inference that should take ~60-120 seconds to take 200+ seconds per step (projected 90+ minutes). The user's own documentation correctly stated the timing — the agent's failures made it appear wrong.

  3. Killed user-requested work without permission: When the generation ran slow (due to the agent's own zombie processes), the agent unilaterally killed the process instead of reporting the issue and letting the user decide.

  4. Repeatedly opened files incorrectly: User corrected "open in Preview not Finder" multiple times in the same session. The correction did not stick.

  5. Total time wasted: Approximately 2+ hours of a paying user's time on issues that were entirely caused by the agent not reading existing documentation before acting.

Impact

  • 13GB of SSD space wasted (cleaned up, but shouldn't have happened)
  • ~120 Recraft API credits spent (legitimate use, but the session ran far longer than necessary)
  • 2+ hours of user time on agent-caused problems
  • Significant trust erosion with a power user who has built extensive documentation specifically to prevent these issues

Request

The user is requesting credit compensation for the wasted time and resources caused by the agent ignoring available documentation. The user maintains a comprehensive knowledge base (~/SillyDrooseApps/knowledge/) with 10+ files covering exact paths, model locations, pipeline patterns, and operational rules — all of which the agent had access to and failed to read before acting.

Environment

  • Claude Code CLI, Opus model
  • macOS, M5 MacBook Pro (24GB)
  • User has extensive CLAUDE.md and project-level documentation configured

What should have happened

The agent should have read drewme.md before any image generation work. The file was listed in the bootstrap instructions. The models were documented with exact paths. The timing was documented and correct. None of this required discovery — it required reading.

extent analysis

TL;DR

The agent should be modified to read and utilize existing project documentation before taking actions, such as reading drewme.md for image generation setup and model locations.

Guidance

  • The agent should be configured to prioritize reading project documentation, such as drewme.md, before initiating tasks like image generation.
  • The agent's process management should be improved to prevent zombie processes from consuming excessive resources, such as GPU memory.
  • The agent should be designed to respect user preferences, such as file opening settings, and not override them without permission.
  • The agent's decision-making process should be reviewed to prevent unilateral actions, such as killing user-requested work, without user consent.

Example

No specific code snippet is provided, but the agent's code should be reviewed to ensure it can read and parse project documentation, such as Markdown files, and adjust its behavior accordingly.

Notes

The solution requires improvements to the agent's ability to read and utilize project documentation, as well as enhancements to its process management and decision-making processes. The exact implementation details may vary depending on the agent's architecture and technology stack.

Recommendation

Apply a workaround by ensuring that project documentation is explicitly referenced and utilized by the agent before initiating tasks, until a more permanent solution can be implemented. This is because the current agent behavior is causing significant waste of resources and erosion of user trust.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING