Where is your Swarmbot AI script? Add useful progress messages to the Device Wall
Ask Swarmbot AI to add concise messages at important script checkpoints so the Device Wall shows the current stage. Check the execution result separately before calling the task done.
Swarmbot shows a running script's status on the corresponding device card. If you want to see whether a task is finding a page, checking a result, or waiting for you, ask Swarmbot AI to add a few clear progress messages to the script. This is useful for people watching a longer workflow across one or several phones without keeping a detailed log open. Start with a saved project in Swarmbot's script development view and identify the stages that matter to you.
Describe stages, not every line of code
A useful request gives AI the starting screen and the moments at which the user needs an update: checking the starting state, completing the main action, and verifying the outcome. For a script that opens an app and reads a page, you could say:
Read the current Swarmbot script-function documentation first. Identify the starting screen, the point where this script reaches the target page, and how it checks the result. Add short device-card messages at those stages, such as “Opening the target page,” “Checking the page,” and “Check complete.” If the page is missing or I need to sign in, say why and stop. Do not treat a click as proof that the task succeeded. Show me the proposed changes before running anything.
Swarmbot's script documentation includes JPShowLog, which updates the current task's message on the device card. Each new message replaces the previous one. It is the script's progress report, not an independent confirmation of a successful business outcome. Keep detailed diagnostics in the execution log and the card message focused on what a person needs to know now.
Place messages after the right checks
Review where AI puts each message. “Check complete” immediately after an open-app call is misleading if the target page has not appeared. A better flow says “Opening app,” then changes to “Reading page” only after the target screen is confirmed, and reports completion after the expected value is checked. If a sign-in prompt requires a person, say “Waiting for sign-in” and stop that path.
Use short, specific phrases. Keep account names, message contents, and customer details out of device-card messages: people nearby may see them, and status changes can appear in execution records. Put the necessary error detail in the log. The W3C guidance on status messages explains the general value of understandable progress feedback; it does not define Swarmbot's script API.
Check the outcome as well as the message
Try the revised script from the agreed starting screen on one authorized device. Watch whether the card message matches the visible stage, then open Logs / Results and inspect the task state and actual page result. A final “Check complete” message alone does not prove the expected value was read. If the script stops, retain the first error and the last stage you actually confirmed.
The Device Wall status guide shows where to view a task. Before running an AI draft, use the three-question review. When asking AI for a revision, provide the last message shown, the screen that was visible, and the relevant first error; that is more actionable than “it failed again.”