Maestro Explore

Maestro Explore

Find a target page, screen, or component in the live app by iteratively inspecting the device, deciding where to navigate, and executing taps/scrolls via Maestro MCP until the target is found. Output the navigation steps so the user knows exactly how to reach it.

Prerequisites

• A device/simulator must be running with the app installed (release build)
• Get the device ID via user-maestro-list_devices
• If no device is running, start one with user-maestro-start_device

MCP Tool Usage Rules

CRITICAL: Understand the two flow execution tools and when to use each.

run_flow — inline ad-hoc commands only

Use for single commands or short sequences that don't reference external files. The YAML is written to a temp file, so runFlow: file: references with relative paths will break.

# GOOD — inline commands
- tapOn:
    id: portfolio-screen-tab

# GOOD — multiple inline commands
- tapOn: "Change portfolio"
- waitForAnimationToEnd
- assertVisible: "All Portfolios"

# BAD — file references break because temp file is in /tmp
- runFlow:
    file: ../../utils/login.yml

run_flow_files — run existing .yml flow files

Use when you need to run an existing flow file (login, startApp, etc.) that lives in the workspace. Pass the workspace-relative path.

run_flow_files(device_id, flow_files="maestro/flows/portfolio/changePortfolioSingleDefcon.yml")

You can also pass env vars via the env parameter.

Summary

Step 1: Gather Target

Collect from the user (use AskQuestion when available):

1. Target: What to find — a page name, component, text, feature, or UI element
2. Account type (optional): Single account, multiple accounts, IRA, etc. (affects login user)

Step 2: Research Before Exploring

Before blindly navigating, look for clues in the codebase.

2a. Search existing Maestro flows

Grep: "<target keywords>" in maestro/flows/
Glob: maestro/flows/**/*.yml

If a flow already navigates to the target, read it to extract the path. This can shortcut the entire exploration.

2b. Search the source code

Grep: "<target keywords>" in src/

Look for screen names, navigation routes, tab labels, or accessibility IDs that match the target.

2c. Build initial hypothesis

From your research, form a hypothesis about how to reach the target:

• Which tab? (dashboard, portfolio, profile)
• How deep? (top-level, nested screen, modal)
• Any prerequisite state? (specific account type, feature flag)

If research gives a clear path, skip directly to Step 3b and execute it. If uncertain, proceed with the explore loop.

Step 3: Explore Loop

3a. Bootstrap — Login and land on dashboard

If an existing flow gets you to the right starting point, use run_flow_files:

run_flow_files(device_id, flow_files="maestro/flows/_temp_explore.yml")

Or write a temp flow file in maestro/flows/_temp_explore.yml with the login + initial navigation, then run it. This avoids the relative-path problem.

If you just need to login, you can also create a minimal temp file:

appId: com.guideline.mobile
tags:
  - ignore
---
- runFlow:
    file: ../utils/login.yml
    env:
      USERNAME: single-defcon@guideline.test

Path depth matters: flows in maestro/flows/ use ../utils/, flows in maestro/flows/subdir/ use ../../utils/.

Default users (choose based on target):

• single-defcon@guideline.test — single 401k account
• multi-defcon@guideline.test — multiple accounts

Initialize the navigation log:

Navigation Steps:
1. Launch app and login

3b. Inspect → Decide → Act → Check (repeat)

Loop until the target is found or you've exhausted reasonable paths.

Inspect:

1. user-maestro-inspect_view_hierarchy — get all elements with text, IDs, bounds, states
2. user-maestro-take_screenshot — visual context of current screen

Decide:

Scan the hierarchy for:

• Target found? — If the target text, component, or element is visible, you're done. Go to Step 4.
• Clue elements — Buttons, tabs, or list items that might lead toward the target
• Scrollable content — If the screen might have the target below the fold, scroll first

Decision priority:

1. Tap an element that exactly or partially matches the target
2. Tap a navigation element that likely leads to the target (based on your hypothesis)
3. Scroll down to reveal more content
4. Back out and try a different path

Act:

Execute via run_flow with inline commands (no file references):

- tapOn:
    id: profile-screen-tab

- scroll

- tapOn: "Statements"
- waitForAnimationToEnd

Log the step — append to the navigation log:

2. Tap "Profile" tab (id: profile-screen-tab)
3. Scroll down
4. Tap "Statements"

Check:

After acting, inspect again to see the new state. If you navigated to a dead end:

• Use user-maestro-back or run_flow with - back to return
• Remove the dead-end step from the log
• Try the next most likely path

3c. Backtracking

If a path doesn't lead to the target:

1. Go back via run_flow: - back or tap back/close button inline
2. Log the backtrack (but don't include dead ends in the final output)
3. Try the next candidate from the previous screen

3d. Bail out

If you've explored all tabs and reasonable paths (typically 10+ iterations) without finding the target:

1. Report what you searched
2. Show the closest match you found (if any)
3. Suggest the target may not exist in the current build, or may require a specific account/feature flag

Step 4: Report Results

When the target is found:

1. Take a screenshot via user-maestro-take_screenshot to show the target
2. Present the navigation steps clearly:

Found: [target description]

Navigation Steps:
1. Launch app and login (user: single-defcon@guideline.test)
2. Tap "Profile" tab (id: profile-screen-tab)
3. Tap "Statements"
4. Tap "2025 Annual Statement"

From the dashboard, it takes 3 taps to reach this screen.

3. Show the element details from the hierarchy (text, ID, bounds) if the user needs selector info for a test

Troubleshooting