v0.3.0

CLI and MCP entrypoint

Spectre now includes a standalone spectre command for inspecting and driving a running, Spectre-enabled Compose Desktop application without first writing a JUnit test.

• Attach to a local JVM, inspect windows and the semantics tree, find nodes by test tag, and drive real click/text input.
• Capture screenshots and recordings from an attached session.
• Run spectre mcp to expose the same session daemon to MCP clients, including inline PNG screenshots.
• Sessions are held by a private per-user daemon, so ordinary CLI invocations and MCP share attached targets.

See the CLI guide for installation, the main workflow, and operational limits.

Install the CLI

macOS:

brew tap rock3r/spectre https://github.com/rock3r/spectre
brew install rock3r/spectre/spectre

Windows:

scoop bucket add spectre https://github.com/rock3r/spectre
scoop install spectre

Linux: download the matching archive below and put spectre on PATH.

The macOS archives are signed and notarised. The CLI requires JDK 21+ for attach operations; the target application must already use Spectre core and run as the same OS user.

Library artifacts

Spectre libraries are available from Maven Central. The CLI is distributed through the release archives, Homebrew, and Scoop—not Maven Central.

dependencies {
    implementation("dev.sebastiano.spectre:spectre-core:0.3.0")
}