Memory and skills

The assistant gets better at working with your devices and apps over time, and lets you teach it directly. Memory is what it noticed and verified on its own, while a skill is a playbook you hand it directly. Both carry forward into future conversations.

​

What the assistant remembers

Across conversations, the assistant keeps notes tied to your account: device quirks, app-specific traps, your stated preferences, and workarounds that turned out to be necessary before.

This device needs a couple of extra seconds after launch before the screen responds.

This account always shows a login screen on a fresh session, even though it worked yesterday.

It writes these down as plain facts, not guesses. Memory is tied to your account, not to a single conversation, so a new chat can still benefit from what an earlier one learned.

​

Asking what it did

Ask “what did you do” or “give me a recap” and the assistant answers from its own record of past actions in this account, not by re-inspecting your devices from scratch. For a specific past session, ask about it by what you were doing at the time.

What did you do on the Pixel 8 yesterday?

Narrow the question to a device or an app and the assistant filters its answer instead of giving you everything.

​

Uploading your own skills

You can upload your own playbook, checklist, or notes as a markdown file, and the assistant picks it up automatically and follows it from your next message onward. This is the fastest way to make it follow a process you already have written down, in your own words, instead of re-explaining it in chat every time.

Here’s my checklist for closing out a listing. Follow it whenever I ask you to close one.

Markdown is the format the assistant reads most reliably, so write your playbook as a plain document rather than a spreadsheet or a slide deck.

​

Teaching it an app or a path once

Ask the assistant to learn a specific path through an app, for example how you post a listing or export a report, and it walks through that path once, on a real device. It notes the stable steps, the screens involved, and anything that tends to go wrong, then saves that as reusable knowledge.

Learn how to export a CSV of orders from this app, so you don’t have to rediscover it every time.

Before treating what it learned as reliable, the assistant replays it once to confirm it still works. If it already has verified knowledge of that exact path from before, it reuses it instead of exploring again.

​

App cards it consults before acting

Before the assistant takes its first action inside an app during a conversation, it checks whether it already has notes on that app: known screens, a login flow, and traps to avoid. If notes exist, it uses them and tends to work more reliably and faster. If not, it falls back to figuring the app out as it goes, and may write new notes afterward. This happens automatically. You do not need to ask for it, and it applies both to apps the assistant already knows well and to ones you taught it yourself with a learn request.

​

Limits

Memory and skills are scoped to your account and are not shared with other Mobilerun accounts. The assistant also periodically refreshes its own built-in knowledge base in the background; you do not need to do anything for that. If you are unsure whether the assistant already knows something about a device or app, just ask it.

​

Related