AI Agent Guide
📅 2026-10-24 ⏱️ 7 min read Dean Dean

Claude Cowork on Android: How to Access It and What It Can Do

Access Claude Cowork on Android with an eligible account, understand the unified chat entry and current cloud behavior, and distinguish native Android actions.

Claude Cowork task status shown on an Android phone alongside connected work and phone actions
📋 Key Takeaways
  • Claude Cowork is available on Android for eligible paid Pro and Max accounts, in beta for Team, and for Enterprise where an administrator enables it.
  • The unified Claude experience may remove the Chat/Cowork selector. Describe your task in the conversation when that experience is enabled; a missing selector alone does not mean access is unavailable.
  • Since October 6, new Pro and Max sessions run in the cloud across surfaces. Older local tasks remain local, and access to connected computer folders still requires the desktop app to be open.
  • Native Claude Android integrations and FoneClaw phone tools are separate action routes. Check the actual destination to distinguish prepared text, completed work and a saved or sent result.

Is Claude Cowork Available on Android?

Yes. Claude Cowork is available through the latest Claude Android app for eligible paid Pro and Max accounts, in beta for Team, and for Enterprise where an administrator enables it. Anthropic's Cowork guide for web, desktop, and mobile confirms mobile access. The useful question is whether your account can use it and whether the intended task fits that surface.

Update the app and sign in to the intended account. Select Cowork if a selector appears. In the unified chat and Cowork experience, there is no separate selector: describe your task in a conversation. Its absence alone is not a fault. Check plan eligibility, rollout and any organization settings before treating it as an Android limitation.

From the phone, you can start, steer, review and resume supported work using authorized connectors and account files. This does not imply unrestricted control of Android screens, apps or system settings.

What Runs on Mobile, in the Cloud, or on Desktop?

The phone can be a real starting and review point without becoming the execution environment for every step. The location of the requested source matters more than the device used to type the instruction.

WorkWhere to start or inspect itImportant boundary
Cloud task using authorized connected sourcesEligible Cowork on Android, web or desktopCheck connector access and the reported output.
Review, steer or resume workLatest Claude Android appClosing the phone view does not necessarily stop cloud execution.
Access connected local computer foldersThrough the desktop appThe desktop app must remain open for that access.
Documented native Android integrationClaude's Android chat experienceDo not assume the same action is available in every Cowork session.
Supported phone setting or Android recordAn action tool with the required permissionsConfirm the device or destination actually changed.

Cloud work can continue while the computer is closed. Local folders, however, remain on the computer; access depends on the open desktop app, and only a requested file is copied into the cloud when needed. A shared account does not make every computer file automatically available to a phone-started task.

For the wider issue of transferring task state and responsibility between devices, see Secure Cross-Device AI Agent Handoff: State, Approval, and Recovery.

Start With a Read-Only Schedule Brief

A small schedule brief is a useful first task because its source and output can be checked without changing a calendar. Use an authorized calendar connector if one is available to your session. Otherwise, supply a short, nonsensitive schedule yourself; do not ask Cowork to infer access it does not have.

For example: 'Using only the calendar you can access, prepare a brief of tomorrow's events. Include each event's time, title and source. Flag missing details. Do not create, edit or send anything.' If you supply text instead, replace the first sentence with 'Using only the schedule pasted below.' This is a proposed reader workflow based on official documentation, not a report of a completed test.

Before relying on the brief, confirm that tomorrow means the intended date and time zone. Compare the listed events with the authorized source or supplied text, and look for omissions or invented details. Starting the task is not completion; a completed answer still needs source verification. The result is a prepared summary, not evidence that a reminder was scheduled or a calendar entry changed.

If you later want the brief repeated, inspect the connected sources, schedule and permissions before enabling recurring work. A read-only preparation step gives you something concrete to review before adding a follow-up action.

Claude Android Actions Are Separate From Cowork

Claude's Android app does more than chat. Anthropic's Android app integration guide documents reviewed message and email handoffs through Android sharing, along with supported calendar, maps, alarm and timer actions. A prefilled message is not a sent message. Claude does not have direct contacts access, and reminders are supported on iOS rather than Android.

These capabilities answer a different question from whether a particular Cowork session can reach an Android app. A feature documented for native Claude chat should not be transferred wholesale into every Cowork session. Check the surface, the available integration and whether the output is a draft, a proposed action or a completed change.

For a phone-side request, verify the destination. An email draft should be visible for review; a calendar change should appear on the intended calendar; an alarm should exist in the clock app. A conversational acknowledgment alone does not establish those outcomes.

Check Task Status and Current Cloud Behavior

Inspect running work through its task controls and status rather than assuming that closing the Android app stopped it. If work has already changed a calendar, file or other destination, stopping the session does not itself reverse that change. Check the destination separately.

Anthropic's current cloud guidance states that new Pro and Max sessions have run in the cloud on every surface since October 6, 2026. The Only on your computer option was removed; those plans do not have a location chooser or switchback for new Cowork tasks. Pre-October 6 local sessions remain local until finished. Existing local schedules also stay local, while new scheduled tasks run in the cloud. Do not generalize this Pro and Max migration to every plan.

When work appears stalled, check its reported state, connector authorization and required desktop resources. Distinguish a task that started, one that completed and an external result you have independently verified. A missing local file may need the desktop app reopened, while a failed external action may need destination-specific recovery.

Choose by What Needs to Change

If you want a brief assembled from authorized connected work sources, use the available Cowork route and verify the sources and brief. If you want a documented Claude Android integration, use native chat and inspect the handoff or destination. For broader task-specific choices involving browser execution, Claude Duet Alternatives for Android: Choose by the Task covers that separate decision.

FoneClaw provides supported Android phone tools for tasks such as reading permitted calendar information, saving a personal To-Do or changing supported device state. Start with our free default model route or configure a compatible external model when needed. The model interprets and plans; enabled Android tools execute under operating-system permissions and the applicable global and per-tool approval policy.

An online model may receive selected task context. Approval behavior depends on the configured policy, not a promise of a prompt before every action. Our Features page describes the supported phone tools and controls.

For example, ask FoneClaw to review supported phone calendar information, check the details, then separately request a personal To-Do. The calendar read, proposed wording and saved item are distinct states. Inspect the destination before retrying an uncertain result.

This is a separate phone-action route, not a native Cowork integration or an automatic send operation. The practical distinction is what must change: connected work material, a native Claude app handoff or Android phone state. AI Agent Phone Control on Android: Intent, Confirmation, Action explains the permission, execution and result checks for that last route.

Frequently asked questions

First check whether you have the unified Claude experience: it removes the Chat/Cowork selector, so you can describe a task directly in a conversation. Otherwise, update the Android app and confirm the intended account. Mobile access is available for eligible paid Pro and Max accounts, in beta for Team, and for Enterprise where an administrator enables it. A missing selector alone does not establish that access is unavailable; check plan, rollout and organization settings.
Try FoneClaw