FONECLAW AGENT / ANDROID

FoneClaw Agent

Say what you need. Let your phone act.

From a voice request to a completed task. Connect phone tools, daily tasks and plugins, with fewer steps in your day.

Interactive examples use sample data and do not control your device. Capabilities vary by edition, permissions and setup.

↗Voice control
Permission and autonomy controls are explicit

An easier way to get everyday things done.

Start now, schedule for later, reuse a shortcut or add a plugin for a specific need.

FONECLAW AGENT

Voice control

Speak your request. The Agent uses your configured model, available tools and permissions to carry out supported actions.

Try the demo ↗

One runtime connects intent, models, and Android tools

FoneClaw is the phone agent. The selected LLM drives understanding and planning; built-in tools perform supported actions on the phone.

01

Intent

02

Configured LLM

03

Agent plan

04

Built-in tools

05

Android result

One Agent. More everyday possibilities.

Plugins extend FoneClaw Agent for specific needs. They cannot run independently.

Plugin Store ↗

Plugins run inside a compatible FoneClaw Agent edition. Plugins are free unless their product page states otherwise.

From understanding your request to taking action.

Choose an everyday scenario and explore how the Agent handles it.

01 / Daily contextStart with a brief built from your phone.FoneClaw can summarize recent SMS, notifications, and device information into one working view.
Daily Brief ↗
02 / MessagesUnderstand an SMS history without opening every thread.Ask for a time range or contact and get the relevant messages grouped and summarized.
SMS Statistics ↗
03 / Device auditTurn phone status into an actionable report.Check memory, storage, battery, network, app permissions, and sensitive app signals from one request.
Phone Health ↗
04 / Phone controlChange settings and manage connections from intent.Adjust supported system controls or work with nearby Wi-Fi and Bluetooth devices.
Controls ↗Connectivity ↗
05 / Cross-app workMove from information to the next phone action.Summarize configured email, find a destination, and open a supported navigation route.
Email ↗Navigation ↗
06 / Visible contextUse what is on screen as context for the next step.When enabled, a new screenshot or photo can trigger a prompt to summarize the visible content.
Screen Context ↗

Interactive examples use sample data and do not control your device. Capabilities vary by edition, permissions and setup.

Explore all built-in tools

141 public built-in tools

ToolRiskApprovalWhat it does
camera_open_photoScreen and AppSENSITIVE_READRequire approvalOpen a specific visible photo from the system gallery. Use this only when the user explicitly asks to view or open a specific photo. Do not use this as a follow-up after camera(command=take_photo) unless the user explicitly asks to view or open the captured photo. indexFromLatest is 1-based in newest-first order: 1 opens the latest photo, 2 opens the second latest photo, 3 opens the third latest photo.
camera_take_photoScreen and AppSENSITIVE_READRequire approvalCapture a new photo and return it as an image attachment when model vision is available. Use this when the user's intent is to capture a new photo. Leave lensFacing unset or auto for normal photo capture. Choose lensFacing=front only for front-facing or selfie intent; choose back only when the user explicitly asks for the back camera. Keep explicitLensSelection false for plain/default photo capture, even if the default physical lens is back. Set explicitLensSelection true only when the user explicitly asks for front, back, rear, or selfie capture. Do not call camera(command=open_photo) after this tool unless the user explicitly asks to view or open the photo. Call this tool directly. Capture uses the native system camera first. Explicit front/back capture may use the direct backend only if the native camera cannot honor the requested lens. Do not ask the user to grant permission before calling this tool.
cross_app_read_screenScreen and AppLOWAutoOpen or switch to a target Android app and return its latest visible accessibility tree after a bounded stability check. Use this when one request asks to both open/switch to an app and read, inspect, describe, summarize, search, type into, or tap an existing visible control, and no dedicated domain or capture tool can complete the request. GUI prerequisites are checked before opening. Do not split that task into a standalone app launch and a later screen read or screenshot, even across model rounds. A pure app-open request uses the launch tool without reading the screen. This tool does not capture a screenshot, type, or tap nodes itself. Use the returned screen and node IDs for the next requested action. Read again only if required information is missing, the screen is stale, or it changed externally. Tree stability does not guarantee that loading has finished.
get_installed_map_appsScreen and AppLOWAutoQuery installed map apps supported by map tools. Returns each app's display name and package name.
get_screen_infoScreen and AppLOWAutoGet UI elements from the active app and exposed input-method windows. Nodes marked keyboard belong to the input method; use a real keyboard search/submit key with tap when ime_enter is unavailable, including on Android 9/10. An editable field marked focused has input focus; match it to the requested field before a keyboard action. Use input_text for prepared text instead of typing through individual keyboard keys. Each element has a node ID (for example [n3]) that can be used with screen(command=tap), screen(command=scroll), or screen(command=input_text). Do not use this to read, list, search, or summarize Android notifications; use sysinfo tools instead. A node marked ime_enter supports its focused keyboard action. A successful tap, scroll, input_text or ime_enter already returns a fresh screen; use it directly. Read again only if it is stale, changed externally or lacks needed information. Node IDs belong only to the latest returned screen.
input_textScreen and AppDEVICE_CONTROLRequire approvalReplace the text in one visible editable field in the current Android app. Pass a node marked edit from the latest read or action result. This action only enters text; it does not submit the form, tap Send, or press Enter. Use ime_enter separately when a requested submission is supported by the focused field. Returns the action summary and a fresh accessibility tree, without a screenshot. Use the returned screen and node IDs for the next requested action. Read again only if required information is missing, the screen is stale, or it changed externally. This must be the only screen call in this model response.
launch_appScreen and AppDEVICE_CONTROLRequire approvalOpen a launchable Android app by package name or installed app display name. This changes the foreground app and may expose that app's screen. Use this when the requested outcome is only to open the app; stop after success without reading or verifying its screen. For a task that also requires reading, searching, typing, or tapping inside the target app, use the combined app-open-and-read tool instead so GUI prerequisites are checked before opening. Prefer a dedicated domain or capture tool when it can complete the requested outcome. Use an exact package name when possible. If the result is ambiguous, ask the user to choose one returned package.
play_store_check_appScreen and AppLOWAutoCheck whether an exact Android package name is listed on Google Play by requesting https://play.google.com/store/apps/details?id=<packageName>. This is a read-only network check. Use it before app(command=install_store_app).
play_store_installScreen and AppEXTERNAL_EFFECTRequire approvalOpen a specific Google Play app details page by exact package name, tap Install, and wait for installation to complete. This tool does not open the installed app. Use only when an exact Android packageName is known. Never use this for fuzzy search results or to guess the first app. If packageName is unknown, ask the user for the exact app package first. Stops if Google Play shows paid, purchase, subscription, update, ambiguous UI, or if installation does not complete before timeout.
screen_ime_enterScreen and AppEXTERNAL_EFFECTRequire approvalTrigger the keyboard action of a visible, focused editable field marked ime_enter in the latest screen. Requires Android 11 or newer and an editor exposing ACTION_IME_ENTER. This may search, submit a form or send a message depending on that field; use only for the requested submission. Does not change text or inject a newline. Returns the action summary and a fresh accessibility screen; verify the actual result. Never replay an unknown submission. This must be the only screen call in this model response.
screen_run_segmentScreen and AppDEVICE_CONTROLRequire approvalAdvance a local GUI goal with several dependent actions using fresh accessibility screens. Reads the initial screen itself. Specify a clear stop condition, allowed operations and exact prepared input texts. Prefer IME_ENTER when the focused editor exposes it. On older Android or when ime_enter is unavailable, allow TAP to choose an exposed keyboard search/submit key. Prefer atomic Tools for one action. The segment is authorized once; its internal actions are part of that invocation. Returns performed actions and the latest screen for Main to verify or continue; completion is only a suggestion. A local wait or execution limit also returns for Main to review and continue from the confirmed actions. A step gets at most two retries using fresh observations; success resets the retry count. Exhausted retries end only this segment; Main continues with atomic screen Tools for the rest of this turn. Never replay an action with an unknown outcome. Reuse the returned screen instead of immediately reading again. Do not replay completed or unknown actions. This must be the only screen call in this model response.
screenshot_openScreen and AppSENSITIVE_READRequire approvalOpen a specific visible screenshot from the system gallery. index is 1-based in the selected order. sortOrder can be newest or oldest.
screenshot_takeScreen and AppSENSITIVE_READRequire approvalCapture an Android screen with the FoneClaw accessibility service. The captured image is kept in app-private cache for Agent use and is not added to the system Gallery. Use only when the requested outcome includes a screenshot or screen-image analysis. Reading a screen for GUI search, typing, tapping, or confirming results is not an image-capture request; use the accessibility screen-reading tools. A loading page or an uncertain action result does not change that boundary. Use targetType=current for the current screen, targetType=app with targetApp for opening an app and capturing it, or targetType=notification_shade only for an explicit screenshot or image-capture request involving the visible notification shade. Never use targetType=notification_shade to read, list, query, or summarize notification data; use a SysInfo notification tool instead. Never use this tool merely to locate or verify a control, recover a stale GUI node, or compensate for missing accessibility labels during cross-app GUI automation. Do not call app(command=launch) or system_panel(command=open) before this tool for app or notification-shade capture. A successful capture already returns the image attachment for delivery. Do not open the gallery to find or verify it. Do not use this when the user wants to view an already saved screenshot; use screenshot(command=open) for viewing saved screenshots.
scrollScreen and AppLOWAutoScroll the current app by using a compatible accessibility scroll action when supported, otherwise perform a bounded swipe gesture. Prefer a node marked scroll from the latest read or action result. Use viewport only when the screen exposes no usable scroll container. Direction is the viewport destination: down reveals content below, up reveals content above, right reveals content to the right, and left reveals content to the left. Returns the action summary and a fresh accessibility tree, without a screenshot. Use the returned screen and node IDs for the next requested action. Read again only if required information is missing, the screen is stale, or it changed externally. The returned tree does not prove content changed. This must be the only screen call in this model response.
tap_nodeScreen and AppLOWAutoTap a UI element on the screen. The element is identified by its node ID, which can be obtained from the latest read or action result. Returns the action summary and a fresh accessibility tree after a bounded stability check. No screenshot is captured. Use the returned screen and node IDs for the next requested action. Read again only if required information is missing, the screen is stale, or it changed externally. Tree stability does not guarantee that loading has finished. This must be the only screen call in this model response.
alarm_modify_alarmDevice Status and System ControlDEVICE_CONTROLRequire approvalImmediately open the Android Clock alarms page when the user wants to modify, edit, adjust, or change an existing alarm. Call this tool for every separate modification request, even if it was already called earlier in the conversation. Do not ask for confirmation. Android does not provide a reliable public API for editing existing alarms, so this tool only navigates to the Clock app for manual editing.
alarm_set_alarmDevice Status and System ControlDEVICE_CONTROLRequire approvalRequest an alarm in Android Clock. Ask only for missing required time; use defaults for optional settings. No calendar-date parameter is supported.
bluetooth_connected_devicesDevice Status and System ControlSENSITIVE_READRequire approvalReturn Bluetooth devices currently connected through public Android Bluetooth profiles visible to normal apps.
bluetooth_nearby_devicesDevice Status and System ControlSENSITIVE_READRequire approvalScan and return nearby Bluetooth devices. Includes BLE scan results and classic Bluetooth discovery results when permissions and Bluetooth state allow it. Devices without a readable name are hidden by default.
bluetooth_pair_deviceDevice Status and System ControlDEVICE_CONTROLRequire approvalStart pairing with a Bluetooth device by MAC address. This launches Android's normal bonding flow and may require user confirmation or PIN entry.
bluetooth_paired_devicesDevice Status and System ControlSENSITIVE_READRequire approvalReturn Bluetooth devices already paired with this Android device.
bluetooth_stateDevice Status and System ControlLOWAutoReturn the current Bluetooth adapter state: on, off, turning_on, turning_off, or unknown.
close_bluetoothDevice Status and System ControlDEVICE_CONTROLRequire approvalRequest Bluetooth to turn off using the public API where Android permits it. When restricted or rejected, open Bluetooth settings for the user. An opened settings page is not proof that Bluetooth is off.
device_app_activity_snapshotDevice Status and System ControlSENSITIVE_READRequire approvalReturn a compact recent app activity snapshot from Android UsageStats. Requires usage access. If no recent activity is available, return status=skipped so other health checks can continue. It is not a live background-process monitor.
device_app_permission_auditDevice Status and System ControlSENSITIVE_READRequire approvalReturn a compact permission-risk audit for installed apps visible to this app. Risk is heuristic and based on declared/granted sensitive permission groups.
device_app_sensitive_auditDevice Status and System ControlSENSITIVE_READRequire approvalReturn compact sensitive app states: accessibility, notification listener, device admin, overlay, battery optimization exemption, and granted sensitive permission groups.
device_battery_statusDevice Status and System ControlLOWAutoReturn compact Android battery and power-save status. No settings are changed.
device_health_checkDevice Status and System ControlLOWAutoReturn a compact read-only health snapshot: memory, storage, battery, and network. No settings are changed.
device_hidden_app_checkDevice Status and System ControlSENSITIVE_READRequire approvalReturn a compact heuristic check for user apps without launcher entries or disabled components. This can flag suspicious apps, but legitimate service-only apps may appear too.
device_memory_statusDevice Status and System ControlLOWAutoReturn compact Android memory status. No settings are changed.
device_network_statusDevice Status and System ControlLOWAutoReturn compact Android active network status and capabilities. No network settings are changed.
device_storage_statusDevice Status and System ControlLOWAutoReturn compact Android internal/shared storage status. No files are scanned or deleted.
device_time_statusDevice Status and System ControlLOWAutoReturn the current Android system time zone and formatted local date-time for time-dependent tool calls. Set verifyWithNtp=true only when the system time is disputed or an online reference is required. NTP verification uses ntp1.aliyun.com and never changes the system clock.
dnd_open_policy_access_settingsDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android settings where the user can grant FoneClaw Do Not Disturb / Notification Policy access. Do not call this immediately after dnd(command=set_mode) reports that it already opened the settings page.
dnd_set_modeDevice Status and System ControlDEVICE_CONTROLRequire approvalSet Android Do Not Disturb mode. If policy access is missing or Android rejects the write, this opens the system DND policy access/settings page.
dnd_statusDevice Status and System ControlLOWAutoRead Android Do Not Disturb policy access state and current interruption filter.
flashlight_set_enabledDevice Status and System ControlDEVICE_CONTROLRequire approvalTurn the Android flashlight on or off using the system camera torch API.
flashlight_statusDevice Status and System ControlLOWAutoReturn whether the flashlight is available and the last known torch state.
flashlight_toggleDevice Status and System ControlDEVICE_CONTROLRequire approvalToggle the Android flashlight. If the current state is unknown, this turns it on.
foneclaw_permission_statusDevice Status and System ControlLOWAutoCheck all current permissions and special-access capabilities of FoneClaw itself. Use this when the user asks which FoneClaw permissions are enabled, missing, limited, or available. This is a fresh read-only check; do not use app audit, notification-panel, or screen-reading tools as a substitute.
open_bluetoothDevice Status and System ControlDEVICE_CONTROLRequire approvalRequest Bluetooth to turn on. On supported older Android versions, try the public enable API; Android 13 and later restrict this API for apps targeting API 33 or above. When restricted or rejected, open Android's system confirmation UI. A request or prompt is not proof that Bluetooth is on.
system_panel_openDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen one visible Android system panel. Use panel=notifications to open the notification shade, or panel=quick_settings to open quick settings / control center. This tool only opens the selected panel. It does not read, capture, search, list, or summarize panel content. Do not call it when any part of the request asks to read, capture, inspect, describe, or summarize notifications. Call it once only for an explicit panel-open-only request. Requires FoneClaw accessibility service.
system_settings_open_battery_optimization_entryDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android battery optimization settings. If appNameOrPackage is provided, open that app's detail page by package name or installed app label. If it cannot be resolved or opened, return failure and do not open another settings page. If empty, open the system battery optimization list/settings page.
system_settings_open_battery_saver_settingsDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android Battery Saver / power saving / low power mode settings. Normal apps cannot directly toggle Battery Saver through public APIs, so after settings opens the user must enable or disable it manually. Vendor ROMs may fall back to generic battery settings.
system_settings_open_date_time_settingsDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen the Android Date & time settings page directly. Use this for date, time, automatic time, time zone, or automatic time-zone settings. This launches a system settings Intent and does not require accessibility, screen reading, or tapping. After it succeeds, do not call app(command=launch), screen(command=read), or screen(command=tap).
system_settings_open_hotspot_entryDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android hotspot settings. Normal apps cannot reliably toggle hotspot silently through public Android APIs. If the exact hotspot settings page cannot be opened, this returns failure and does not open another settings page.
system_settings_open_location_entryDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android location settings. If appNameOrPackage is provided, open that app's detail page by package name or installed app label. If it cannot be resolved or opened, return failure and do not open another settings page. If empty, open the system Location settings page.
system_settings_set_auto_rotateDevice Status and System ControlDEVICE_CONTROLRequire approvalEnable or disable Android auto rotation. Requires the special modify-system-settings permission.
system_settings_set_brightnessDevice Status and System ControlDEVICE_CONTROLRequire approvalSet Android screen brightness. Manual mode writes percent from 1 to 100; auto mode only enables automatic brightness and ignores percent. Requires the special modify-system-settings permission.
system_settings_set_eye_comfortDevice Status and System ControlDEVICE_CONTROLRequire approvalOpen Android Display settings for Eye comfort/Night Light/blue light filter/reading mode. Use this tool instead of only giving manual instructions for multilingual eye-comfort intents. Android vendors expose the exact switch differently, so this tool opens Display settings and lets the user finish the switch on that page.
system_settings_set_font_scaleDevice Status and System ControlDEVICE_CONTROLRequire approvalSet Android system font scale. Requires the special modify-system-settings permission. Typical values are 0.85 small, 1.0 default, 1.15 large, 1.3 larger, and up to 1.6 extra large.
system_settings_set_haptic_feedbackDevice Status and System ControlDEVICE_CONTROLRequire approvalEnable or disable Android haptic feedback. Requires the special modify-system-settings permission.
system_settings_set_screen_timeoutDevice Status and System ControlDEVICE_CONTROLRequire approvalSet Android screen-off timeout in seconds. Requires the special modify-system-settings permission. Values are clamped to 15..1800 seconds.
system_settings_set_touch_soundsDevice Status and System ControlDEVICE_CONTROLRequire approvalEnable or disable Android touch sounds. Requires the special modify-system-settings permission.
system_settings_set_user_rotationDevice Status and System ControlDEVICE_CONTROLRequire approvalLock Android screen rotation. Requires the special modify-system-settings permission and disables auto rotation. Use portrait, landscape, reverse_portrait, or reverse_landscape.
system_settings_statusDevice Status and System ControlLOWAutoReturn writable system settings permission state plus current screen brightness, font scale, screen timeout, rotation, touch sounds, and haptic feedback. This reads Android system settings only.
volume_adjust_streamDevice Status and System ControlDEVICE_CONTROLRequire approvalRaise or lower one Android audio stream by one system step. Choose this for relative volume changes.
volume_set_all_streams_mutedDevice Status and System ControlDEVICE_CONTROLRequire approvalMute or unmute all supported Android audio streams and report which streams actually changed. Choose this for whole-device or all-volume mute requests.
volume_set_ringer_modeDevice Status and System ControlDEVICE_CONTROLRequire approvalSet Android phone ringer mode. For silent mode, this automatically falls back to muting all audio streams when Android rejects the ringer-mode write.
volume_set_streamDevice Status and System ControlDEVICE_CONTROLRequire approvalSet one Android audio stream to a target percentage. Choose this when the user asks for an exact volume level.
volume_set_stream_mutedDevice Status and System ControlDEVICE_CONTROLRequire approvalMute or unmute one Android audio stream. This changes a stream mute state, not the phone ringer mode.
volume_statusDevice Status and System ControlLOWAutoRead the current Android volume state for audio streams and the current ringer mode.
wifi_configured_networksDevice Status and System ControlSENSITIVE_READRequire approvalRead configured/saved Wi-Fi networks only when Android exposes them. Android 10 and later block this API for normal apps targeting API 29 or above. Returns only SSID, networkId, security type, whether credentials exist, whether the network is hidden, current connection status, and configuration state. Does not return Wi-Fi passwords.
wifi_connectDevice Status and System ControlDEVICE_CONTROLRequire approvalConnect to a Wi-Fi network through legacy APIs only where Android permits them. Android 10 and later block saved-network and password-based changes for apps targeting API 29 or above, so the tool falls back to Android's Wi-Fi panel for user action. Confirm success only after the active SSID is verified.
wifi_disconnectDevice Status and System ControlDEVICE_CONTROLRequire approvalDisconnect from the current Wi-Fi access point. The tool first attempts a silent legacy WifiManager disconnect where Android permits it; if Android rejects it, it falls back to opening Android's Wi-Fi panel for user action.
wifi_forgetDevice Status and System ControlDESTRUCTIVERequire approvalForget a saved Wi-Fi network. The tool first attempts silent legacy WifiManager removeNetwork, then falls back to Android's Wi-Fi panel for user action.
wifi_scan_networksDevice Status and System ControlSENSITIVE_READRequire approvalScan and return nearby Wi-Fi access points. If Wi-Fi is off, try a direct state change only where Android permits it, otherwise open Android's Wi-Fi panel if direct enable fails. Requires location permissions and device location services. Results can reveal location-sensitive network data.
wifi_set_enabledDevice Status and System ControlDEVICE_CONTROLRequire approvalEnable or disable Android Wi-Fi. Where Android permits it, the tool attempts the public operation, then checks whether Android actually reached the requested state; if the request fails or remains pending, it falls back to opening Android's Wi-Fi panel for user action.
wifi_statusDevice Status and System ControlSENSITIVE_READRequire approvalReturn current Android Wi-Fi status and active Wi-Fi connection details when the app has permission. This reads network state only.
get_locationLocation and NavigationSENSITIVE_READRequire approvalGet the current Android device location while FoneClaw is in use. Requires foreground location permission only.
location_search_nearby_placeLocation and NavigationSENSITIVE_READRequire approvalSearch nearby place candidates for an ambiguous place name using the current device location. Use this only when the user explicitly asks to find, verify, resolve, choose, or navigate to a place, or when a navigation destination is ambiguous. For calendar creation, a user-provided place name is sufficient: preserve it as locationName and do not call this tool solely because an exact address or coordinates are missing.
map_navigateLocation and NavigationEXTERNAL_EFFECTRequire approvalOpen a route or navigation screen in a map app for a destination and travel mode. This launches an external map app, uses only the provided arguments, and does not read device data.
travel_plan_append_daysLocation and NavigationDEVICE_CONTROLRequire approvalAppend new consecutive days after a saved trip's last date and archive the prior version. Preserves all existing days, trip information, preparation and packing. Use update instead if the user also changes any of those fields. Read the plan first; use its current revision. Continue from its last endpoint and accommodation, group nearby visits and order regions to avoid unnecessary backtracking across days. Respect fixed appointments and user-specified order; leave realistic transfer and rest time without claiming live routing or inventing precise travel times. Do not repeat existing visits unless requested or necessary. On revision conflict read again; never overwrite concurrent edits. Does not create calendar events or todos.
travel_plan_createLocation and NavigationDEVICE_CONTROLRequire approvalSave one complete new travel plan requested by the user. Supply the exact new plan id from the host context when provided, otherwise a stable explicit plan id, revision 0, destination, timezone, selected days, activities, preparation and packing. Plugin ownership is bound by the host's current turn context; templateId in model JSON cannot change it. Before creating a travel plan, collect the destination or ordered city route, the start and end dates for each city, the departure point, and a valid departure time in HH:mm. Use only information supplied by the user or explicitly accepted by the user. Ask for missing required information and do not create or claim to save a plan until it is complete. Do not invent missing fields from another saved trip, current location, or a default departure time. Before creating, also ask once about optional visit preferences, travel pace, number of travelers, total trip budget and currency, and other requirements such as accessibility or dietary needs. Use any details already provided; do not ask the same answered question again. Tell the user these details are optional and may be skipped, and proceed after their answer or explicit request to skip. Leave skipped information unknown rather than inventing it. Include travelers and total budget when supplied. Never substitute a fixed sample itinerary. Retrying the same exact content with the same plan id returns the existing plan; different content for an existing id is rejected, never overwritten. This does not create calendar events, todos, bookings, shared membership or photos.
travel_plan_readLocation and NavigationSENSITIVE_READRequire approvalRead a private saved travel plan and its current revision before modifying or extending it. Does not change anything.
travel_plan_updateLocation and NavigationDEVICE_CONTROLRequire approvalUpdate a saved travel plan after reading its latest JSON. Save trip information in its plan fields, not only in activity notes or the reply. For targeted edits use changeScope=EDIT and send only changed fields, including stopEdits keyed by the exact existing stop ids. Successful targeted edits return a receipt with planId, revision and currentVersion. To replace days or replan use a complete TravelPlan JSON with matching id and revision; preserve existing stop and checklist ids and generate ids only for new items. The host archives a version only when the daily itinerary actually changes; updates to shared trip information, preparation and packing still save. Use changeScope=REPLAN only for a requested overall itinerary replan. On revision conflict read again and merge into the latest plan. Only claim the plan was updated after this tool succeeds. Does not create calendar events or todos.
mail_account_listMailLOWAutoList configured mail accounts. Leave query empty to list all accounts. When query is provided, matching priority is account id, email, alias, then fuzzy alias or email. Exact matches can still return multiple accounts. If an exact email query has no configured match, the result may include providerSetupGuide with a fixed provider credential URL. For Gmail addresses, providerSetupGuide.accountConfigPreset contains the complete non-secret IMAP, SMTP, and username fields to carry unchanged into mail_account(command=save); ask the user only for the remaining app password. No server preset is returned for other domains.
mail_account_saveMailDEVICE_CONTROLRequire approvalTest both the receiving server (IMAP or POP3) and SMTP, and save only when both succeed. Call this as soon as every required configuration field is available. This operation requires user approval.
mail_deleteMailDESTRUCTIVERequire approvalMove up to 20 exact messageRefs to trash, or permanently delete them only when the user explicitly requested permanent deletion. Never retry an uncertain result.
mail_listMailLOWAutoList, filter, or search message summaries. Query searches subject, sender, recipients, and body. Use folder ALL once when the user requests both received and sent mail or does not limit direction; use INBOX or SENT only for an explicit single direction. Never guess provider-specific folder names or retry a completed query. If a constrained query fails, report the failure without clearing or changing its query, sender, or time filters to manufacture a broader result. Each result includes a preview of up to 500 characters for list and batch summaries; do not read every full message after a completed list query. Do not follow nextCursor again in the same run; report that more results are available and let a later user request continue the query. Call this Tool again for every new list, search, filter, date-range, summary, or reformat request even when conversation history contains earlier mail results. Historical messageRefs may be reused only for an operation on an exact already-selected message. Leave accountId empty to use the only account or the unique default account. POP3 exposes only INBOX, cannot filter read status, and uses server message sequence for NEWEST_FIRST/OLDEST_FIRST rather than a guaranteed date order. POP3 date filters use the sender's Date header; isRead is null when read status is unsupported.
mail_readMailSENSITIVE_READRequire approvalRead one message from a messageRef returned by mail(command=list). IMAP marks it read; Gmail and POP3 remain read-only. Use this only when the user explicitly needs the full body, attachment metadata, or exact details absent from the mail(command=list) preview; do not use it for every message merely to produce a list or batch summary. Never repeat the same messageRef and bodyCursor. After the tool succeeds, summarize the message for the user in the same response.
mail_sendMailEXTERNAL_EFFECTRequire approvalSend a new email, reply, reply all, or forward. Requires approval. Attachments must use the exact structured metadata announced with the current user message.
call_log_listCommunication and ContactsSENSITIVE_READRequire approvalList recent Android call log entries, optionally filtered by call type. Requires READ_CALL_LOG permission. Use type=missed for missed-call questions and before selecting a missed call to call back. After selecting a number, call phone(command=dial).
contacts_createCommunication and ContactsEXTERNAL_EFFECTRequire approvalCreate one device-local Android contact directly through the Contacts Provider without opening the Contacts app. Requires READ_CONTACTS and WRITE_CONTACTS permissions. Set displayName and at least one of phoneNumber or emailAddress. If an exact phone number or email address already exists, do not create a duplicate.
contacts_listCommunication and ContactsSENSITIVE_READRequire approvalList a limited number of Android contacts, optionally filtered by display name or phone number. Requires READ_CONTACTS permission. Leave query empty only when the user explicitly asks to view contacts; set query when the user asks to find a contact.
phone_dialCommunication and ContactsEXTERNAL_EFFECTRequire approvalOpen the system dialer for exactly one phone number or named contact. Set exactly one of phoneNumber and contactName. A named contact must resolve to one match; if multiple contacts match, stop and ask the user to choose. This operation only prefills the dialer. For a dialer-open-only request, stop there. Only if the user asked to place the call, continue with available screen operations to identify and tap the visible Call button. Do not claim the call connected from a dialer-open or tap result alone.
send_to_sms_messageCommunication and ContactsEXTERNAL_EFFECTRequire approvalAfter approval, open a visible SMS/MMS draft. For a text SMS with a recipient, automatically tap Send only when FoneClaw accessibility is connected and the default message app, recipient, full message body, and one stable Send control are all verified. Attachments, dual-SIM prompts, ambiguous UI, or unavailable accessibility require manual action. After any terminal result, stop tool planning and never call screen(command=read) or screen(command=tap).
sms_listCommunication and ContactsSENSITIVE_READRequire approvalQuery live SMS messages on this Android device. With no keyword, address, contact, or threadId, list recent messages. Set keyword/address/contact to search. Set threadId only from an earlier sms(command=list) result to read that conversation. For a summary request, call once with box=all and includeBody=true, then summarize only the returned received and sent messages. Use returnedBreakdown for counts and keep its byAddress rows separate. Never use SysInfo history as a replacement for this live result.
calendar_create_eventCalendarEXTERNAL_EFFECTRequire approvalCreate an Android calendar event. Both start and end are required. If no end time or duration can be determined from the request, ask for it; never invent a duration. Optional reminders default to 30 minutes. For an all-day event, set allDay=true and use local midnight for the start and the exclusive next-day local midnight for the end. A user-provided place name is sufficient and should be passed directly as locationName. Do not search for an exact address or coordinates unless the user explicitly asks to verify, resolve, choose, or navigate to the place. Use startLocalDateTime/endLocalDateTime in yyyy-MM-dd HH:mm[:ss] for user dates and relative dates; the tool will parse them in the device timezone. Do not create events from model-calculated epoch milliseconds. Use calendarId=0 unless the user explicitly selected a calendar id. After creation, use the tool result actualStart/actualEnd as the user-facing created time.
calendar_delete_eventCalendarDESTRUCTIVERequire approvalDelete one Android calendar event using an exact eventId from calendar(command=list_events) or calendar(command=search_events). Identify the target by its returned title, time and location; ask the user to choose if ambiguous. Pass only eventId to this operation.
calendar_list_calendarsCalendarSENSITIVE_READRequire approvalList writable Android calendars. Use this to let the user choose a calendar; do not assume that calendarId=1 is the local or target calendar.
calendar_list_eventsCalendarSENSITIVE_READRequire approvalList Android calendar events in a concrete time range. Use for requests like today's schedule, tomorrow's schedule, existing events, or this week's events. Use startLocalDateTime/endLocalDateTime in yyyy-MM-dd HH:mm[:ss]; the tool will parse them in the device timezone. Do not guess calendarId; use calendarId=0 to search all calendars unless the user explicitly selected a calendar id.
calendar_open_eventCalendarSENSITIVE_READRequire approvalOpen an Android calendar event detail page by event id. Search or list events first when the user describes an event in natural language. Do not guess event id.
calendar_search_eventsCalendarSENSITIVE_READRequire approvalSearch Android calendar events by keyword in a concrete time range. Use before opening, updating, or deleting an event when the user describes the event by title or content. Use startLocalDateTime/endLocalDateTime in yyyy-MM-dd HH:mm[:ss]; the tool will parse them in the device timezone. Do not guess calendarId; use calendarId=0 to search all calendars unless the user explicitly selected a calendar id.
calendar_update_eventCalendarEXTERNAL_EFFECTRequire approvalUpdate an Android calendar event by id. Search/list events first when the user describes the target in natural language, and pass known target details with the changed fields. Do not guess calendarId or event id; search all calendars with calendarId=0 unless the user explicitly selected a calendar id. Blank text fields are ignored. Use blank startLocalDateTime/endLocalDateTime to keep existing times. Use yyyy-MM-dd HH:mm[:ss] for changed times. Use reminderMinutes=-2 to keep reminders, -1 to remove reminders, and >=0 to replace reminders.
memo_createMemoDEVICE_CONTROLRequire approvalAdd a user-visible to-do to To-do Center. Use for add a to-do, record a to-do, 添加待办, or 记录待办, including an actionable reminder the user wants kept. Store user content, not assistant profile memory or Main's internal execution plan. Resolve to-do dates directly from the runtime environment without calling Calendar or Alarm Tools. To-do scheduling: Schedule a to-do only when the user's request or explicitly referenced source gives a definite calendar date, a uniquely resolvable relative date (today, tomorrow, the day after tomorrow, in exactly two days / 两天后), or an explicit date range. The runtime-provided original request time and timezone are only a calculation base, never a user-supplied schedule. If no date is mentioned, or timing is vague (这两天, 这个两天, 过几天, 近期, 有空, 改天, soon, sometime this week, in a couple of days), create an undated to-do in Unscheduled with both startDate and endDate omitted or empty. Never default to today, pick a convenient day, or turn a vague window into a multi-day scheduled event. Preserve vague timing in the to-do content. When the content is known, do not ask for a date just to create the to-do. Resolve definite dates from the original request time and timezone supplied by runtime; an unknown hour does not make an explicit day undated. For updates, keep existing dates when the user only changes content and gives no scheduling intent. If the user explicitly removes the schedule, says time undecided, or replaces it with vague timing, use clearStartDate=true with empty date strings to move it to Unscheduled and clear both dates. Report the saved Unscheduled section or scheduled date from the Tool result, not from assumptions. The internal task_pool result marker identifies the undated section; express that section in the response language without echoing the marker or adding a translation in another language. These rules apply to to-dos, not calendar events or alarms.
memo_deleteMemoDESTRUCTIVERequire approvalSoft-delete a user to-do in To-do Center by id. Search/list to-dos first when the user describes the target in natural language so its id/title is known. Do not delete assistant profile memory or Main's internal execution plan with this tool.
memo_listMemoSENSITIVE_READRequire approvalShow the user's to-do list in To-do Center. Use for 待办列表 requests. status can be active, done, archived, or all. This queries personal to-dos, not Main's internal execution plan or assistant profile memory. An empty result applies only to this to-do list.
memo_mark_doneMemoDEVICE_CONTROLRequire approvalComplete a user to-do (完成待办) or reopen it in To-do Center by id. This changes a user record, not Main's internal execution plan or assistant profile memory.
memo_searchMemoSENSITIVE_READRequire approvalFind user to-dos in To-do Center by keyword in title, content, or tags. status can be active, done, archived, or all. Search only user to-dos, not assistant profile memory, conversation history, or Main's internal execution plan.
memo_updateMemoDEVICE_CONTROLRequire approvalEdit a user to-do in To-do Center by id. Search/list to-dos first when the user describes the target in natural language, and pass known target details with changed fields. This edits user to-dos, not assistant profile memory or Main's internal execution plan. Blank title/content/tags and date strings keep existing values. Use yyyy-MM-dd dates resolved from the original request time and timezone supplied by runtime; never calculate epoch milliseconds or call Calendar or Alarm Tools only to resolve a to-do date. To-do scheduling: Schedule a to-do only when the user's request or explicitly referenced source gives a definite calendar date, a uniquely resolvable relative date (today, tomorrow, the day after tomorrow, in exactly two days / 两天后), or an explicit date range. The runtime-provided original request time and timezone are only a calculation base, never a user-supplied schedule. If no date is mentioned, or timing is vague (这两天, 这个两天, 过几天, 近期, 有空, 改天, soon, sometime this week, in a couple of days), create an undated to-do in Unscheduled with both startDate and endDate omitted or empty. Never default to today, pick a convenient day, or turn a vague window into a multi-day scheduled event. Preserve vague timing in the to-do content. When the content is known, do not ask for a date just to create the to-do. Resolve definite dates from the original request time and timezone supplied by runtime; an unknown hour does not make an explicit day undated. For updates, keep existing dates when the user only changes content and gives no scheduling intent. If the user explicitly removes the schedule, says time undecided, or replaces it with vague timing, use clearStartDate=true with empty date strings to move it to Unscheduled and clear both dates. Report the saved Unscheduled section or scheduled date from the Tool result, not from assumptions. The internal task_pool result marker identifies the undated section; express that section in the response language without echoing the marker or adding a translation in another language. These rules apply to to-dos, not calendar events or alarms.
voice_memo_readMemoSENSITIVE_READRequire approvalRead the latest saved recording or collection, editable content and opaque revision before modifying it. The result contains source recording ids, indexed sentences, speaker ids, indexed chapters, key-point indexes and action ids. Their times, identities, source citations and todo associations are read-only. Collection summary belongs to the collection; source transcripts and chapters are shared with the original recording and other collections.
voice_memo_updateMemoDEVICE_CONTROLRequire approvalSave requested edits to a recording or collection after voice_memo(command=read). Pass its exact opaque revision. On conflict read again and merge only the user's changes; never overwrite concurrent edits. Omitted fields stay unchanged. Summary keyPoints/actionItems/navigationPlaces lists, when provided, replace that list: include existing key-point indexes and action ids to retain their sources and todo links; omit index/id only for new items. Source sentences, speakers and chapters are partial edits by their exact indexes/ids. Keep sentence/chapter times unchanged. Do not pass audio, state, source membership, todo ids or association fields. Collection source edits also update original recordings and any other collections sharing them. A collection summary is independent. Only claim saved after success. A request to preview a rewrite does not authorize saving.
sysinfo_deleteSystem InformationDESTRUCTIVERequire approvalPermanently delete matching FoneClaw local SysInfo cache only. This never deletes original Android notifications, SMS, mail, call logs, or calendar events. At least one filter is required unless deleteAll=true. Multiple filters are combined with AND.
sysinfo_mark_reviewedSystem InformationDEVICE_CONTROLRequire approvalMark local SysInfo event ids as reviewed only after the user explicitly confirms.
sysinfo_querySystem InformationSENSITIVE_READRequire approvalQuery already-captured local notifications, SMS, mail summaries, call logs, calendar events, and accessibility input by source, time window, or keyword. Collection coverage may be incomplete and captured records may be stale; they do not establish current live state. It never opens a system panel or scans live system sources. Each row may include sourceRef for deduplication against a live provider result. Summarize the returned JSON for the user.
sysinfo_threadSystem InformationSENSITIVE_READRequire approvalLoad one local SysInfo thread by a threadKey returned by sysinfo(command=query).
purchase_queryWeb and ShoppingLOWAutoRead real account points or current plan prices ONLY when the user asks about usage, balance, pricing or upgrading. Never invent prices, recovery dates or purchase links. Expiry is not a promised refill date. This does not buy anything or resume tasks.
purchase_recommendationsWeb and ShoppingLOWAutoChange proactive long-task and cancellation purchase recommendations ONLY after the user explicitly asks to stop or resume recommendations. Never infer consent.
shopping_compareWeb and ShoppingLOWAutoSearch public web results on Shopee Taiwan (shopee.tw) and momo (momo.com.tw) and return read-only product comparison evidence. Region is a search hint, not a country-site selector. Extracted prices are candidates, not confirmed checkout prices, stock, shipping or coupons. Use this before giving shopping price advice.
web_fetchWeb and ShoppingLOWAutoFetch one HTTP/HTTPS page by URL and return readable text up to maxChars. This is a read-only HTTP fetch, not an interactive browser or JavaScript renderer; empty or truncated text does not establish that the full page was read.
web_searchWeb and ShoppingLOWAutoSearch the web for relevant pages. Returns result titles, exact source URLs, and short snippets, and search-provider dates when available. Dates are source metadata, not independently verified publication times. Preserve date-only precision: its time and timezone are unavailable, so do not invent hours, minutes, or midnight. Missing dates remain unknown. Use sufficient search evidence directly; fetch only to resolve a material gap in the requested answer. Preserve the exact URL after each result summarized in the final answer.
scheduled_task_createTasks, Workflows, and ShortcutsEXTERNAL_EFFECTRequire approvalCreate a local time-triggered automation, managed in the Automations sidebar page. The automation runs unattended on this device around the given local time; Android may delay execution. Results are delivered as system notifications. Only read-only web research is allowed during unattended runs. There is no target-date parameter: once means the next occurrence of hour/minute after creation, not an arbitrary future date. Do not claim a date embedded in prompt changes the schedule. Returns the created task id.
scheduled_task_deleteTasks, Workflows, and ShortcutsDESTRUCTIVERequire approvalPermanently delete a local automation by id and cancel its triggers.
scheduled_task_listTasks, Workflows, and ShortcutsLOWAutoList the user's local automations (time-triggered scheduled tasks). Use the product name Automations when guiding users to the sidebar. Returns each task id, title, local trigger time, repeat rule, and enabled state. Read-only.
scheduled_task_run_nowTasks, Workflows, and ShortcutsDEVICE_CONTROLRequire approvalQueue an immediate manual run of an existing automation. This confirms enqueueing, not completion. A pending manual run is coalesced by the scheduler. A later manual run can execute again and is separate from the scheduled occurrence; do not promise once-per-day execution.
scheduled_task_set_enabledTasks, Workflows, and ShortcutsDEVICE_CONTROLRequire approvalEnable or disable a local automation by id. Disabling cancels future system triggers but keeps the task and its run history.
scheduled_task_updateTasks, Workflows, and ShortcutsEXTERNAL_EFFECTRequire approvalUpdate the instruction for future runs of an existing automation. First use scheduled_task(command=list) to identify the existing task and preserve unrelated instructions. Does not create a task or run it now. Preserves title, schedule and enabled state. Ask which task if the target is ambiguous.
shortcut_save_agent_promptTasks, Workflows, and ShortcutsDEVICE_CONTROLRequire approvalSave a user-created shortcut that sends a prompt to the agent when launched; saving does not execute it. Only call this after the user confirms the title, description, and behavior.
shortcut_save_direct_toolTasks, Workflows, and ShortcutsDEVICE_CONTROLRequire approvalSave a user-created direct tool shortcut. Only call this when every requested action can be fully mapped to known atomic tool steps with complete parameters. Saving does not execute the steps. Use each atomic operation's fixed contract, not the Main domain command wrapper. Parameters are literal saved values with no execution-time expressions; never freeze a rolling date range into fixed dates.
task_createTasks, Workflows, and ShortcutsLOWAutoCreate or append progress items for this request. Plan complex or multi-stage work preferably before execution; simple work can execute directly. Later calls append new IDs while preserving existing items. Avoid unnecessary duplicate steps. Never include task management, cleanup, status-update, or final-response items. This internal execution plan is not the user's persistent To-do Center. For personal to-do creation, lookup, completion, or deletion, use the memo Tool instead.
task_listTasks, Workflows, and ShortcutsLOWAutoList internal TODO items for the current user request. By default returns open, in_progress, and blocked items. This internal execution plan is not the user's persistent To-do Center. For personal to-do creation, lookup, completion, or deletion, use the memo Tool instead.
task_updateTasks, Workflows, and ShortcutsLOWAutoUpdate a task from actual evidence. Start work with in_progress and mark done after verification; already verified work may move directly from open to done. Any nonterminal state can move to any of the five statuses. Done and abandoned are terminal; repeating the current status is a no-op. Prefer one in_progress item when practical. Task status never authorizes additional actions. This internal execution plan is not the user's persistent To-do Center. For personal to-do creation, lookup, completion, or deletion, use the memo Tool instead.
workflow_deleteTasks, Workflows, and ShortcutsDESTRUCTIVERequire approvalDelete a saved workflow definition by its exact id. This does not undo actions already executed by that workflow.
workflow_listTasks, Workflows, and ShortcutsSENSITIVE_READRequire approvalList saved workflows.
workflow_saveTasks, Workflows, and ShortcutsDEVICE_CONTROLRequire approvalSave a reusable workflow definition; this does not execute or schedule it. stepsJson must be a non-empty JSON array string of {toolName, arguments}. Supported atomic toolName values: mail_list, mail_read, mail_send, mail_delete, mail_account_list. Use each atomic operation's exact business parameters without a domain command wrapper. Saved arguments are literals, not expressions recalculated at execution time.
accept_skill_proposalSkills and PluginsDEVICE_CONTROLRequire approvalAccept and apply one pending Skill proposal after user confirmation.
add_skillSkills and PluginsDEVICE_CONTROLRequire approvalCreate or replace a user Skill with this exact id after validation and enable it. For untrusted imports, use preview_import and save_draft.
disable_skillSkills and PluginsDEVICE_CONTROLRequire approvalDisable a user Skill for future discovery. Content already read remains in the current conversation.
enable_skillSkills and PluginsDEVICE_CONTROLRequire approvalEnable a valid user Skill for discovery.
list_skill_proposalsSkills and PluginsSENSITIVE_READRequire approvalList pending Skill changes that require explicit user confirmation.
list_skillsSkills and PluginsSENSITIVE_READRequire approvalList user and system Skills with source, enabled state, and validation state.
load_skill_detailSkills and PluginsSENSITIVE_READRequire approvalRead the full text of a relevant Skill using its exact full id from the available catalog. Returns document text only; referenced resources and scripts are not loaded.
plugin_request_installSkills and PluginsEXTERNAL_EFFECTRequire approvalCreate a structured install proposal for one official plugin. This does not download or install the plugin; the host handles the install proposal and user confirmation. Do not claim installation or use a newly installed capability in this frozen run.
plugin_searchSkills and PluginsLOWAutoSearch official FoneClaw plugin metadata when a user asks for a capability that is not available in the current tool list. This only searches metadata and never downloads or installs a plugin.
preview_skill_importSkills and PluginsLOWAutoPreview a pasted SKILL.md document. This parses and validates but does not save.
reject_skill_proposalSkills and PluginsDESTRUCTIVERequire approvalReject and remove one pending Skill proposal after user confirmation.
remove_skillSkills and PluginsDESTRUCTIVERequire approvalRemove the user Skill with this exact id.
rollback_skillSkills and PluginsDEVICE_CONTROLRequire approvalRestore a user Skill to its most recently archived content revision. Requires that the user Skill and an archived revision exist.
save_skill_draftSkills and PluginsDEVICE_CONTROLRequire approvalSave a SKILL.md document as a disabled user Skill draft.
update_skillSkills and PluginsDEVICE_CONTROLRequire approvalUpdate an existing user Skill while preserving its enabled state.

Choose what drives the agent

You do not need your own API. Model configuration changes the reasoning engine; FoneClaw remains the Android agent that executes the phone task.

Settings ↗
Use the free FoneClaw default model

Start immediately without supplying your own API credentials.

Connect a mainstream online model

Add an OpenAI-compatible model with an API Base URL and API Key.

Import an on-device model

Use the in-app Hugging Face import path for a compatible local model.

Permissions requested on demand

FoneClaw prompts for the specific Android permission only when the requested task needs it.

Configurable tool approval

Choose Auto approve, Follow tool policy, or Deny all to match how much autonomy you want.

Local management controls

Review memory, third-party account information, agent data collection, image detection, and permissions from Settings.

Choose your edition with clarity.

APK

FoneClaw Full

Full is the direct APK edition. Screen actions and plugin installation require the relevant permissions and setup.

GOOGLE PLAY

FoneClaw Lite

Lite is the Google Play edition. It does not use Accessibility Service, read SMS or call logs, or install APK plugins.

Plugins extend FoneClaw Agent for specific needs. They cannot run independently.

Frequently asked questions

What can FoneClaw control on Android?

The public GitHub catalog includes 100+ built-in tools for device checks, SMS, calls, system settings, Wi-Fi and Bluetooth, screenshots, email, calendar, maps, web tasks, Workflows, and Skills.

Does FoneClaw ask for every permission during installation?

No. When a task needs a permission, FoneClaw prompts for that specific access and guides you to enable it. You can review permissions later in Settings.

Can FoneClaw send SMS or email automatically?

FoneClaw can prepare and execute supported communication actions. Whether a tool asks for approval depends on your selected Tool Approval Mode and the applicable tool policy.

Does every feature work without setup?

No. Email needs IMAP/SMTP setup, maps need an installed map app, image auto-summary needs the relevant detection and overlay permissions, and some Android settings require additional system permissions. Core features like phone status, SMS summary, and system settings work out of the box.

Do I need my own model API?

No. You can use the free FoneClaw default model. You can also configure a mainstream online model with an API Base URL and API Key, or import a compatible on-device model.

Say what you need. Let your phone act.

Explore the app, one interaction at a time.

Try the demo ↗
Try FoneClaw