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.
Download the Release manifest and its generated strict-hash lock from the same immutable GitHub Release. Do not install AutoGenesis directly by version from an index. Use the package index or mirror you choose only under that lock:
curl --proto '=https' --tlsv1.2 --fail --location --remote-name https://github.com/FSQ-lab/AutoGenesis/releases/download/agent-contract-v2.1.0/release-manifest.json
curl --proto '=https' --tlsv1.2 --fail --location --remote-name https://github.com/FSQ-lab/AutoGenesis/releases/download/agent-contract-v2.1.0/autogenesis-release.lock
python -m pip download --require-hashes --requirement autogenesis-release.lock --dest autogenesis-wheelhouse
python -m pip install --force-reinstall --no-deps --no-index --find-links autogenesis-wheelhouse --require-hashes --requirement autogenesis-release.lock
autogenesis install --scope user --project-root "$PWD"The Release workflow derives autogenesis-release.lock from the reviewed
manifest wheel identities and a universal third-party dependency lock. Missing
or changed bytes fail before any first-party AutoGenesis code executes.
The 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 the authenticated
Runtime bundle and installs one canonical autogenesis Skill at the explicit
--scope; --project-root binds discovery precedence. Re-running identical
bytes is idempotent, while another canonical or legacy discovery copy fails.
The command does not install Appium Server, Drivers, SDKs, project MCP, or
business configuration. Invoke autogenesis for preparation, diagnosis, direct
execution, or BDD work. For Appium targets it loads only a supported authenticated
official workflow with autogenesis appium-workflow <id> --json; the Coding Agent
follows its terminal diagnostics and then uses the canonical installed platform MCP.
Copy agent-install-prompt.txt
from the reviewed Release or Candidate into the Coding Agent. The prompt rejects
Linux/WSL before writes, authenticates one autogenesis Skill and the CLI source,
shows the complete scope/destination/package plan, obtains one approval, and uses
the same autogenesis install transaction as CLI-first installation. It stops
before a business task.
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.