Discover how to automate a new app or website. Explore UI elements, scrape docs, build selector references. Use when: "learn how to automate", "explore the UI of", "map the interface", "discover selectors", "build reference for", "what can you do in this app", "how does this app work", "explore app".
You are exploring a new app or website to build automation knowledge — discovering UI elements, selectors, keyboard shortcuts, and flows.
Every tool call returns automatic hints. When you navigate to a URL or focus an app, the server auto-loads any matching reference file and injects selector hints, known errors, and strategy suggestions into responses. Watch for [HINT], [WARNING], and [STRATEGY] lines.
Always start with:
platform_guide(platform="{name}")
memory_recall(task="explore {name}")
memory_query_patterns(scope="{name}")
Existing reference files (use these exact names with platform_guide):
x-twitter, , , , , , instagramlinkedinredditthreadsyoutubediscordfigma, canva-smoke-testdavinci-resolve-keyboard, davinci-resolve-menu-map, davinci-resolve-menus-batch1 through batch4codex-desktop, n8n, devto, devpostgoogle-flowIf a reference already exists, review it before exploring further. You may not need to re-explore.
platform_explore)Discovers all interactive elements by actively testing them.
For web apps:
platform_explore(url="https://app.example.com", maxElements=30)
What it does:
For native apps:
platform_explore(bundleId="com.example.App")
What it does:
Output: Saved to references/{platform}.json.
platform_learn)Learns from official documentation without interacting with the app.
platform_learn(platform="{name}", url="https://docs.example.com/shortcuts")
What it does:
Best doc URLs to provide:
Output: Saved to references/{platform}.json.
When the automated tools aren't enough, explore manually:
apps → find the target appfocus(bundleId) → bring to frontui_tree(pid, maxDepth=3) → get overview of top-level elementsui_tree(pid, maxDepth=8) → deep dive into specific areasscreenshot_file → visual referenceui_press, menu_click, keybrowser_navigate(url) → open the appbrowser_dom(selector="button, a, input, [role='button'], [role='tab']") → all interactive elementsbrowser_page_info → page structurebrowser_clickscreenshot_file at each major sectionFor comprehensive coverage:
platform_learn first → get keyboard shortcuts and documented featuresplatform_explore second → discover actual UI elements and test themA good reference file contains:
After exploration:
references/{platform}.jsonmemory_save(task="explored {platform}") to record the exploration strategyplatform_guide and the context tracker$ARGUMENTS