VerdictUI · Version 1.1.3

UI verification.
Evidence you can act on.

Give your agent structured feedback from your actual interface. Inspect state, perform an action, and check its outcome across SwiftUI, AppKit, live macOS apps, and headless web sessions.

Download for Apple Silicon Connect your project

macOS 13 or later · Developer ID signed and notarized

Choose the interface you need to verify.

Each path has an explicit target and its own evidence. Bundled demo scenarios demonstrate the engine; they do not measure your product.

SwiftUI scenarios

Compile your own views into a consumer runner. Inspect semantic layout, exercise actions, and sweep variants with evidence tied to node IDs.

Your scenario registry and instrumentation

AppKit and live macOS

Verify AppKit subjects through your runner, or inspect a running app’s Accessibility tree and check the observed outcome of an action.

A configured runner, or a running app with OS access

Headless web sessions

Open real pages in owned Chrome sessions. Inspect rendered content, act on observed controls, and verify the resulting state through CLI or MCP. A PASS can still include unresolved paint warnings.

Chrome and an explicit URL or saved profile

A desktop workbench for your checks.

VerdictUI 1.1.3 includes a local desktop interface for editing project checks, running verification, reviewing evidence and history, and cancelling work in progress.

Read the desktop guide

Prefer the CLI?

brew install medlars/tap/verdictui

Homebrew builds the CLI from source and requires Xcode 16.0 or later. Browser checks also need Chrome or Chromium. The desktop download above is for Apple Silicon Macs.

Start with your project.

Declare the real targets in .verdictui/checks.json, then run one project check. A missing configuration is reported as unavailable.

For SwiftUI scenarios, link the reusable runner to your registry. With a configured build product, the warm MCP or daemon transport rebuilds and restarts its consumer when source changes. Failed builds cannot certify the old executable.

Project check

verdictui check \
  --project /path/to/your/project \
  --pretty

0 · PASS: No confirmed errors in the checks performed. Warnings may still need review.
1 · FAIL: A measured check found a failure.
2 · UNAVAIL: A target could not be verified. This takes precedence over failure.

Documentation and downloads

Version 1.1.3 is available now. Start with the desktop download or Homebrew CLI, then configure the subjects and workflows you want to verify.

Integration guide

Connect real project views and configure checks.

MCP setup

Connect your agent to scenario, web, and live tools.

Source and documentation

Read the architecture, contracts, and test evidence.

Version 1.1.3 release notes

Read what shipped and verify the published checksums.

A passing check covers its declared subjects and assertions. Browser PASS may include a web-paint-unverified warning; it does not certify painted overlap or occlusion. Review cited findings as well as the status. Full application coverage requires your own scenarios and workflows. Live macOS verification depends on available OS permissions; system dialogs and application lifecycle tests may still require dedicated end-to-end tests.

UI verification.Evidence you can act on.