Repository navigation
mobium assistant: ask Gemini, Google Assistant or Siri in typed text, and report what came back and what is in front - #252
Merged
Merged
Conversation
… and report what came back and what is in front A new tool, app_assistant, on every front door. On Android the assist key opens the assistant, its field is typed into and sent, and it waits for an app to come forward or the answer to settle, closing a panel still up with back; on an iPhone Siri is asked through WebDriverAgent and closed with Home. --app names the app expected to come forward, and reached is true only when the assistant handed the request to it — the first version took MobiumApp, uncovered by closing the panel after a web search, for the assistant's doing. A request that acts for the owner is refused without --app; a simulator's Siri, which answers nothing (CHALLENGES 351), and a TV's assistant are refused. assistant.sh passes on the emulator and refuses the simulator; not run on a phone.
lana-20
added a commit
to mobiumdev/mobiumdev.github.io
that referenced
this pull request
Oct 21, 2026
The generator requires an example for every tool, and app_assistant (mobiumdev/mobium#252) had none: the 2026-10-21 scheduled build failed with KeyError 'app_assistant', and the live site stayed at the 2026-10-20 build. Two scenarios, from the command's own help, in all five clients: "Open Clock" naming the app expected to come forward, and reading reached; and a question, reading the answer it showed. The first is captured on the Android 15 emulator, with Clock in front after. The second is not recorded: a signed-out emulator's Google Assistant answers a question with a web search sheet, read in one run of five, so its output would be third-party search results that change between runs. check_examples: 113 scenarios, 0 problems in every client, .NET included.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 6 of docs/ACCESSIBILITY.md: a new tool,
app_assistant(mobium assistant), on every front door (CLI, MCP, Go, Python, JavaScript, Java, .NET). It's for testing an app through the assistant: whether the task was done is for the app to show, never for the assistant to say.How it works:
front,typed: true,closed, and withapp,reached.reachedis true only when the assistant handed the request to the app named. The first version took the app uncovered by closing the panel for the assistant's doing: "Open MobiumApp", a web search signed out, read as MobiumApp coming forward. A unit test and the check's control hold this.Refused:
appnames the app it's for;Measured on the Android 15 emulator, Google Assistant signed out:
Checks:
docs/checks/assistant.sh. PASS on emulator-5554 in 15 s: the text request is refused, Calculator is reached, and the same request naming the app it left is not reached. The simulator refusal also passes.ALLOW_PHONE=1.reached, and the answer extraction.make cigreen.