# OpenAI Codex — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/codex

An agent’s patch and its execution trace should be available for inspection.

## What we admire

Codex’s task-oriented coding workflow makes it natural to delegate a change and inspect the resulting diff, commands, and tests. That creates the exact handoff CodeVetter was built to verify.

## The principle that stayed

Even when an agent reports successful tests, the verifier should bind those observations to the precise revision and test scope. A changed branch or missing environment changes what the claim means.

## Where CodeVetter stands

CodeVetter supports local Codex sessions as one input to verification. It is independent software and does not use Codex output itself as the final judge.

## Sources

- [OpenAI Codex](https://developers.openai.com/learn/codex) — the creator's own source
- [CodeVetter project log](https://github.com/Codevetter/codevetter/blob/main/docs/archive/project-log.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)