Today we are releasing uok, a command-line tool that brings verification to wherever your C code actually lives: your terminal, your CI or a coding-agent workflow. It is part of Agentic SQA, not a separate product. Foundry Verify reviews pull requests in GitHub, and uok is how you verify eligible claims from those findings yourself, in your own environment.
Why a CLI?
Since launching our GitHub App, the most consistent request we have heard has come from teams who liked what verification does but needed it to run where their code lives: in a developer checkout, in a CI job and, increasingly, in coding-agent workflows, where agents generate C code faster than anyone can review it.
The pattern is the same each time: the check needs to come to the code, not the other way around. uok is that check.
What it does
Agentic SQA works in two layers. The first is investigation: the agent reviews a pull request in a C codebase, finds likely defects and reports each one with evidence. The second layer — the part we care about most — is verification, and uok is where it runs. uok checks concrete review claims against the exact code revision in your own environment and returns a verdict with supporting evidence you can inspect, rather than a score you have to trust.
Not every claim can be mechanically decided. When one can, uok returns PROVEN or REFUTED with supporting evidence; when it cannot, it says NOT PROVABLE rather than guessing. That distinction is the whole product: a finding you cannot trust is a triage burden; a finding with evidence is a fix waiting to happen.
Where it fits
- In CI, on every change.
- In coding-agent workflows: agents write C fast. uok gives the pipeline a verification step before that code reaches a human reviewer.
- In local development: run it from a developer checkout, against the exact code revision in your working tree.
Verification executes locally, and the CLI authenticates to your workspace and transmits results and related metadata to IR Labs. The details of how uok handles your code are in our privacy policy and on the docs page — we keep the precise language there rather than paraphrasing it in a blog post, because precision matters on that topic.
Getting started
curl -LsSf https://get.irlabs.ai/uok/install.sh | shThen uok status reports the state of your installation, uok findings lists the findings available to verify and uok verify returns verdicts. Full documentation lives in the CLI docs, and we would genuinely like to hear what you hit.
Next up: our first public benchmark, so you can see measured results rather than take our word for anything. That is the standard we want to be held to.