Codex Feedback Lens

Codex Feedback Lens is a small, read-only-first feedback path for Codex CLI projects. After a supported post-edit event, it can run an already-installed TypeScript checker and return bounded current diagnostics to Codex.

This is an early release with a deliberately narrow support boundary.

Install

The PyPI distribution is codex-feedback-lens. The installed command is agent-lens.

pipx install codex-feedback-lens
cd your-project
agent-lens init
agent-lens doctor --json

init creates a project-level Codex hooks file only when Agent Lens can prove that the path is empty and safe to own. It refuses existing or drifted configuration instead of overwriting it.

doctor is read-only. uninstall removes only an exact, unchanged installation that Agent Lens can prove it owns.

Supported feedback path

The verified first-phase path is limited to:

• Linux-native Codex CLI 0.146.0.
• Non-interactive codex exec.
• A successful canonical apply_patch PostToolUse event.
• A pre-installed, conformed TypeScript tsc runner.

Make the absolute runner path available to the Codex process before starting it:

export AGENT_LENS_TSC=/absolute/path/to/tsc

The hook reports current errors in changed files with a fixed detail limit. Project-scope errors outside the changed files are summarized by count, without causal or historical claims.

Safety boundaries

• Existing, malformed, unknown, or drifted project hook configuration is preserved and refused.
• doctor does not run Codex, write runtime evidence, repair files, or change trust state.
• Agent Lens never installs, downloads, updates, fixes, or formats a runner.
• The first phase does not provide ruff or biome adapters, historical comparisons, autofixes, or support for other Codex hosts and edit paths.
• pyright remains reported as disabled-unverified until a separate real conformance gate enables it.

Development

Focused checks from a checkout:

PYTHONPATH=src python -m unittest test.test_cli
python -m unittest test.test_packaging_acceptance

The supported-path end-to-end claim is limited to the host and event boundary listed above; it is not a claim that every Codex edit path or every project has been checked.