AI assistants on phones have long been better at talking than at doing. Anthropic is trying to close that gap on Android, where Claude can now connect to the apps already installed on a device. A request made in a conversation can turn into a real alarm, a calendar entry or a drafted message, without the user having to copy and paste anything between apps.
The idea is simple, but the details matter, because they decide what the assistant can touch, what it can’t, and how much control stays with the person holding the phone. What follows is a look at what Anthropic says the feature does, how it works, and what an independent test found when it was put to use.
What Anthropic says Claude can do
According to a help page published by Anthropic on August 25, 2026, the feature is supported on all Claude plans and works with both native and third-party apps. Claude can draft and send messages through the default messaging app or through services such as WhatsApp, Slack and Messenger, and it can compose emails that open in the phone’s email app with the text already filled in. It can also use the device’s location to suggest nearby places, show those places on an interactive map, and hand them off to Google Maps for turn-by-turn directions.
Beyond communication and navigation, Claude can read the calendar, check availability, create events and schedule meetings. It can set alarms and timers through the Clock app, and, on some plans, it can read and analyze health data from Health Connect and present the results in native charts.
How a request turns into an action
Claude does not take over the phone. When it decides that one of these features would help, it offers it automatically and shows a card inside the conversation. The user reviews the proposed action and taps the card to pass it to the right app.
For a message or email, the flow is deliberately manual at the end. A user might ask Claude to draft a note to a supervisor about a project update. Claude prepares the text and shows a preview, and tapping the card opens the messaging or email app with the content already in place. The person can change anything before sending it as usual, which means nothing leaves the phone until they press send.
Calendar requests follow a similar pattern. Claude can look at a schedule and find free slots, create a single event, or set up a recurring one, such as a workout every Tuesday and Thursday at 6 AM, and the user can edit or delete any event afterwards. Alarms and timers are the simplest case, because Claude creates the alarm or starts the timer directly and the Clock app takes care of the rest, including the notification when it goes off.
Location requests work the same way. Asked for nearby restaurants or parks, Claude requests access to the device’s location if it doesn’t already have it, then returns suggestions that can be viewed on a map, with each point open to a tap for more detail.
What Claude can and can’t see
The connection runs through Android’s standard sharing and intent systems, the same mechanisms any app uses to hand a task to another. That keeps the design fairly narrow, and Anthropic is specific about the boundaries. Claude does not read existing messages or emails and only creates new content. It has no direct access to the contact list, and it uses the location only when a request calls for it. Alarms and timers are created without touching personal data, and calendar access covers only the event details needed to check availability or to create and change events.
Permissions follow the same cautious logic. Messages and email need none at all, because they rely on the system share sheet. Reading the calendar, using the location and reaching Health Connect each ask for permission at the moment they are needed, with an explanation of why, and the user can allow the request once, always allow it, or deny it. Calendar events can even be drafted through the system interface without special permission. Everything can be adjusted later in the phone’s app settings, where each permission can be limited to times when the app is in use, set to ask every time, or removed.
Health data, with conditions attached
The most restricted part of the feature is the Health Connect integration. Anthropic describes it as a beta that is available only on Pro and Max plans, requires Android 14 or later, and is currently limited to users in the United States.
Health Connect is Android’s central store for fitness and health information, gathering data from apps and wearables such as Fitbit, Samsung Health and Google Fit. With the user’s permission, Claude can read activity figures like steps, distance and active calories, as well as workouts, vital signs, body measurements, sleep and nutrition data when those are tracked. It can read this information but can’t write to it or alter any entries.
When a user asks about their health data, the answer can come with native Android charts, including bar charts that compare activity across days or weeks, line charts that track trends in pace, heart rate or weight, and progress indicators for goals. Health permissions are managed separately from the rest, so the user chooses exactly which data types to share.
Anthropic is explicit that Claude is not a medical device and can’t provide medical guidance. It also says that Claude does not save health information to memory by default, although turning on the option to include sensitive topics in memory changes that.
Limits Anthropic acknowledges
The help page lists several boundaries itself. Reminders remain exclusive to Claude for iOS and are not available on Android, and members of Team and Enterprise plans can’t use the location tool for now. Whether Claude can edit a calendar event depends on who owns that event, and Health Connect doesn’t work inside Android work profiles. Anthropic also notes that some features may behave differently depending on the Android version and the phone’s manufacturer.
What a hands-on test found
Documentation describes intent, and daily use tells a different story. A comparison published by MakeUseOf, which tested Claude’s Android abilities against those of Gemini, paints a more mixed picture.
The calendar was one of the clearer successes. Claude was able to add an event to the device calendar and confirm that it had done so. The reviewer also pointed out a practical detail that is easy to miss: for Claude to use the device calendar directly, the Google Calendar connector has to be switched off, and the first time access is set up the user can choose which calendars Claude may see.
Messaging proved a weaker spot. Although Anthropic says Claude can send text messages as well as WhatsApp and Slack messages, the tester reported that this did not seem to work as described, and that the Slack case in particular did not produce anything specific to the Android phone. Maps and location-based suggestions were also judged to be better in the promise than in the delivery.
It is worth keeping this in proportion. The result reflects one reviewer’s experience, on one device and one app version, and it shouldn’t be read as a verdict on the whole feature. It does show why the distance between a help page and everyday use is worth checking.
Getting better results
Anthropic’s own advice is to be specific about the action and to include every relevant detail, such as recipients, dates, times and durations. For alarms, that means stating AM or PM and any repeating days, and for timers it helps to mention what the timer is for so it can be labeled properly. The company also recommends reviewing the content in the destination app before sending or saving it, since Android apps may format text slightly differently than Claude does.
When Claude doesn’t offer to use an app at all, the troubleshooting guidance starts with the basics: updating to the latest version of Claude for Android, restarting the app, and making sure the relevant messaging, email, calendar or clock apps are installed and up to date. Users are also told to confirm that Claude holds the permissions it needs in the phone’s settings, to clear the app’s cache if sharing options fail to appear, and to check that the Clock app is enabled and that Do Not Disturb isn’t blocking alarms.
Why it matters
The feature fits a wider shift in how assistants are built. They are moving from answering questions to carrying out small tasks, and the phone is the most natural place to do it, because calendars, alarms, maps and messages already live there. Android’s intent system makes this possible without handing an AI broad control over the device, and the review step before anything is sent keeps the user in charge.
The early test results are a reminder that capability on paper and capability in daily use are not the same thing. For now, the sensible approach for users is to try the pieces that matter most to them, such as the calendar and alarms, before relying on the rest.
