| FMRS | 59 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 18 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Teams building React Native, Expo, Flutter, or native apps
- Teams validating apps on local devices, simulators, emulators, or CI
- QA and development workflows where an agent chooses actions at runtime
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Teams seeking a complete replacement for conventional maintained test suites
- Workflows requiring physical Fire TV, capture, or Vega selector backends
- Users without an available supported device, simulator, emulator, or desktop target
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Access to and control of connected iOS, Android, TV, desktop, or other supported device environments
- Reading accessibility trees, logs, network data, performance information, and crash details where supported
- Saving screenshots, videos, traces, and other verification evidence when requested
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - Device actions can change application state or perform test operations
- Element targeting and verification may be less reliable when accessibility data is poor
- Earlier @eN references may no longer identify the same element; use references from the latest output
- Vega OS support is currently VVD-only; physical Fire TV, capture, and selector backends are unsupported
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 0 | 0 |
|---|