# AI use cases for Buddy Android (ghorbelhamdi/buddy-android)

Repo: [ghorbelhamdi/buddy-android](https://github.com/ghorbelhamdi/buddy-android) | Use cases: 3 | Page: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/

Buddy is a free Android app with a floating chat bubble that lets Claude Code, Codex or OpenCode read the phone screen and tap, type, scroll and open apps for you, without adb, a PC or root.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Reply to incoming messages from notification rules: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/reply-to-messages-from-notification-rules/
- Control phone apps by voice for everyday chores: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/voice-control-phone-apps-for-chores/
- Give a terminal coding agent control of your phone: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/phone-tools-in-terminal-agent-sessions/

## How to reply to incoming messages from notification rules with Buddy Android

Repo: [ghorbelhamdi/buddy-android](https://github.com/ghorbelhamdi/buddy-android) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Set rules so Buddy answers routine WhatsApp or chat messages, with your approval before each send.

**Who it is for:** A small shop owner or freelancer who gets repeated customer messages on WhatsApp and wants routine answers sent while away from the phone.

**The problem:** Routine questions such as opening hours pile up in notifications while you are busy, and replying by hand is slow.

**The outcome:** Matching messages get a drafted reply that you approve, or that goes out after a countdown you can stop. Replies you do not answer wait in Waiting for you.

### Steps

1. Download buddy.apk from the Releases page and install it, then finish the setup guide including Accessibility and Notification access.
2. Choose Claude Code or Codex in the setup guide and sign in.
3. Open Settings, then Experience, then Notification rules, and create a rule that picks the messaging app and the instruction, for example replying with your opening hours.
4. Pick a smaller model for the rule to keep it quick, and choose either the approval card or a countdown.
5. Send a test message from another account and check that the approval card or countdown appears in Buddy.

### Prompt to paste into your agent

```text
Using the buddy-android repo at https://github.com/ghorbelhamdi/buddy-android, set up one notification rule for <messaging app> that replies with <your opening hours text> and asks for approval first. Expected output: a saved rule on the Notification rules screen and an approval card when a test message arrives. Verify that the rule shows a Recent activity entry after the test message.
```

### Caveat

A notification that Android hides from apps with notification access, such as one containing a one-time code, cannot be read by a rule.

Risk, credentials: The rule sends replies from your messaging account, so check each rule's wording and approval setting before enabling a countdown.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/reply-to-messages-from-notification-rules/

## How to control phone apps by voice for everyday chores with Buddy Android

Repo: [ghorbelhamdi/buddy-android](https://github.com/ghorbelhamdi/buddy-android) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Speak a task such as adding an item to a shopping cart, and let Buddy tap through the app.

**Who it is for:** A person with busy hands or limited mobility who wants to finish app tasks such as shopping, settings changes or smart home controls by speaking.

**The problem:** Many everyday tasks need several taps across apps, which is hard when hands are full or movement is limited.

**The outcome:** You say or type the task, Buddy reads the screen and performs the steps, and it asks you before anything is bought, sent or deleted.

### Steps

1. Install buddy.apk and turn on Buddy assistant under Accessibility in the setup guide.
2. Sign in to Claude Code or Codex, or pick OpenCode and use its free models with no account.
3. Tap New chat, then tap the mic and speak a task, for example adding an item to your Amazon cart.
4. When Buddy shows an Approve, Deny or Change card, check the details before tapping Approve.
5. Open Settings, then Voice, and pick the recognizer you want to use for later tasks.

### Prompt to paste into your agent

```text
Using the buddy-android repo at https://github.com/ghorbelhamdi/buddy-android, ask Buddy in a new chat to <task in one sentence>, and approve only the final step. Expected output: the task completed in the target app with a short summary in the chat. Verify that the approval card showed the exact item and quantity before you approved.
```

### Caveat

Buddy works through the accessibility service, so tasks in apps with unusual screens may need a retry or a clearer instruction.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/voice-control-phone-apps-for-chores/

## How to give a terminal coding agent control of your phone with Buddy Android

Repo: [ghorbelhamdi/buddy-android](https://github.com/ghorbelhamdi/buddy-android) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Use Buddy's local MCP phone tools from Claude Code or Codex running in any terminal.

**Who it is for:** A developer who already works in Claude Code or Codex in a terminal and wants the agent to check or operate the phone as part of a task.

**The problem:** Testing an Android flow or reading what is on screen normally means switching to the phone by hand, which breaks the coding session.

**The outcome:** The terminal agent can read the screen, tap, type, take screenshots and open apps through Buddy's local MCP server, so the phone check happens inside the same session.

### Steps

1. Install Buddy and finish the accessibility setup so the phone tools are running.
2. Confirm the local MCP server is reachable at http://127.0.0.1:8765/mcp on the phone before connecting a session.
3. Add the MCP server at http://127.0.0.1:8765/mcp to your Claude Code or Codex configuration, using that tool's own MCP setup command. (inferred, check the README)
4. Start a session in your terminal and ask the agent to call read_screen to confirm it sees the phone.
5. Ask for one small action, such as opening an app with open_app, and check the result on the phone.

### Prompt to paste into your agent

```text
Using the buddy-android repo at https://github.com/ghorbelhamdi/buddy-android, connect this session to the local MCP server at http://127.0.0.1:8765/mcp and call read_screen, then report the name of the app currently in front. Expected output: a short text description of the visible screen. Verify that the description matches what is on the phone right now.
```

### Caveat

The MCP server runs on the phone, so the terminal session must be able to reach 127.0.0.1 on that device, which the README does not show how to set up.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ghorbelhamdi-buddy-android/phone-tools-in-terminal-agent-sessions/
