Run selected tests
Run AI Select from the root of your git repository:--ai-select-base when you need to set it explicitly:
How selection works
AI Select combines three sources of evidence:- The git diff identifies the code and behavior that changed.
- A local code index traces imports and downstream consumers in your repository.
- The App Graph connects product journeys and UI states to the tests that exercised them in real runs.
Use the code index in GitHub Actions
Check out full git history and install the code-index parsers before running AI Select:Preview a selection
Use shadow mode to compare a selection with the full test run before using it to gate pull requests. Momentic still runs every in-scope test and records which ones AI Select would have skipped.momentic ai select:
jq when you want to inspect
or transform it before running the selected paths:
momentic run --ai-select when you do not need to customize the handoff; it
performs selection and execution in one command.
Benchmark
The benchmark uses real code changes across frontend, backend, CLI, shared-library, configuration, and non-behavioral scenarios. The GPT-5.5 Codex baseline receives the same changes and candidate test files as AI Select, but does not use the App Graph or AI Select’s investigation workflow.
We can share the raw results and reproduction harness on request.
Notes
- AI Select needs enough git history to resolve the base ref. Use
fetch-depth: 0withactions/checkout. - The code index currently analyzes TypeScript and JavaScript imports. App Graph evidence can still connect behavior across other boundaries.
- A budget limits selection size, not safety behavior. Edited tests are still included, and AI Select can fall back to running all tests.