Cowork: Mobile App Missing Desktop Features — What to Do

You're trying to use Cowork on your iPhone or Android phone and finding that file tools, scheduled tasks, plugins, and local connectors aren't available like they are on the desktop. This isn't a limitation of the app—it's by design. Claude's mobile app handles chat and voice and talks to cloud-hosted connectors. File tools and scheduled tasks run only on the desktop because they need a workspace folder and a persistent runtime that phones don't expose. The solution is to design workflows where the desktop produces the artifact and a connector delivers it to you.

What Works on Mobile vs. Desktop

Mobile (Claude app on iOS / Android):

• Chat and voice with Claude
• Cloud-hosted connectors: Gmail, Slack, Drive (when configured at the account level), Calendar
• Reading artifacts: viewing tables, trackers, spreadsheets, or documents created by Cowork
• Viewing scheduled task outputs that land in Slack, email, or calendar

Desktop (Cowork on macOS / Windows):

• Chat with full agent capabilities
• File tools: read, create, modify files in local folders
• Scheduled tasks: daily, weekly, or ad-hoc automation
• All local connectors and custom MCP servers
• Plugins
• Full access to workspace folders

The pattern that works across distributed teams is clear: design workflows so the desktop does the heavy lifting and a connector delivers the result to the team.

Workflow Design: Desktop Produces, Connector Delivers

How ScaleIT handles this: See AI Quick-Start

Instead of expecting parity between mobile and desktop, build workflows where each plays its natural role.

Example 1: Morning Report

• Desktop Cowork runs a scheduled task at 8 a.m.
• Task pulls data from multiple sources and creates a formatted report.
• Task posts the report to Slack #operations.
• Team member reads the report on their phone while commuting, via Slack, no Cowork app needed.

Example 2: File Processing

• Desktop Cowork reads a folder of raw data files.
• Processes and structures them into a spreadsheet.
• Uploads the result to a shared Drive.
• Team member opens the Drive file on mobile and reviews it.

Example 3: Weekly Board Update

• Desktop task pulls updates from Jira, converts them to a calendar event, and posts to Slack.
• Users read the summary on mobile from Slack and calendar.

The mobile app becomes a consumer of outputs, not a producer of automations. This keeps the architecture clean and prevents the frustration of trying to run complex workflows on a device that can't stay connected to a workspace.

If You Need Mobile Access to Cowork Features

If your team genuinely needs to create or modify automations from mobile (unusual, but possible in some workflows):

1. Use the browser version. Open Safari (iOS) or Chrome (Android) and navigate to Claude.ai. Log in and access your Cowork instance. You'll have full feature access, though the mobile browser experience is less optimized than the native app.
2. Design for offline-first data. If you need mobile-triggered automations, store connectors and configuration in cloud services (Slack, Drive, Airtable) rather than local files. Then mobile can read and write to the cloud while the desktop handles file system operations.

For the vast majority of teams, the desktop-produces-mobile-reads pattern is cleaner and more reliable than trying to do everything on the phone.

Verify

• You can read artifacts created by Cowork on your mobile device via Slack, email, or Drive.
• Team members can use the Claude mobile app for chat and voice without missing desktop-only features.
• Scheduled tasks post their output to a channel or app everyone can see.

Design workflows that work across all your devices without forcing mobile to do desktop-level work. ScaleIt helps teams architect Cowork deployments where the right tool does the right job. Contact us for a free consultation.