Remote Control from Your Phone: Let Your Company Computer Work While You Commute
💡 One-sentence summary: Use WorkBuddy Remote Control to set up a "remote control console" between your phone and your company computer—check status, continue conversations to dispatch work, stop with one tap, and receive output.
Searching for "WorkBuddy Remote Control" mostly turns up two kinds of results: configuration tutorials that teach you to plug WorkBuddy into WeChat or WeCom chat windows, and generic software articles on "how to use remote desktop." The former can only send messages—you can't see how far a task has gotten; the latter puts your entire computer screen onto your phone, and the connection drops as soon as the subway network stutters. This lesson takes a third path: use the WorkBuddy built-in App and mini program to turn your phone into a "remote control console" for the desktop Agent—start tasks at your workstation, then check status, continue conversations, call things off, and receive output during your commute.
First, let's be clear about the factual boundaries: the connection steps, switch names, status and notification rules, and credit accounting on this page come from the official App and mini program documentation "Multi-Device Collaboration (Connect Computer)"; the two scenario instructions for finding files while commuting and troubleshooting errors remotely, plus three points of caution, come from the official practice case "Practice Six: Remotely Control WorkBuddy"; the "local first, then remote" recommendation comes from item 4 of the official getting-started tips. The App and mini program are largely identical in features; the few differences on this page—notification mechanisms, the new-conversation entry point, and output export—are noted separately.
The previous lesson, C1 WeCom Remote, solved "dispatching work from a chat tool"—the WeCom bot receives a message and forwards it to the computer for execution; this lesson solves "remote control from the phone in your pocket": not a chat window, but task-level takeover. The two paths each have their own role; for an overview of the six chat channels, see 5.1 Assistant Overview. This is lesson 2 of Route Three in "Scenario Practice," based on WorkBuddy v5.9.3.
- How many credits do remote tasks consume: 2.6 Credits and Pricing
- How to choose among the six chat channels: 5.1 Assistant Overview
What You'll Be Able to Do After This Lesson
- Control your computer from your phone: connect once and it persists—no need to pair every time
- Do three things during your commute: check the two-layer task status, dispatch tasks remotely (continue conversations to add instructions), and stop off-track tasks with one tap
- Use the official scenario instructions to find files and troubleshoot errors remotely (the original text can be copied directly)
- Computer output is automatically sent back to your phone: preview, save, and share; the App can also export to PDF / DOCX / Markdown
- Understand the credit rules for remote use: viewing and continuing conversations on your phone costs no extra credits; execution on the computer is the same as desktop operation
Why Use WorkBuddy Instead of a Web-Based AI?
| Capability | Web-Based AI | WorkBuddy Remote Control |
|---|---|---|
| Can reach your company computer | ❌ Conversations happen in the cloud and can't touch the files and tasks on your computer | ✅ Phone connects to computer; instructions are executed by the desktop WorkBuddy (official multi-device collaboration) |
| Task progress | ❌ Close the webpage and you're cut off; how far it's gotten is anyone's guess | ✅ Device-level + conversation-level two-layer status indicators—one glance tells you |
| Proactive notifications | ❌ Without opening the webpage, you know nothing | ✅ Four event types—task completed, interrupted, awaiting an answer, awaiting approval—are pushed to your phone (official documentation) |
| Emergency stop | ❌ Nothing is executing, so there's nothing to stop | ✅ One-tap remote stop, terminated in sync on the computer (official documentation) |
| Getting output back | ❌ Copy and paste, then transfer it back to your computer yourself | ✅ Output is automatically sent back to your phone; the App can export to PDF / DOCX / Markdown (official documentation) |
Your Current Predicament
- A long task is running on your computer while you're already on the subway: How far along is it? Does it need more instructions? Is it stuck? You have no idea
- In a meeting, the boss suddenly asks for a document that's on your workstation computer—you can only stew helplessly or make a trip back
- Asking a colleague to operate your computer means handing over your account and files; half an hour of instructions isn't worth it compared to going yourself
- You installed remote desktop software, but the connection drops whenever the subway network stutters, and finding buttons on the small screen means zooming in on everything
When to Use This Technique
When you need to:
- You're commuting, in a meeting, or out and about, the WorkBuddy task on your computer is still running, and you want to take over anytime (a scenario named in the official documentation)
- To temporarily send PPTs, documents, and other files from your computer to your phone or another device (an official practice case scenario)
- To keep pushing forward on debugging, fixes, or document organization while away from your workstation (an official practice case scenario)
And you don't want to:
- To run back to your workstation just to glance at task progress
- To hand your computer account over to someone else to operate on your behalf
- To operate your entire computer desktop on a small phone screen
🎒 Preparation Before You Start
- Completed C1 WeCom Remote, or read 5.1 Assistant Overview—knowing that "dispatching work via chat channels" and the "task-level remote control" in this lesson are two different paths
- The desktop WorkBuddy client is installed and signed in on your computer (macOS / Windows)
- Your phone is ready to install the WorkBuddy App (or use the mini program), signed in to the same account as the computer
- Both the computer and phone are online; the company computer stays powered on—the physical prerequisite for the remote route
- 15 minutes
Follow Along
Step 1: On the computer, turn on the "Allow mobile devices to connect to this device" switch
Why: Whether your phone can connect to this computer is decided on the computer side. If this switch is off, you can't connect even when you want to on the subway—you'd have to run back to your desk.
How to: In the WorkBuddy desktop app, hover the mouse over the "Connect Mobile" icon at the bottom of the sidebar. In the "Connect Mobile" panel that pops up, turn on the "Allow mobile devices to connect to this device" switch.
You should see: The panel expands, showing QR codes on two tabs, "App" and "Mini Program", plus two switches: "Allow mobile devices to connect to this device" and "Keep awake for remote access".
- The "Allow mobile devices to connect to this device" switch is now on
Step 2: Enable "Allow running while locked" so a locked screen can't block remote control
Why: Company computers usually auto-lock after a few minutes of inactivity. Without keep-awake, the computer "sleeps like the dead" once you step away—your phone may connect but can't wake it or control it.
How to: In the connection panel from the previous step, turn on "Keep awake for remote access"; you can also set it under System Settings → General → Allow running while locked. Choose between the two run modes as needed:
| Run mode | Effect |
|---|---|
| Keep awake after screen off (recommended) | Screen turns off normally; background tasks and remote control proceed as usual, more power-efficient |
| Keep screen always on | Screen never turns off, tasks can be checked at any time, more power-hungry |
You should see: The setting stays on the run mode you selected.
⚠️ Take a quick look before leaving your desk
Official usage advice: Before leaving your desk, confirm that both "Allow mobile devices to connect to this device" and "Keep awake for remote access" are turned on, to avoid being unable to connect after going out.
Step 3: Scan the QR code with your phone to establish the connection, and sign in to the same account
Why: Pairing doesn't rely on the QR code itself—scanning it just guides you to open or download the App / Mini Program; the actual device relationship is established through signing in to the same account.
How to:
- In the connection panel, select the "App" tab (choose the "Mini Program" tab if you want the Mini Program), scan the QR code to open or download the WorkBuddy App
- Sign in with the same account as the desktop app and go to the home page
- Tap the device entry at the top of the sidebar, and in the "Select device" panel choose the computer you want to connect to
You should see: After connecting, a green "Online" badge appears next to the device name; the device name shown on your phone matches the one set in the computer's system (the name under "About This Mac / About"). Once pairing is complete, the device relationship is persistently retained—no need to pair again each time. From then on, opening the mobile app lets you directly check the task status of the connected computer.
⚠️ The WeChat account must match
The official App documentation states clearly: the WeChat account signed in to the App must be the same as the one signed in on the computer, otherwise connecting to the computer won't work.
- You can see the target computer's green "Online" badge on your phone
Step 4: Tasks keep running after you leave; your phone remotely tracks task status
Why: The worst part of remote work is waiting blindly. Multi-device collaboration provides two layers of status: whether the device is there and how far the task has gotten—one glance tells you.
How to: Before leaving your desk, start a long task on the computer (such as file organizing or report generation); on the road, open the App—the main screen shows the two layers of status:
- Device level: Green "Online" badge = desktop app is online and interactive; gray "Offline" = offline or network unreachable
- Conversation level: Running / Awaiting input / Completed / Stopped / Failed—five states updated in real time
The sidebar also has a set of quick-read indicators: loading animation = processing, green dot = completed but unread, "Pending confirmation" pill = waiting for your answer or approval, red exclamation mark = task failed or was aborted. Each task shows only one indicator at any given moment.
You should see: While the task runs on the computer, the conversation on your phone shows "Running" with live progress scrolling; when it needs your confirmation, it changes to "Awaiting input".
💡 Notifications chase after you—no need to keep reopening to check
The App uses system notifications: four event types—task completed, task interrupted, awaiting answer, awaiting approval—are proactively pushed to your phone, and tapping one takes you straight to the corresponding conversation. Tasks initiated on the phone or computer (including scheduled tasks) all trigger notifications, and multiple phones under the same account receive them simultaneously. There is a buffer period before a notification is sent: if you handle it on the computer or phone during that window, no push is sent.
- Start a task on the computer and see the "Running" status on your phone
Step 5: Continue the conversation remotely and send additional instructions to the company computer
Why: If a task needs extra instructions or a change of direction midway, you don't have to wait until you're back at your desk—messages sent from your phone are routed directly to the desktop app for execution.
How to: Find the target conversation in the task list or workspace, open the conversation detail page, and send instructions in the input box. Official examples: "Continue", "Add logging to the changes just made".
A remote troubleshooting scenario (from the official practice case, with the topic swapped for yours):
I'm not at my computer right now. Please continue troubleshooting the errors in this project, prioritizing the most recent run log, and first tell me the cause and handling suggestions before deciding whether to modify the code.Recommended approach from the official practice case: describe the current problem, expected goal, and acceptable handling scope in natural language—ask for the cause and suggestions first, then decide whether to touch the code.
Besides text, tapping the + next to the input box lets you hand content from your phone over to the computer: take a photo, pick photos / videos, or select phone files (the Mini Program also supports WeChat files, Tencent Docs, and the ima knowledge base). To start a new task within the current workspace, tap the new-chat icon at the top-right of the conversation page (top-left in the Mini Program).
You should see: The input box shows "Replying", the instruction is executed on the computer, and progress scrolls in the conversation.
💡 This is the unique value of WorkBuddy multi-device collaboration
Everything you say on your phone is executed by the WorkBuddy on your company computer—it can work with the files on your computer and keep running tasks left unfinished at your desk, which chatbots and web-based AI cannot do. Official best practice: start long-running tasks at your desk, and follow up, continue the conversation, or stop them from your phone during the commute.
- Send a "Continue" from your phone and the task on the computer keeps running
Step 6: Stop it if it goes off track; artifacts are automatically sent back to your phone
Why: In remote scenarios you can't see the screen, so every extra second an off-track task runs is waste—the official best practice reminds you: stop promptly when the task deviates from the expected direction to save Tokens. After stopping, you still need to get the results back to your phone.
How to (stop): Open the running conversation, tap the input box, then tap the send button on the right—while running it has already become the stop button; tap it once and the desktop Agent terminates execution immediately.
You should see: The conversation status updates to "This round's task has been stopped; the computer has synchronized and terminated the run"; results of completed steps are preserved in the conversation and unaffected.
How to (collect artifacts): Files produced on the computer are automatically sent back to your phone and displayed in the conversation as artifact cards. Tap a card to preview it; tap "All artifacts" to open the list, where you can save or share individual artifacts, and "Batch actions" at the bottom handles multiple at once; the App also supports exporting to your phone (PDF / DOCX / Markdown) or exporting to Tencent Docs.
You should see: Report and document artifacts appear as cards in the conversation; tap to preview, save, or share them directly.
- The artifact list shows the file the computer just generated
📋 Magic Prompt
The two remote scenarios from the official practice cases are distilled below into copyable templates, plus a safety valve for high-risk operations. Placeholders are marked with 【】—swap in your own and they're ready to run.
📝 Remote error troubleshooting (commute rescue edition)
Expected effect: when you're away from the computer, have the WorkBuddy on it keep troubleshooting the problem—a template version of the official practice case example.
## Role
You are an assistant skilled at troubleshooting problems and pinpointing error causes from run logs.
## Task
I'm not at my computer right now. Please continue troubleshooting the errors in 【project name】, prioritizing the most recent run log, and first tell me the cause and handling suggestions before deciding whether to modify the code.
## Input information
### Required fields
- Project/task name: 【e.g., order export script】
- Error symptom: 【e.g., crashes halfway through the run】
### Optional fields
- Log location: 【e.g., the logs/ directory?】
- Acceptable scope of handling: [e.g., only change configuration, do not touch code?]
## Output specifications
- Give the conclusion first: cause + handling recommendation
- Wait for my confirmation before executing any changes
## Constraints
- ✅ Prioritize checking the most recent run log
- ✅ Explain what will be changed before making changes
- ❌ Do not modify code directly without confirmation
- ❌ Do not perform operations beyond the acceptable scope📝 Find files on your phone and transfer across devices
Expected outcome: when you temporarily need to send a PPT or document from your computer to your phone—a template version of the official practice case example.
## Role
You are a file management assistant, skilled at locating and organizing files on the computer.
## Task
Please help me find the 【PPT】 file named 【Project Report】 on my computer, confirm the version, organize it into a directory convenient for sending, and tell me how to complete the cross-device transfer next.
## Input information
### Required fields
- File name: [e.g., Project Report]
- File type: [e.g., PPT / Word / PDF]
### Optional fields
- Directory: [e.g., D:/Documents/2026?]
- Version requirement: [e.g., the most recently modified version?]
## Output specifications
- List the candidate files found (name, path, modification time)
- After confirming the version, organize it into a directory convenient for sending
- Provide the next steps for the cross-device transfer
## Constraints
- ✅ Specify the file name and directory to improve locating success rate
- ✅ When there are multiple versions, list them first for me to confirm
- ❌ Do not directly delete or overwrite any files
- ❌ Do not touch files outside the list📝 Preview high-risk operations first (remote safety valve)
Expected outcome: remotely instruct the computer to delete files or batch-move them, but view the list first—a template version of the official practice case's "reduce high-risk operations" recommendation.
## Role
You are a cautious file organization assistant; you must preview before executing high-risk operations.
## Task
Please 【move the .pdf files in D:/Downloads to D:/Documents/PDF Archive, move the .xlsx files to D:/Documents/Spreadsheets Archive, and leave other files untouched】. Before executing, first list the pending move list for me to confirm.
## Input information
### Required fields
- Operation type: [move / rename / archive]
- Target scope: [directory + file type]
### Optional fields
- Exclusions: [e.g., do not change file names?]
- Backup requirement: [e.g., make a backup copy first?]
## Output specifications
- First output the pending operation list (original path → target path)
- Execute only after receiving my confirmation
## Constraints
- ✅ Require a preview before deleting, overwriting, or batch-moving
- ✅ List operations outside the list item by item
- ❌ Do not skip confirmation and execute directly
- ❌ Do not touch files outside the listCheckpoints ✅
- Both switches on the computer are turned on, the phone and computer are logged in to the same account, and a green "Online" is shown next to the device
- Start a task from the computer, and the phone can see the "Running" status and real-time progress
- Send a follow-up instruction from the phone, and the computer executes it in sync
- Try a remote stop once; the conversation shows "This round of tasks has been stopped; the computer has terminated the run in sync"
- Files produced on the computer are sent back to the phone as artifact cards, viewable or savable
Pitfall reminders
❌ Assuming that scanning the QR code means pairing
Symptom: after scanning the code, you think you are connected, but the device list is empty.
Cause: the official documentation states clearly—the QR code serves only as a guide for opening / downloading and does not participate in pairing; the device relationship is established by logging in to the same account and then selecting the computer at the device entry point.
Correct approach: scan the code to open the App → log in with the same account as on the computer → device entry at the top of the sidebar → select the device.
❌ The phone and computer are not logged in to the same WeChat account
Symptom: no matter what, you cannot connect to the computer.
Cause: the official App documentation states clearly: the WeChat account logged in to the App must be the same as the WeChat account logged in on the computer; otherwise, connecting to the computer cannot be used.
Correct approach: unify both ends to the same WeChat account before logging in.
❌ Only finding out you cannot connect once you are on the subway
Symptom: the device shows "Offline," or the computer cannot be woken once you leave.
Cause: "Allow mobile devices to connect to this device" or "Keep awake for remote access" is not enabled on the computer, or the computer is locked or asleep.
Correct approach: official usage advice—confirm both switches are turned on before leaving your workstation; if the mobile status is inconsistent with the desktop (e.g., it shows offline but the computer is actually online), try reconnecting or check the network.
❌ Sending a vague remote instruction: "Help me organize my files"
Symptom: the computer improvises and touches files it should not, and you cannot even see it.
Cause: the official practice cases remind you—vague instructions should be avoided in remote scenarios; official tips also point out: remote control means WorkBuddy will act autonomously where you cannot see, and operations beyond expectations may not be stopped in time.
Correct approach: give a clear goal + keep key file names and directories; require a preview before deleting, overwriting, or batch-moving. Compare:
# ❌ Vague
Help me organize the Downloads folder
# ✅ Clear
Please move the .pdf files in D:/Downloads to D:/Documents/PDF Archive,
leaving other files untouched. Before executing, first list the pending move list for me to confirm.❌ Mini Program notifications come and go, so you think it is broken
Symptom: sometimes you receive notifications, sometimes not.
Cause: the Mini Program uses WeChat subscription notifications; one authorization allows only one push; when the quota is used up, no push is sent and no pop-up interrupts you. One more thing: the Mini Program only pushes "Task complete" when the task was initiated from the Mini Program—tasks initiated on the computer are notified by the computer itself, without duplicate interruptions.
Correct approach: for the in-session subscription prompt, choose "Notify me"; each interaction in the Mini Program (sending messages, answering questions, approving permissions) automatically replenishes the next push opportunity. For a worry-free option, switch to the App—system notifications; enable notification permission once and no per-item subscription is needed.
Advanced tips (optional)
- Remote configuration session: the phone + panel can select skills, summon experts, toggle connectors, switch permission modes, and choose models—but everything is based on the computer side: unauthorized connectors prompt you to complete authorization on the computer, custom models only show a "Custom" label without displaying keys, and new configurations are still done on the computer; the list is pulled from the computer in real time and cannot be modified when the device is disconnected.
- Remotely create scheduled tasks: tap "Scheduled Tasks" on the + panel, describe what to do and choose the execution frequency (daily / weekly / monthly, etc.), and the computer executes automatically at the set time—official example: "push a summary of yesterday's AI industry news at 9 a.m. every morning." For the full walkthrough, see 3.3 Scheduled Tasks.
- Local first, then remote, then let go: official tips suggest that beginners first use the desktop while watching, get familiar with execution methods, understand habits and risk boundaries, and then gradually let go and run remotely—a three-step example: list locally → move locally and confirm → once the judgment is confirmed to be correct, set it to run every Friday on a schedule.
- Security boundaries: communication between the mobile and desktop is encrypted through a secure relay channel; the device relationship is a one-to-one binding, and other accounts cannot connect to your computer; remote operations do not exceed the existing permission scope of the desktop. Disconnect any device no longer in use at any time; log out promptly after using a public device.
Lesson summary
In this lesson, you used WorkBuddy remote control to turn your phone into a "remote console" for your work computer:
- ✅ One-time pairing, permanently retained: two switches on the computer + same account on the phone to select the device
- ✅ Commute trio: two-layer status viewing, remote follow-up task assignment, one-tap stop
- ✅ Automatic artifact return: preview, save, share; the App can export PDF / DOCX / Markdown or save to Tencent Docs
- ✅ Credit rules: viewing and follow-ups on the phone consume no extra credits; execution on the computer is the same as desktop operations
| Key point | Details |
|---|---|
| Connection permission | "Connect Mobile" panel at the bottom of the sidebar → "Allow mobile devices to connect to this device" |
| Locked-screen remote control | "Keep awake for remote access" or System Settings → General → Allow running when locked |
| Pairing method | QR code is only a guide; same-account login + select the computer at the device entry point; the relationship is permanently retained |
| Conversation-level status | Running / Waiting for input / Completed / Stopped / Failed |
| App notifications | Task complete / Task interrupted / Waiting for answer / Waiting for approval, system notifications |
| Mini Program notifications | WeChat subscription notifications, one authorization per push, interactions automatically replenish the quota |
| Remote stop | The send button becomes a stop button while running; results of completed steps are retained |
| Credits | Viewing and continuing chats on mobile does not consume extra credits; desktop execution matches desktop usage |
Next Lesson Preview
Your phone can now remote-control your computer. In the next lesson, let WorkBuddy live directly inside Tencent Docs—C3 Tencent Docs connector: create a sheet with one sentence, summarize comments, and archive meeting notes.
You will learn:
- The authorization entry point and permission scope of the Tencent Docs connector (read + edit)
- The official Prompt for creating an online sheet or a collection form with one sentence
- Summarizing comments and archiving meeting notes into Tencent Docs