MochiBot practical tips: clear requests and usable results
MochiBot is a mobile AI assistant developed by MochiLab to connect to and operate an OpenClaw workspace. The phone provides chat, files, Skills and reminders; the workspace runs models and tools. This guide covers common Android 1.1.1 operations.
iPhone / iPad: In development.
1. Specify the input, action and result
Provide the material, say what to do with it and describe the output. For large tasks, review a small sample before processing everything.
Check whether you can read this document, and process only the first two pages.
Produce a Chinese summary with main findings, important figures and unresolved questions.
Keep original dates and qualifications; identify uncertainties separately.
Show the sample and wait for my confirmation before continuing.
If you immediately notice a wrong name or time, correct it in the same conversation. For reminders or external operations, still check the final plan and actual task record rather than relying on a promise.
2. Check the destination before sending files
Check the current workspace and AI recipient before sending. Specify which material to process and why. Your model provider receives the content required for the task. Put model keys and complete pairing codes in their dedicated model and connection settings, not in chat.
You can also choose MochiBot from another app's system share menu. Shared content enters a local confirmation flow first. Review the workspace and content before sending; importing is not uploading. File readability and format support depend on workspace tools.
3. Find outputs in Results
Open Results from the chat menu to review task replies and actual files. Local result records are stored independently from chat. Long chat history can also be browsed in pages.
Downloads show progress and can be cancelled; supported files can be previewed. Rechecking result files does not rerun the original task. For same-name files, check the source task and time to avoid mistaking an old result for a new one.
When clearing chat, review whether you also want to clear local results. Removing a local result record neither deletes server files nor cancels tasks. Keeping a result record does not guarantee that its server file remains available forever.
4. Set simple recurring reminders on the phone
In Reminders → My reminders → New scheduled reminder, choose Once, Daily, Monday–Friday or Selected weekdays. Examples include a daily 07:00 wake-up or weekday 17:30 school pickup.
Local reminders do not call AI and use the phone's current time zone. Monday–Friday does not detect public holidays. Use “⋯” to edit, pause, resume or delete. Allow the required permissions and test the sound first.
Use an assistant server task when weather, files or announcements must be checked before notifying you. The execution location and requirements differ. See the task and reminder guide.
5. Inspect task facts; stopping does not undo work
The “⋯” menu beside an assistant task contains its supported actions. Inspect Task details and recovery history for pause reasons, execution facts and recent results. Resume the existing task where supported instead of creating a duplicate.
Pause, resume and stop actions depend on current state and server capabilities. Messages already sent, files already written and other completed external actions are not automatically undone. Deleting received history, clearing chat or disconnecting a phone does not cancel a background task.
6. Watch progress instead of submitting duplicates
A request can pass through queueing, model generation and tool execution. Check its state and elapsed time. File processing often takes longer than a greeting. When adding a correction, identify the part of the previous request that should change.
For persistent delays, check app, connector and OpenClaw versions, along with request times and symptoms. Waiting alone does not prove that the server needs more hardware. Versions appear in Settings; further diagnostics are in Advanced settings.
7. Treat time and city separately from long-term memory
Open Settings → Time and location to follow the phone's time zone or choose one. Enter a city manually, or use Get current city when needed. If you allow approximate location, review the detected city before saving. Clear the city or disable automatic refresh when it is unnecessary.
Saved city and time zone accompany new messages to the current workspace, helping interpret requests such as “tomorrow” or “weather here.” They are not automatically written to long-term memory. Local reminders still use the phone's current time zone; separately verify the time zone in a server task plan.
8. Check native memory for information needed across chats
Explicitly ask the assistant to remember a preference, then inspect native OpenClaw memory in Assistant memory. A new conversation changes chat context without deleting persisted memory. Mentioning something once does not guarantee it has been saved for the long term.
USER.md, MEMORY.md and daily memory files have different recording roles. One missing file does not mean all memory has failed. Test with non-sensitive information you are comfortable saving: save it, open a new conversation and ask about it. Clearly request changes or forgetting and inspect the relevant records. Avoid saving unnecessary personal data.
9. Find Skills by the job, then validate a sample
Search Skills for tasks such as file organization or news summaries. Search covers the entire downloaded catalogue. Refresh when a newer catalogue is needed, without refetching on every visit.
Review the purpose, dependencies and installation request before asking the assistant to install a Skill. Check the actual output afterward. Market monitoring needs its corresponding Skill; scheduled price-check scripts do not imply a model call on every check. Model reasoning and analysis tasks can still consume model usage. All MochiLab Skills are free; server and model costs are separate.
10. Complete a small check before relying on long-running tasks
First confirm chat replies, actual file downloads, an existing task record and a short test reminder. On Android, check notifications, background operation and power restrictions. The workspace, model allowance and external sources also need to remain available.
Start with a short document saved as a real file. Review the result before adding daily briefings or monitoring. See Getting started for connection, or browse Skills for more capabilities.