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

Is Claude Cowork Available on Android?

Yes. Claude Cowork is available in beta through the latest Claude Android app for eligible Pro, Max, and Team accounts. Enterprise access depends on an administrator enabling it. Anthropic's Cowork guide for web, desktop, and mobile describes mobile task access, so the presence of Cowork on Android is no longer an open question. The useful question is whether your account can enter it and whether the task you want is supported on that surface.

Update the Claude app, sign in to the intended account, and select Cowork if the app shows a Cowork selector. Anthropic says its unified experience may let you start a task without a separate selector. If the entry is missing, check the app version, account plan, and any Enterprise administrator setting before treating it as a general Android limitation.

From the phone, you can start a cloud task, steer it, review its progress, and resume it. Connectors, skills, plugins, file previews, and scheduled tasks may be part of the supported work. None of that implies that a Cowork session can freely operate Android's screen, apps, or system settings.

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

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

Anthropic's mobile and desktop guidance distinguishes cloud work from local-resource access. A desktop-started session can use connected local folders while the desktop app is open. Closing that app can remove access to those resources even if cloud work continues. Do not assume a file on your computer becomes available to a phone-started task merely because both devices use the same Claude account. For the wider issue of transferring task state and responsibility between devices, see our 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 Cowork task because its source and output can be checked without changing a calendar. Use an authorized calendar connector if one is available to your Cowork 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 suggested reader task, not a report of a completed test.

Before relying on the brief, check that “tomorrow” refers to the intended date and time zone. Compare the listed events with the authorized source or supplied text, and look for omissions or invented details. 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 task's 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 message and email drafting through Android sharing, along with supported calendar, maps, alarm, and timer actions. Drafting through a share flow does not mean a message was sent. The guide also distinguishes limitations: Claude does not have direct contacts access, and its reminder integration is described for iOS rather than Android.

These capabilities deserve credit, but they answer a different question from “Can this Cowork session access my Android app?” A feature documented for Claude's native Android experience should not be assumed to transfer wholesale into Cowork. Check which surface you are using, which app or connector it can reach, and whether the output is a draft, a planned action, or a completed change.

For a phone-side request, the verification point is 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 acknowledgement alone does not establish any of those outcomes.

Check Task Status and Upcoming Cloud Changes

Mobile Cowork lets you inspect and steer work that may continue in the cloud independently of the phone interface. If a task is still running, use its task controls and status rather than assuming that closing the Android app stopped it. If work has already changed an external calendar, file, or other destination, stopping the session would not itself reverse that change; check the destination separately.

As of September 30, 2026, Anthropic has announced an October 6 transition under which new Pro and Max Cowork tasks will run in the cloud, while preexisting local tasks remain local. That announced change has not yet occurred as of this article's update. It also does not erase desktop dependencies for tasks that need connected local folders or computer use.

When a task appears stalled, check its reported state and whether its required connector or desktop resource remains available. Keep the distinction between a pending task, a completed answer, and an external action that needs its own recovery. Those checks are more useful than treating every mobile session as either entirely local or entirely self-contained.

Choose by What Needs to Change

If you want a brief assembled from connected work sources, start with Cowork and verify the sources and resulting brief. If you want a documented Claude Android integration, use the native app and inspect the draft or destination. If the objective is to read phone calendar entries, create a memo, or change supported device state through an Android phone agent, FoneClaw is the separate phone-action route we provide.

In FoneClaw, a configured compatible model interprets the request, while supported Android tools act 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 that policy; it is not accurate to promise a prompt before every action. Our Features page describes the supported phone tools and controls.

For example, a user can ask FoneClaw to review supported phone calendar information and then separately request a memo based on the checked details. The calendar read, proposed memo text, and saved memo are distinct states to verify. That is not a native integration with Cowork, nor does it imply Cowork lacks its own Android integrations. The practical difference is the object being changed: connected cloud work, a native Claude app handoff, or a supported action on the phone. Our AI Agent Phone Control on Android: Intent, Confirmation, Action explains the intent, permission, action, and result checks for that last route.