Handing a Swarmbot AI script to a teammate? Package the whole project
A main.js file alone is not a useful handoff. Ask Swarmbot AI to document the script's purpose, run inputs and image assets, review the saved project, then export its package. Check name conflicts before import and test on one device afterward.
Swarmbot lets you keep a repeatable phone workflow as a script project. If a teammate needs to continue that work, hand over the project, not just a pasted code file. This is for small teams that already have a script draft from Swarmbot AI and want to review it before using it on another computer or account. Start by opening and saving the project in Swarmbot's script development view, then ask AI to identify its purpose, run inputs and required assets.
Ask AI for a handoff checklist first
A Swarmbot script project can include a manifest with its name and inputs, an entry file, supporting modules and image assets. Sending only main.js may leave the next person guessing which screen to start on, what to enter, or which image a matching step expects. Here is an example request you can adapt in the Swarmbot script assistant; it is not a quote from a customer conversation:
Help me prepare this Swarmbot script project for a teammate. First list its task, required starting screen, values the runner must supply, image or helper files it needs, and any step that changes data or needs human confirmation. Let me review that list before changing the project name, description or inputs. Do not put accounts, passwords or device identifiers in the code.
Put values that change between runs into the input form instead of making a teammate edit code for each search; see the guide to run parameters. If the script uses image matching, check the saved project's image panel and asset names, not merely an image mentioned in the chat. The button-crop guide explains how to prepare that asset.
Review the saved project before exporting
Save the project in Swarmbot's script development view, then use Export Script Package. The package represents the project directory, so review the manifest, entry file, helpers and images together. Ask whether the name and description explain its job, the input form matches the steps, and every image is necessary for that job.
Look for account details, access tokens, private screens or customer information in code, descriptions and images. Do not make a real secret a default input. GitHub's credential guidance also advises against hard-coding credentials in code that may be shared. Give the package only to someone authorized to use it; do not post it as a public attachment.
Check the receiving account before importing
Swarmbot has an Import Script Package action. Before using it, your teammate should inspect their script list: importing a package with the same package name updates the existing project rather than necessarily creating a second copy. If there is a name collision, decide whether replacement is intended and keep the prior version before proceeding. After import, open the project and check its description, inputs, helper files and images.
Finally, start from the agreed screen on one authorized test device and validate a low-risk step before widening the scope. A successful import means the project files arrived; it does not prove that the teammate's app version, signed-in state or device screen meets the script's assumptions. Use the three-question draft review to check what the script may change.