iOS Shortcut Workaround for Sending iPhone Photos to Cowork via iCloud Sync
Problem: Cowork's iPhone Photo Access Limitation
The Cowork platform cannot access iPhone camera rolls directly. This means no photo upload from mobile, no Dispatch image support, and no way to share screenshots or photos without workarounds like emailing to yourself or AirDropping to a Mac first. The developer wanted to maintain their workflow of taking screenshots and photos on iPhone and asking Claude questions about them within Cowork sessions.
The PhoPo iOS Shortcut Solution
The workaround involves creating an iOS Shortcut that processes photos and leverages iCloud sync to make them available to Cowork. The shortcut is named "PhoPo" (a play on "photo" and the developer's Claude instance name "PoPo").
Setup Steps
- Create a folder in your Cowork workspace (which automatically syncs via iCloud since Cowork workspaces are iCloud directories)
- Right-click the folder in Finder and select "Keep Downloaded" to prevent macOS from offloading it to iCloud-only storage
- Build an iOS Shortcut with four actions:
Select Photos(accepts multiple photos)Convert Image(to JPEG format - HEIC format won't work)Resize Image(the developer uses 1500px wide with auto height to keep file size reasonable)Save File(to the iCloud folder you created)
- Place the shortcut icon somewhere accessible on your iPhone home screen
Claude Training
Train your Claude instance with this instruction: "When I say 'phopo', check the PhoPo folder for any new images since last check and pull them into this conversation. Also schedule a task to check the folder every 15 minutes so photos are ready when I need them."
Workflow
- On iPhone: Take a photo or select one from camera roll, then share it to your PhoPo shortcut
- The shortcut converts to JPEG, resizes, and saves to the synced iCloud folder
- In Cowork: Say "phopo" (or your trained trigger word) and Claude checks the folder and pulls new images into the conversation
Use Cases and Capabilities
Claude can perform sophisticated recognition on the photos: screenshots of error messages, photos of real-world objects, handwritten notes, receipts, whiteboard scribbles, billboards with links, and more. The developer uses this during Cowork sessions to show Claude what they're looking at, what errors they're encountering, or what screens they're viewing.
Limitations
- Both devices need to be on the same iCloud account
- iCloud sync can lag on cellular networks (instant on WiFi)
- Claude doesn't auto-detect new files - you need to prompt it to check the folder
- Frequent folder checks (more than every 15 minutes) can burn through tokens
📖 Read the full source: r/ClaudeAI
👀 See Also
Structuring Claude Code Agents with CLAUDE.md and .claude/ Directory Patterns
A developer shares their approach to running multiple AI agents using Claude Code, with each agent having its own directory containing a CLAUDE.md file and a .claude/ directory with rules and skills. The key insight is separating always-on context from on-demand workflows to optimize token usage and response quality.
Trellis 2 Successfully Running on ROCm 7.11 with AMD RX 9070 XT
A developer got Trellis 2 working on Linux Mint 22.3 with an AMD RX 9070 XT using ROCm 7.11, fixing two key issues: ROCm instability with high N tensors and a broken hipMemcpy2D in CuMesh.
CLAUDE.md Files Are Often Organized for Developers, Not AI Models – Here's Why That Matters
CLAUDE.md files commonly place Hard Rules at line 47, after background and tech stack. By the time the model reads constraints, it has already constructed conflicting assumptions. A better structure puts hard rules first.
100 Tips for Building a Personal AI Agent: From Cloud Prototype to Production
Six weeks of building a persistent AI agent — not a chatbot wrapper — that manages tasks, tracks deals, reads emails, and analyzes data. Key lessons: Write a Constitution not a system prompt, use flat markdown files for memory, and version your identity file in git.