AutoGenesis is an AI-powered automated testing framework based on Model Context Protocol (MCP), supporting multiple platforms including desktop applications (Windows/macOS) and mobile applications (iOS/Android).
Native macOS and native Windows are supported; Linux and WSL are not. Python 3.10 or newer is required. The Agent Install Prompt detects the native host from local OS facts first and stops on Linux, WSL, or any other unsupported host before any download, acquired-content interpretation, approval request, or write.
Install the CLI through the Python environment and package index you choose:
python -m pip install autogenesis-cli==0.2.0
autogenesis installThe Python package installation resolves the supported host bundle:
| Host | Installed AutoGenesis dependencies |
|---|---|
| macOS | Agent Contract 2.1.0 and Appium Runtime 0.5.0 |
| Windows | Agent Contract 2.1.0, Appium Runtime 0.5.0, and Windows Runtime 0.5.0 |
Check the installed command versions without starting a Runtime or reading business configuration:
autogenesis --version
autogenesis-appium-mcp --version
autogenesis-windows-mcp --version # Windows onlyautogenesis install does not invoke pip or uv. It verifies those already
installed package versions and installs the canonical autogenesis-setup and
autogenesis-run files under ~/.agents/skills. Running it again with identical
Skill files reports them as unchanged.
The command does not install Appium Server, Appium Drivers, platform SDKs,
project MCP configuration, or business configuration, and does not execute an
application. Use autogenesis-setup afterward to inspect a concrete target and
approve any additional machine or project preparation.
For local Appium readiness, Setup loads the immutable official Appium Skills
snapshot pinned by Agent Contract 2.1.0. autogenesis appium-skills --json
verifies its identity and inventory, and autogenesis appium-asset <relative>
returns only bytes held by that verification pass without trusting a mutable path.
Copy agent-install-prompt.txt
from the Agent Contract 2.1.0 release into OMP, Pi, Codex CLI, or GitHub Copilot
CLI. Before acquisition, the prompt requires native Darwin or native Windows
and rejects Linux and WSL. Only after that gate passes does it download the
Setup Skill as untrusted bytes, verify the published SHA-256, show the selected
scope and destination, request approval, and persistently install only
autogenesis-setup through the Coding Agent's native Skill mechanism. A
session-only trial is not supported in this release. Setup then proposes the
host Runtime and project-readiness plan; it does not execute that plan without
the user's approval.
Low-level autogenesis-appium-mcp and autogenesis-windows-mcp packages remain
independently runnable without Skills for expert CLI/MCP consumers.
Please refer to the appropriate documentation based on your testing platform:
Features:
- Windows desktop app automation
- Native Windows control support
- AI-assisted test script generation
Get Started:
- See WINDOWS-README.md for detailed setup instructions
Features:
- macOS desktop app automation
- Native macOS control support
- AI-assisted test script generation
Get Started:
- See MAC-README.md for detailed setup instructions
Features:
- iOS and Android app automation
- BrowserStack cloud testing integration
- AI-assisted test script generation
Get Started:
- See MOBILE-README.md for detailed setup instructions
Features:
- AI-powered BDD test recording and one-click replay
- Natural language to automation code generation
- GitHub Copilot integration via Model Context Protocol (MCP)
Get Started:
- See BDD AI Toolkit README for detailed setup instructions
AutoGenesis/
├── appium-mcp-server/ # MCP server for mobile/mac automation
│ ├── tools/ # Platform-specific driver tools
│ ├── llm/ # LLM integration
│ └── utils/ # Utilities
├── pywinauto-mcp-server/ # MCP server for Windows automation
│ ├── tools/ # Windows-specific automation tools
│ ├── llm/ # LLM integration
│ └── utils/ # Utilities
├── bdd_ai_toolkit/ # VS Code extension
│ ├── src/ # Extension source code
│ └── resources/ # UI resources
└── behave-demo/ # Sample BDD tests
└── features/ # Feature files and step definitions
By default, AutoGenesis reports usage data to the official AutoGenesis Application Insights instance for product improvement.
This telemetry is used to understand feature usage and improve product quality.
For questions or feedback, please contact: autogenesis@microsoft.com
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
See CONTRIBUTING.md for detailed contribution guidelines.
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet, and Xamarin.
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's definition of a security vulnerability, please report it to us as described below.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.
If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the Microsoft Security Response Center PGP Key page.
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
See LICENSE for license information.