3 Dominant Themes
| Theme | Summary | Representative Quote |
|---|---|---|
| 1️⃣ Container / sandbox friction | Deploying Claude in containers (Dispatch/Cowork) often hits permission roadblocks – PDF handling, Git lock‑files, and network access are limited or broken. | “Cowork gets tangled with git as well. Fails, and then can't delete lock files.” – _puk “Cowork won't download and fill out or read pdfs or other files due to container permissions.” – hahajk |
| 2️⃣ Local hardware as a persistent sandbox | Many users run Claude on a dedicated Mac mini or an M1/M2 MacBook, using remote‑control (Tailscale, Blink iOS, SSH) to keep a “always‑on” environment that’s cheaper than a full‑time server. | “I’ve been doing something similar with an old m2. It isn’t powerful enough for local models, well sufficient local models but for openclaw and Claude it’s been perfect.” – rootsudo “I’d love to just have Claude use my machine as a sandbox host instead of having to run RC on each host session.” – theptip |
| 3️⃣ Cost, pricing opacity, and skepticism about value | The convoluted subscription tiers and high per‑token costs make casual experimentation pricey, leading many to question whether the productivity gains justify the expense. | “With the $200 Claude subscription I was able to get around $13‑15k of API equivalent usage in one month.” – iambenm “None of these are things I want or need in the product I maintain with a team, there's really no point to any of this unless you run a vibe‑coded SaaS (?).” – deadbabe |
These three themes capture the most frequently voiced concerns and observations across the discussion.