Claude Code struggles with Docker/Laravel view caching debugging

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

⎿ # Bug Report: Claude Code struggles with Docker/Laravel view caching debugging

## Summary

Claude Code spent significant time (15+ iterations) attempting to debug why a Laravel
Blade template change wasn't appearing in a Docker container, repeatedly trying the
same cache-clearing approaches without success, and failing to identify the root
cause.

## Environment

• Claude Code CLI
• Model: Claude Opus 4.5
• OS: Ubuntu Linux
• Docker Desktop on Linux
• Laravel 5.7 application with Docker Compose

## What I Asked Claude To Do

1. Add "Japanese Level" field to a Laravel Blade template (showUser.blade.php)
2. Deploy the change using a "fast deploy" script that copies files to a running

Docker container

## What Happened

Claude made the correct edit to the Blade template, but the change never appeared in
the browser despite:

1. The host file having the change (verified)
2. The container file having the change (verified with docker exec cat)
3. MD5 checksums matching between host and container
4. Multiple cache clears (php artisan view:clear, cache:clear, config:clear,

route:clear)

1. Deleting compiled views manually (rm -rf storage/framework/views/*.php)
2. Resetting PHP opcache via HTTP request
3. Restarting the Docker container

## Claude's Behavior Pattern

Claude got stuck in a loop of:

1. Try cache clear command
2. Verify file exists in container
3. User reports change still not visible
4. Try different cache clear command
5. Repeat

This continued for approximately 15+ tool calls without Claude stepping back to
consider alternative hypotheses.

## The Likely Root Cause (Identified Too Late)

The container had duplicate view directories:
``
/var/www/resources/views/admin/showUser.blade.php # Updated
/var/www/html/resources/views/admin/showUser.blade.php # NOT updated
/var/www/html/html/resources/views/admin/showUser.blade.php # NOT updated
``

Laravel may have been loading from one of the html/ subdirectories instead of the
expected location. Claude identified this possibility but only after many failed
attempts.

## Expected Behavior

Claude should have:

1. Formed multiple hypotheses early - not just "it's a caching issue"
2. Searched for duplicate files - find /var/www -name "showUser.blade.php"

should have been one of the first diagnostic steps

1. Checked Laravel's view path configuration - to understand which directory takes

precedence

1. Avoided repeating the same solutions - after 3-4 cache clears didn't work, try

something different

1. Suggested the full deploy earlier - when fast deploy wasn't working, recommend

the reliable alternative

## Suggested Improvements

1. Pattern detection for circular debugging - Claude should recognize when it's

repeating similar actions without progress and explicitly change strategy

1. Docker debugging heuristics - When a file change isn't reflected despite the

file being correct:

• Check for duplicate files in different locations
• Verify which path the application is actually using
• Consider volume mount overlays and precedence

1. "Step back" behavior - After N failed attempts at similar solutions, Claude

should explicitly say: "I've tried X, Y, Z without success. Let me reconsider the
problem from scratch."

1. Laravel-specific knowledge - Understanding that Laravel can load views from

multiple paths and that view.paths config determines precedence

## Reproduction Steps

1. Have a Laravel app in Docker with bind mounts
2. Have duplicate view files in subdirectories (e.g., html/resources/views/)
3. Ask Claude to modify a view and deploy via file copy
4. Observe Claude repeatedly trying cache clears instead of checking for duplicates

## Impact

• User frustration due to prolonged debugging session
• Loss of confidence in Claude's ability to handle Docker deployments
• Time wasted on ineffective solutions

## Additional Context

The "fast deploy" script uses docker cp to copy files and artisan commands to clear
caches. The full deploy script rebuilds the Docker image, which would work but takes
longer.

---

Submitted by: User via Claude Code session
Date: 2026-01-25

What Should Happen?

See error description

Error Messages/Logs

No error message

Steps to Reproduce

See error description

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.12

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_