← Back to Discover

Vericore

Vericore is a local-first verification layer that checks whether an AI coding agent changed only what it was supposed to change.

Testing & QACommand-line tools
Visit website ↗

What it does

Vericore compares a Git repository with a change contract recorded before editing. Before asking the coding agent to edit, run vericore prepare with the intent and a planned file path. Then ask the agent to make the change, and do not replace the saved contract after the edit. Next, run vericore verify with the repository path. Vericore reports whether the observed change matched the prepared boundary and what its checks established. Its results identify checks, reasons and criteria that still need review. Repository analysis stays local by default. Deterministic analysis does not require an AI API key.

Capabilities

  • The installer verifies the SHA-256 checksum of the downloaded archive.
  • Release archives include a Java runtime.
  • AI-provider features are optional.
  • You can connect an agent to Vericore through MCP.
  • Vericore can be used in GitHub Actions.

When to use it

  • You want to check whether an AI coding agent stayed within the change you asked for.
  • You want to see what the verification evidence does and does not prove.
  • You work in Java or Kotlin repositories.