Skip to main content
Use the Interfere CLI to inspect problems, read investigation evidence, and call workspace operations from your terminal.

​
Install and sign in

Then sign in and select your workspace:
Sign-in opens your browser. Sign in to Interfere, then set INTERFERE_WORKSPACE to the workspace slug from its URL. For interfere.com/~/acme, use acme. Native binaries support macOS on Apple Silicon and Intel, Linux on ARM64 and x64, and Windows on x64. Keep optional dependencies enabled so installation can select the binary for your platform.

​
Discover commands and arguments

Use help to find commands and --schema to inspect a command’s arguments before calling it:
Workspace operations use INTERFERE_WORKSPACE or an explicit --workspace flag:

​
Inspect a problem

Read a problem, its timeline, and related findings in one command:
The inspect command combines problem details, timeline entries, and related findings. To return only the problem and findings as JSON:

​
Preview a request

--dry-run shows the request without sending it. It does not check your permissions or validate the request against live data. The API performs those checks when you execute the command.

​
Use JSON in scripts

Piped output defaults to JSON. Set --format json to request JSON explicitly. Use --query for a JMESPath expression that selects fields from the output.
Errors in machine output modes are also JSON on stdout, with a nonzero exit status. Check the exit status before treating output as a successful response.

​
Credentials

Credentials are specific to the operations that accept them. A release-only key cannot manage workspace resources. See API keys for scope and expiry behavior. The SDK build plugins read INTERFERE_API_KEY. The CLI reads INTERFERE_SECRET_KEY; use the variable expected by the tool you are running.

​
Build automation

The Next.js and Vite plugins register releases and upload source maps during builds, including builds deployed to AWS, Fly, Render, or your own servers. For other build systems, follow the custom release workflow. Inspect the CLI’s generated command help and schema for the required request fields. Do not automatically repeat a write after a timeout. Check whether the operation succeeded, and preserve its idempotency key when retrying an operation that supports one.