Want Codex fixing bugs as they land in Linear? Start your Loop small and let an engineer review the PR

#What changed

On Oct 13, Linear published five lessons from Andrew Moedinger, one of the engineers building Loops. Loops run the Linear Agent on a schedule or when an event happens, and Linear's docs say a loop can open a coding session when a well-scoped bug reaches Triage. Coding sessions run on Claude Code or Codex, set at the workspace level, and come back as a draft pull request. Separately, you can assign an issue to Codex or mention @Codex, and Codex works in your Codex cloud environment and posts progress back to the issue.

Linear CEO Karri Saarinen also shared one customer's chart: after turning on Loops plus Linear's cloud coding agent, their 95th-percentile time from bug report to a production fix fell from 9 weeks to 3 days over three months.

#Who is affected

Teams that track work in Linear and want Codex to pick up recurring work such as bug fixes or dead-code cleanup. Codex for Linear needs a ChatGPT Plus, Pro, Business, Enterprise, or Edu plan with Codex cloud set up, GitHub connected, and an environment for the repo.

#What to do now

1. Pick one recurring job, for example fixing a bug type that keeps coming in or deleting one kind of deprecated code.
2. Have the loop only list candidates at first, and tighten the rules from what it finds.
3. Next, let it file issues into your triage inbox with the assignee it would pick and why, without actually assigning anyone.
4. Cap each run. Moedinger limited his cleanup loop to five issues at a time instead of all 80 or so cases in the codebase.
5. Once its picks look right, let it assign the issue and hand it to the coding agent, and have the assigned engineer review and submit the pull request.
6. Don't over-explain the task. Point the loop at context you already have, like a team skill for investigating bugs or the docs that define who owns what, and ask the Linear Agent to rewrite the loop when its output is off.
7. If you call Codex directly, check the repo map in your Codex environment: the task runs against the default branch of the first repo listed there.

#What is not confirmed

The 9-weeks-to-3-days figure comes from one unnamed customer's chart shared by Linear's CEO. It is a field report and has not been independently verified. How well this works depends on how well-scoped the issues are, and loop runs use Linear AI credits.