AI SRE Agent with Temporal, ClickHouse, and Codex: AURA in a Gated Run

1,133 requests failed on one bad commit. The patch and the regression test are already written by the time anyone is asked to read the exact diff.

Learn more about AURA → https://www.mezmo.com/aura
Get started today → https://github.com/mezmo/aura
Get deployment help → https://www.mezmo.com/contact

This demo runs AURA as one step inside a Temporal workflow, alongside Codex. A GET request against a product catalog service goes from success to HTTP 500, and ClickHouse records the version, commit, trace ID, and exact error for every request. By the time AURA investigates, all 1,133 requests on that version have failed.

AURA reaches ClickHouse through MCP, and in this demo those tools are read-only. It compares the healthy and failing versions, traces one error signature to price formatting in the product handler, and returns the affected commit, supporting query results, a reproduction, and the exact query the workflow should use after deployment. It cannot change the service.

Temporal passes that investigation to Codex. Codex works in an isolated Git work tree, a separate copy of the repository, fixes the formatter, adds a regression test, and runs the test suite. Four tests pass. Temporal then stops. Nothing can deploy until a person reviews the exact diff and approves the rollout.

Approval resumes the same workflow. Temporal deploys the reviewed patch, then AURA checks only the new ClickHouse events and finds 12 successful requests, no failures, and no return of the original error. Temporal preserves the full workflow history.

For more detail, visit
https://www.mezmo.com/videos/ai-sre-agent-with-temporal-clickhouse-and-codex-aura

0:00 How AURA, Codex, and Temporal fit together

0:44 A product catalog regression in ClickHouse

1:27 Codex patches and tests in an isolated work tree

1:48 Approval, deploy, and verification

#AURA #Temporal #AISRE